Skip to content

lastseen score MCP server

dev.lastseen/scorelastseen.devstreamable-httpv1.0.1Scanned

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

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the lastseen score MCP server can do

The lastseen score MCP server is published by lastseen.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: trust_score, schema_history and dependency_risk), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • dependency_riskWhen 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_historyWhen to call: before you rely on an MCP server's tools being stable, e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_scoreWhen 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://score.lastseen.dev/mcp: tools/list returned 3 tools to an anonymous client, including trust_score (write), schema_history (write), dependency_risk (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__score__trust_score",
      "mcp__score__schema_history",
      "mcp__score__dependency_risk"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as score. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.lastseen/score/verify?hash=cf50568055912db99df198d3ebbd960e38a4f82fbec63250408fb5a9ee7fd4e2" | jq -e '.changed == false'

Pinned hash cf5056805591, from Nov 15, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.lastseen/score/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.lastseen/score
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.lastseen/score.svg)](https://radar.anlyon.com/servers/dev.lastseen/score)

Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.

lastseen score MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the lastseen score MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the lastseen score MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the lastseen score MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the lastseen score MCP server have?

3 tools: 3 write. trust_score, schema_history and dependency_risk.

Does the lastseen score MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the lastseen score MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the lastseen score MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.