mcpbeat Sign in

lastseen score MCP Server

answering

lastseen score is answering right now. Last checked 6 min ago. It exposes 3 tools.

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

Uptime history 69 days of history · worst day 95%
69 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
279 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 October 2026. No other catalogue keeps this.

5 Oct 3 tool descriptions were rewritten dependency_risk, schema_history, trust_score

Nothing serious here today

Today is the operative word: we check lastseen score every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add score --transport http https://score.lastseen.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://score.lastseen.dev/mcp
~/.codex/config.toml
[mcp_servers.score]
url = "https://score.lastseen.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "score": {
      "url": "https://score.lastseen.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "score": {
      "type": "http",
      "url": "https://score.lastseen.dev/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dependency
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, 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
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 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
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 · 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.

Endpoints

URLTransportStateLatencyChecked
https://score.lastseen.dev/mcp streamable-http answering 266 ms 6 min ago

Alternatives to lastseen score

same job, measured the same way
Search MCP Registry
by onticx

Search and discover MCP servers from the MCP Registry.

168 installs/wk local only
Open MCP Registry
by onticx

Search and discover MCP servers from the MCP Registry.

85 installs/wk local only
MCP Server MCP Registry
by formulahendry

MCP Server for MCP Registry to discover and search for available MCP servers in the registry

18 installs/wk local only
MCP Queen
by mcpqueen

The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server.

7 tools answering
A
Azure Verified Modules (AVM) MCP Server
by stefanstranger

Discover and explore Azure Verified Modules from the Bicep Public Registry

132 installs/wk local only
Trello MCP Server
by stucchi

MCP server for the Trello REST API – manage boards, lists, cards, labels, checklists and more

229 installs/wk local only
Kvk Handelsregister
by iwebdevelopment

KVK Handelsregister AI Connect: hosted MCP server for the Dutch business register.

answering
VerifyMCP
by verifymcp

Independent trust scores, tool surfaces and change history for MCP servers.

9 tools answering

lastseen score — questions

Answers built from our own checks of this server.

What can lastseen score do?
It exposes 3 tools, read directly from the server on our last check. Among them: dependency_risk, schema_history, trust_score. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is lastseen score working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 279 ms. The bar chart above shows every period we have measured.
How do I connect lastseen score?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does lastseen score need an API key?
No. lastseen score completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is lastseen score?
It answers our handshake in 279 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.