# lastseen mortality (pypi · lastseen-mcp)

Check whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned.

- Trust score: 84/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `lastseen-mcp`: 84/100 (this document), [markdown](https://verifymcp.io/servers/dev-lastseen-mortality/lastseen-mcp.md), [page](https://verifymcp.io/servers/dev-lastseen-mortality/lastseen-mcp)

## Channel facts

- Registry: `pypi`
- Package: `lastseen-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 40 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 351 tokens (~87/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add dev-lastseen-mortality -- uvx lastseen-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-lastseen-mortality": {
      "command": "uvx",
      "args": [
        "lastseen-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-lastseen-mortality": {
      "command": "uvx",
      "args": [
        "lastseen-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-lastseen-mortality -- uvx lastseen-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-lastseen-mortality": {
      "type": "local",
      "command": [
        "uvx",
        "lastseen-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-lastseen-mortality --command uvx --arg lastseen-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-lastseen-mortality:
    command: "uvx"
    args: ["lastseen-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-lastseen-mortality": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "lastseen-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-lastseen-mortality -t stdio -c uvx -a lastseen-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-lastseen-mortality": {
      "command": "uvx",
      "args": [
        "lastseen-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 84, +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.

### 2026-09-18 (score 83, −3)

- [functional] Stability: pass → 0.83

### 2026-09-17 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 85, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-14 (score 69, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-13 (score 84, +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.

### 2026-09-12 (score 83, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-11 (score 83, +1)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (4)

### `check_entity` (~104 tokens)

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.

Input parameters:

- `live` (boolean): optionally attach a live GitHub read (absence != gone); default false
- `slug` (string, required): owner/repo, e.g. 'actions/checkout'

### `check_org` (~57 tokens)

Dated survival states across the components referenced under an ORG (a github owner slug), from lastseen.dev. Org-level only. Lookup, not advice.

Input parameters:

- `name` (string, required): github owner/org slug, e.g. 'actions'

### `check_manifest` (~71 tokens)

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.

Input parameters:

- `paste` (string, required): raw manifest text to parse

### `survival_profile` (~90 tokens)

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.

Input parameters:

- `category` (string, required): e.g. 'mcp', 'github-action', 'github-repo'
- `limit` (integer): max ranked rows (default 50)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-lastseen-mortality/lastseen-mcp#diagnostics

## Score history

- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 83
- 2026-09-17: 86
- 2026-09-16: 85
- 2026-09-15: 85
- 2026-09-14: 69
- 2026-09-13: 84
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 86
- 2026-09-08: 85
- 2026-09-07: 85
- 2026-09-06: 84
- 2026-09-05: 84
- 2026-09-04: 83
- 2026-09-03: 83
- 2026-09-02: 82
- 2026-09-01: 82
- 2026-08-31: 81
- 2026-08-30: 81
- 2026-08-29: 80
- 2026-08-28: 80
- 2026-08-27: 80
- 2026-08-26: 79
- 2026-08-25: 78
- 2026-08-24: 77
- 2026-08-23: 77
- 2026-08-22: 76

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/lastseen-mcp/
- Socket report: https://socket.dev/pypi/package/lastseen-mcp
- Repository: https://github.com/agentidx/lastseen-mcp
- Website: https://lastseen.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-lastseen-mortality/lastseen-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-lastseen-mortality/lastseen-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-lastseen-mortality/lastseen-mcp