lastseen score
by score.lastseen.dev in Security & trust
Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev notary register.
https://score.lastseen.dev/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 400 ms typical, 429 ms slowest 5%
- Last check
- 3 h ago
- Next check
- in 3 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"lastseen-score": {
"type": "http",
"url": "https://score.lastseen.dev/mcp"
}
}
}3 tools
- trust_score
When to call: before you connect to, install, wire into an agent, or recommend an MCP server, to check what the public record shows about whether it is still maintained. Pass the MCP schema-server id. Returns: JSON with trust_score (0 to 100 or null), display (score · depth · pro
- schema_history
When to call: before you rely on an MCP server's tools being stable, e.g. you are about to integrate it, pin tool names, or check whether the tool list changed under the same server id. Returns: dated facts, not a score: first_seen, last_observed, drift_events, n, and observation
- dependency_risk
When to call: before you connect to or recommend an MCP server, when you care whether its declared dependencies were observed dead or dormant in the lastseen.dev register. Returns: dated facts, not a score: depends_on[], dead_dependency_count, dormant_dependency_count, n, provena
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 3 h ago | Passed | 200 | 429 ms |
| 12 h ago | Passed | 200 | 404 ms |
| 21 h ago | Passed | 200 | 400 ms |
| 31 h ago | Passed | 200 | 245 ms |
| 41 h ago | Passed | 200 | 377 ms |
| 2 days ago | Passed | 200 | 504 ms |