lastseen mortality MCP server
dev.lastseen/mortality·v0.1.2Check whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned.
0 stars
Reviews
Write oneNobody has reviewed lastseen mortality yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
lastseen mortality tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 44 days ago12/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
How lastseen mortality compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 1,119 Developer tools servers
Install lastseen mortality in Claude Code, Cursor or VS Code
claude mcp add mortality -- uvx lastseen-mcp
What the publisher says
From the lastseen mortality repository's README, as published. We do not edit it. Read it on GitHub
lastseen-mcp
<!-- MCP registry ownership --> mcp-name: dev.lastseen/mortality
Is this dependency dead? Dated observations of whether an npm package, GitHub Action, MCP server, or Docker image is alive, dormant, abandoned, archived, or deleted — published by lastseen.dev. Free, no API key, zero telemetry.
There are two ways in, and they answer the same question from the same dated data:
keeps a dependency list can re-check it on every build.
- Call the free HTTP API directly — the durable, machine-native path (below). An agent that
- Run it as an MCP server — a thin stdio wrapper over that same API, for MCP clients.
1. The free API (call it directly)
No key. No signup. 60 requests/minute, anonymous GET. Every response is a dated observation with its source — not a score, not advice. Base URL https://lastseen.dev.
# one component (owner/repo)
curl https://lastseen.dev/api/v1/entity/actions/checkout
# everything held under a GitHub owner/org
curl https://lastseen.dev/api/v1/org/actions
# a whole manifest at once (names-only body)
curl -X POST https://lastseen.dev/api/v1/manifest \
-H 'content-type: application/json' \
-d '{"channel":"api","components":[{"name":"actions/checkout","kind":"github-action"}]}'
# self-describing API docs (JSON)
curl https://lastseen.dev/api/v1/docsA single-component response carries the lateststate, the dated series behind it, the sourceofrecord, and interval-censoring notes — enough to re-check any verdict against GitHub yourself. This is the recurring path:** wire GET /api/v1/entity/{owner}/{repo} into CI and a dead dependency shows up on the build that introduces it, not months later.
Contract
instead", never a composite score, never a ranking by preference, never urgency language.
- Lookups, not advice. Every answer is a dated observation with its source. Never "use X
fabricated result. A network/store error degrades (try later); it is never read as "dead".
- Fails closed. An unknown or fabricated subject returns a clean not_observed — never a
HTTP 404 is a deletion.
- Absence ≠ gone. No record means "not checked", never "deleted". Only an authoritative
States
alive (≤180d since last commit) · dormant (180–365d) · abandoned (>365d) · archived (repo archived) · deleted (authoritative HTTP 404) · eol (declared end-of-life) · unknown-stale (the observation the verdict rests on is older than the 180-day threshold and was not re-verified — no state asserted; not a death) · notobserved (403 / 429 / timeout / not held — not** dead).
2. Run it as an MCP server
A pure-standard-library stdio wrapper over the API above — no mcp package, no requests, no FastAPI/Starlette, nothing that can conflict with a host app. It speaks JSON-RPC 2.0 over stdio and calls the free API over urllib.
Install
pipx install lastseen-mcp
# or run without installing:
uvx lastseen-mcpRequires Python ≥ 3.10. No dependencies.
Add to an MCP client
{
"mcpServers": {
"lastseen": { "command": "lastseen-mcp" }
}
}(If you use uvx, set "command": "uvx", "args": ["lastseen-mcp"].)
Tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
lastseen mortality: common questions
- Is lastseen mortality MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the lastseen mortality safety report
- How do I install lastseen mortality?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does lastseen mortality need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is lastseen mortality maintained?
- The last commit was 86 days ago (2026-08-10). The latest release is v0.1.2.
- What can I use instead of lastseen mortality?
- Servers from other publishers that do the same job: Docker MCP Server, Gnt MCP server and Pare Github MCP server.
Alternatives to lastseen mortality
Same job from other publishers: the closest match first, then the best rated.
- Docker MCP ServerManage Docker (containers, images, Compose, Swarm, registries) via the Docker SDK and CLI.not reviewedGrowingA
- GntGit-native policy layer for AI agents: check_action verdicts against rules approved via PR.not reviewedGrowingA
- Pare GithubPare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.not reviewedGrowingA
- GitDiagramArchitecture diagrams, explanations and Mermaid source for public GitHub repositories.not reviewedEstablishedA
- GitHubConnect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.not reviewedEstablishedA