Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

lastseen score

REMOTE · SCORE.LASTSEEN.DEV · SCANNED AUG 20

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

Available components

remote · score.lastseen.dev 65
65 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 235 tokens (~78/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · score.lastseen.dev

# add to Claude Code
claude mcp add --transport http dev-lastseen-score https://score.lastseen.dev/mcp
# ~/.codex/config.toml
[mcp_servers.dev-lastseen-score]
url = "https://score.lastseen.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-lastseen-score": {
      "type": "remote",
      "url": "https://score.lastseen.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-lastseen-score --url https://score.lastseen.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-lastseen-score:
    url: "https://score.lastseen.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "dev-lastseen-score": {
      "type": "http",
      "url": "https://score.lastseen.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Aug 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 18 Aug 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Aug 2026 · Probed https://score.lastseen.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lastseen.dev CN=WE1,O=Google Trust Services,C=US 2 Aug 2026 31 Oct 2026 ECDSA 256 ECDSA-SHA256 dd5f28c8575e04d91312f40bc69a329c
SANs: lastseen.dev, *.lastseen.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of score.lastseen.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
lastseen.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://score.lastseen.dev/mcp Verified 200
http (plaintext) http://score.lastseen.dev/mcp HTTPS enforced 301 https://score.lastseen.dev/mcp
MCP tools · 3 exposed · ~235 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
dependency_risk ~49

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

NameTypeReqDescription
idstringyese.g. io.github.owner/name

No output schema declared.

No examples provided.

schema_history ~57

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.

NameTypeReqDescription
idstringyese.g. io.github.owner/name

No output schema declared.

No examples provided.

trust_score ~129

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.

NameTypeReqDescription
idstringyesMCP schema-server identifier, e.g. io.github.owner/name

No output schema declared.

No examples provided.