protogrid

Search / dev.lastseen/score

lastseen score

R0· no sign-in

Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev notary register.

v1.0.1 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality68needs work
Trust82of 100
Uptime, 30 days96%
Latency p50658 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "score": {
      "type": "http",
      "url": "https://score.lastseen.dev/mcp"
    }
  }
}
claude mcp add --transport http score https://score.lastseen.dev/mcp
[mcp_servers.score]
url = "https://score.lastseen.dev/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "score": {
      "type": "remote",
      "url": "https://score.lastseen.dev/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "score": {
      "type": "http",
      "url": "https://score.lastseen.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=score&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vc2NvcmUubGFzdHNlZW4uZGV2L21jcCJ9"
}
{
  "servers": {
    "score": {
      "type": "http",
      "url": "https://score.lastseen.dev/mcp"
    }
  }
}
{
  "mcpServers": {
    "score": {
      "httpUrl": "https://score.lastseen.dev/mcp"
    }
  }
}
extensions:
  "score":
    enabled: true
    name: "score"
    type: streamable_http
    uri: "https://score.lastseen.dev/mcp"
    timeout: 300

Quality 68 / 100needs work

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: trust_score (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); schema_history (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dependency_risk (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 605 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability50 · weight 15
  • pass
    stability.changes3 tool changes in 30 days
  • fail
    stability.rug_pull3 tools kept their name but changed most of their description in 30 days; review before trusting them
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 605 tokens to load them all · tool set fe1a8bd90aa1 · tools last changed 2026-10-05 · checked 2026-10-19 13:37 UTC

Tool changes

  • dependency_riskchangeddescriptionmeaning changed
    before

    An MCP server's dependencies and their mortality state (dead/dormant counts) from the register. Facts, not a score.

    after · 18% of words in common

    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_historychangeddescriptionmeaning changed
    before

    Dated schema/tool-count observations for an MCP server (a series when known): first_seen, last_observed, drift events. Facts from the register, not a score.

    after · 27% of words in common

    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_scorechangeddescriptionmeaning changed
    before

    Derived trust score (0-100) for an MCP server, computed from the lastseen.dev register's dated observations by a published method. The score carries DEPTH (how many of 5 dimensions were computable) BOUND INTO the number as `display`, e.g. '80 · depth 2/5 · provisional' — a depth-2 score answers a narrower question (mortality, not merit). Not a prediction, not advice. Methodology: score.lastseen.dev/methodology.

    after · 21% of words in common

    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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository
provenance55
liveness99
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-96% +updated-21d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://score.lastseen.dev/mcp streamable-httpnoneyes96%658 ms2025-06-182026-10-19

Tools (3)

dependency_riskWhen 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_historyWhen 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_scoreWhen 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.

Schemas: list_tools.

Similar MCP servers

More from dev.lastseen

Official server.json
{
  "name": "dev.lastseen/score",
  "title": "lastseen score",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://score.lastseen.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "websiteUrl": "https://score.lastseen.dev",
  "description": "Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev notary register."
}