Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev register.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://score.lastseen.dev/mcp3 tools · 625mstrust_scoreDerived 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 n…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 n…
| Parameter | Type | Description |
|---|---|---|
| id* | string | MCP schema-server identifier, e.g. io.github.owner/name |
schema_historyDated 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.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.
| Parameter | Type | Description |
|---|---|---|
| id* | string | e.g. io.github.owner/name |
dependency_riskAn MCP server's dependencies and their mortality state (dead/dormant counts) from the register. Facts, not a score.An MCP server's dependencies and their mortality state (dead/dormant counts) from the register. Facts, not a score.
| Parameter | Type | Description |
|---|---|---|
| id* | string | e.g. io.github.owner/name |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev register.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.