lastseen mortality
PYPI · LASTSEEN-MCP · SCANNED SEP 20
Check whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 40 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 351 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the lastseen mortality MCP server?
lastseen mortality runs locally as a PyPI package, launched with uvx lastseen-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · lastseen-mcp
claude mcp add dev-lastseen-mortality -- uvx lastseen-mcp
{
"mcpServers": {
"dev-lastseen-mortality": {
"command": "uvx",
"args": [
"lastseen-mcp"
]
}
}
} {
"servers": {
"dev-lastseen-mortality": {
"command": "uvx",
"args": [
"lastseen-mcp"
]
}
}
} codex mcp add dev-lastseen-mortality -- uvx lastseen-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-lastseen-mortality": {
"type": "local",
"command": [
"uvx",
"lastseen-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-lastseen-mortality --command uvx --arg lastseen-mcp
mcp_servers:
dev-lastseen-mortality:
command: "uvx"
args: ["lastseen-mcp"] {
"McpServers": {
"dev-lastseen-mortality": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"lastseen-mcp"
]
}
}
} assistant mcp add dev-lastseen-mortality -t stdio -c uvx -a lastseen-mcp
{
"mcpServers": {
"dev-lastseen-mortality": {
"command": "uvx",
"args": [
"lastseen-mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.83 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
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 Sept 2026 · Analysed pypi/lastseen-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_entity ~104
Dated survival observation(s) for ONE owner/repo (e.g. 'actions/checkout') from lastseen.dev. Returns the recorded state series with dates and sources. Lookup, not advice. Unknown/fabricated subjects return a clean not_observed, never a fabricated result.
| Name | Type | Req | Description |
|---|---|---|---|
| live | boolean | – | optionally attach a live GitHub read (absence != gone); default false |
| slug | string | yes | owner/repo, e.g. 'actions/checkout' |
No output schema declared.
No examples provided.
check_manifest ~71
Parse a pasted manifest (GitHub Actions workflow `uses:` refs, or a list of owner/repo lines) and return the dated survival state per component from lastseen.dev. Components not held are reported as not_observed. Lookup, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| paste | string | yes | raw manifest text to parse |
No output schema declared.
No examples provided.
check_org ~57
Dated survival states across the components referenced under an ORG (a github owner slug), from lastseen.dev. Org-level only. Lookup, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | github owner/org slug, e.g. 'actions' |
No output schema declared.
No examples provided.
survival_profile ~90
Ranked survival profile for a CATEGORY. NOTE: category ranking is not available over the free HTTP API — this returns an honest not_supported result and points to the per-entity/org/manifest lookups and the CC-BY dumps.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | e.g. 'mcp', 'github-action', 'github-repo' |
| limit | integer | – | max ranked rows (default 50) |
No output schema declared.
No examples provided.
What is the lastseen mortality MCP server?
lastseen mortality is an MCP server listed in the public MCP registry as dev.lastseen/mortality. Check whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned. This page covers its PyPI package (lastseen-mcp).
Is the lastseen mortality MCP server safe to use?
lastseen mortality scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the lastseen mortality MCP server expose?
lastseen mortality exposes 4 tools: check_entity, check_org, check_manifest, survival_profile. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Is the lastseen mortality MCP server still maintained?
lastseen mortality is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the lastseen mortality MCP server under?
lastseen mortality declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.