lastseen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_entityA | 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. |
| check_orgA | Dated survival states across the components referenced under an ORG (a github owner slug), from lastseen.dev. Org-level only. Lookup, not advice. |
| check_manifestA | Parse a pasted manifest (GitHub Actions workflow |
| survival_profileA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct input scope: single owner/repo, org slug, pasted manifest, and category profile. The scopes are clearly described, and the batch manifest tool is unlikely to be confused with the single-entity or org-level lookups.
Three of the four tools follow the consistent check_<scope> pattern (check_entity, check_org, check_manifest). survival_profile breaks the verb_noun pattern, but it is a single recognizable exception rather than a systemic inconsistency.
Four tools is a reasonable size for a narrow read-only lookup service. However, survival_profile is effectively an unsupported stub that always returns not_supported, so it pads the count without adding a working capability.
The core lookup workflows are covered: single entity, org-wide, and manifest-based batch checks. The main gap is category-level ranking, which survival_profile cannot provide, though the description points to alternative lookups and external dumps as workarounds.