lastseen score MCP server

• dependency_riskFree

  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).

• schema_historyFree

  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.

• trust_scoreFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 2084ms17/20
• Tool poisoning3 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

71/100

higher than 36% of 48,255 servers

Tools

3

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

200 ms

faster than 64% of 30,031 servers

Grade history

• 2026-11-03restoreC → Bscore 71: No source repository listed

lastseen score: common questions

Is lastseen score MCP server safe?

Mostly: it is graded B (71/100). Read the lastseen score safety report

How do I install lastseen score?

It runs remotely at score.lastseen.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does lastseen score need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is lastseen score maintained?

The latest release is v1.0.1.

Is lastseen score up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does lastseen score compare with other MCP servers?

safety score 71/100 (higher than 36% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.