Trust scores and dated liveness/drift facts for MCP servers, from the lastseen.dev register. Connect the official lastseen score MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http lastseen-score https://score.lastseen.dev/mcpRun in your terminal, then restart Claude Code.
lastseen score · https://score.lastseen.dev/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “trust_score”: Derived trust score (0-100) for an MCP server, computed from the lastseen.dev register's dated observations by a published method. The score.”
“Use “schema_history”: Dated schema/tool-count observations for an MCP server (a series when known): first_seen, last_observed, drift events. Facts from the regist.”
“Use “dependency_risk”: An MCP server's dependencies and their mortality state (dead/dormant counts) from the register. Facts, not a score.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how lastseen score holds up.
Operated by lastseen score (lastseen.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If lastseen score adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose lastseen score in the gate directory. No sign-in needed.
lastseen score's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
trust_score — Derived trust score (0-100) for an MCP server, computed from the lastseen.dev register's dated observations by a published method. The score
schema_history — Dated schema/tool-count observations for an MCP server (a series when known): first_seen, last_observed, drift events. Facts from the regist
dependency_risk — An MCP server's dependencies and their mortality state (dead/dormant counts) from the register. Facts, not a score.
https://score.lastseen.dev/mcpYes — lastseen score operates its own remote MCP server at score.lastseen.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick lastseen score in the directory. No account or sign-in is needed. From then on, lastseen score's tools are available in every client you've connected to gate.
No. lastseen score runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect lastseen score in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up lastseen score in: Claude · Claude Code · ChatGPT · Cursor · VS Code
One URL. All MCPs. Full control. Free to start.
Get started free