Skip to content

Lastseen MCP server

Which MCP servers are Lastseen's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Lastseen

Whose server it is
  • Registry namedev.lastseen/scoreverified in the MCP registry

The registry name sits under lastseen.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools3
  • Server calls itselflastseen-score
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 522 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Use25 PyPI downloads a week
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer539 ms
  • Space in an agent's context≈ 641 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 3 of 3

What an agent can do with it

  • not sure · check whether a repo's or package.json's dependencies are still maintained
  • not sure · look up a component's maintenance state as of a past date
  • not sure · verify published observation history against its public hash chain

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-26
  • 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…

  • 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…

  • 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[]…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "score": {
      "type": "http",
      "url": "https://score.lastseen.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http lastseen https://score.lastseen.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://score.lastseen.dev/mcp as a custom connector in the settings.

Other servers listed as Lastseen's
  • dev.lastseen/mortalitynot asked yetverified in the MCP registry

OpenAPI spec

61 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.