lastseen score
Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev notary register.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"score": {
"url": "https://score.lastseen.dev/mcp"
}
}
}Remote endpoints
https://score.lastseen.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢trust_score(id)
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 · provisional), depth/depth_max, per-dimension values (liveness, maintenance, adoption, spec_currency, dependency_health; null = unknown, never invented), effective_weights, resolution method/confidence, status (scored | unresolved | insufficient_data), methodology URL. Depth 2 answers mortality more than merit; cite display as-is. Not a prediction, not advice, not a ranking of alternatives. Example: {"id":"io.github.06ketan/medium-ops"} id: MCP schema-server identifier (e.g. io.github.owner/name or owner/name). Not an npm package name, Action slug, or Docker image.
Input Schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "MCP schema-server identifier, e.g. io.github.owner/name"
}
},
"required": [
"id"
]
}🟢schema_history(id)
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 observations[] with observation_date, tools_hash, tool_count (may be null), changed. Use trust_score for the derived score and dependency_risk for dependency mortality counts. Example: {"id":"io.github.06ketan/medium-ops"} id: MCP schema-server identifier (e.g. io.github.owner/name). Same id space as trust_score.
Input Schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "e.g. io.github.owner/name"
}
},
"required": [
"id"
]
}🟢dependency_risk(id)
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, provenance. Empty depends_on or zero counts means no dependency edges were on record for that id as of the response, not a guarantee of zero risk. Example: {"id":"io.github.06ketan/medium-ops"} id: MCP schema-server identifier whose dependency edges to inspect (e.g. io.github.owner/name).
Input Schema
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "e.g. io.github.owner/name"
}
},
"required": [
"id"
]
}Community
Evidence