stalemap
NPM · STALEMAP
Tells coding agents which npm dependencies changed after their training cutoff, and what changed.
Available components
Last scanned (21 hours ago)
Scores higher than 50% of npm servers
Category Developer Tools
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1024 tokens (~256/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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
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.
- 4 Nov 26 +7
- Stability: unverified → 0.50 ▲ functional
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 53
First indexed and scored.
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 4 Nov 2026 · Analysed npm/stalemap@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 36 |
| 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_notes Is the stalemap block in AGENTS.md / CLAUDE.md current? ~109
Check whether the project's stalemap notes block is missing or out of date for the current dependencies and model. Offline and fast.
| Name | Type | Req | Description |
|---|---|---|---|
| cutoff | string | – | Training cutoff (YYYY-MM or YYYY-MM-DD) to use instead of a model id. |
| cwd | string | – | Project directory (default: the server's working directory) |
| model | string | – | Your own model id (e.g. claude-opus-5-5). Defaults to the model configured in the coding agent's settings. |
No output schema declared.
No examples provided.
package_changes What changed in a package since my training data ~203
Before writing or changing code that calls a third-party npm package, call this to learn which of its APIs changed after your training cutoff: removed or renamed exports, new required parameters, removed options, deprecations with replacements, and breaking changelog entries. Pass the version the project pins (from package.json or the lockfile) when you know it.
| Name | Type | Req | Description |
|---|---|---|---|
| apis | array | – | Exports you are about to use, to rank changes to them first |
| cutoff | string | – | Training cutoff (YYYY-MM or YYYY-MM-DD) to use instead of a model id. |
| model | string | – | Your own model id (e.g. claude-opus-5-5). Defaults to the model configured in the coding agent's settings. |
| name | string | yes | npm package name, e.g. `ai`, `next`, `@tanstack/react-query` |
| version | string | – | Version or range the project uses (default: latest) |
No output schema declared.
No examples provided.
project_changes Dependency changes since my training data (whole project) ~153
Scan a JavaScript/TypeScript project and list the dependencies it imports that changed after your training cutoff, with the specific API changes that affect this code. Use it at the start of a task in an unfamiliar project, or after dependencies were upgraded.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Check every direct dependency, not only imported ones |
| cutoff | string | – | Training cutoff (YYYY-MM or YYYY-MM-DD) to use instead of a model id. |
| cwd | string | – | Project directory containing package.json (default: the server's working directory) |
| model | string | – | Your own model id (e.g. claude-opus-5-5). Defaults to the model configured in the coding agent's settings. |
No output schema declared.
No examples provided.
search_changes Search what changed in this project's dependencies ~406
Searches what changed in this project's dependencies since your training data, for the versions it has installed: removed, renamed and moved APIs, options and config keys, new required arguments, changed defaults and behavior, file conventions. Sources are the installed versions' type declarations, every release-note item since your training data and the packages' upgrade guides; each result says which. Call it BEFORE your first edit whenever the task touches a library's API or a config file, even for libraries you know well and even when you're sure: your training data predates these versions, and the API you remember may be gone. Also call it when a type error or warning names a package's API. Describe what you are about to do in your own words; old names are fine and often best. Good: 'resolve alias for a module in next.config', 'middleware that redirects with cookies', 'zod error message per parse', 'tsconfig baseUrl paths aliases', 'mongoose pre save hook next'. Bad (too vague): 'config', 'errors'. Keep one topic per call; call again for another. Do not call it more than 4 times for one question.
| Name | Type | Req | Description |
|---|---|---|---|
| cutoff | string | – | Training cutoff (YYYY-MM or YYYY-MM-DD) to use instead of a model id. |
| cwd | string | – | Project directory containing package.json (default: the server's working directory) |
| limit | integer | – | Results to return (default 8) |
| model | string | – | Your own model id (e.g. claude-opus-5-5). Defaults to the model configured in the coding agent's settings. |
| package | string | – | Limit to one npm package of this project, e.g. `next`, `zod`, `typescript` (default: all of them) |
| query | string | yes | What you're about to do or look up, in your own words: an API, option, config key, file or error message. Old names are fine. |
No output schema declared.
No examples provided.
How do I install the stalemap MCP server?
stalemap runs locally as an npm package, launched with npx -y stalemap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · stalemap
claude mcp add umair-stalemap -- npx -y stalemap
What is the stalemap MCP server?
stalemap is an MCP server listed in the public MCP registry as io.github.Umair/stalemap. Tells coding agents which npm dependencies changed after their training cutoff, and what changed. This page covers its npm package (stalemap).
Is the stalemap MCP server safe to use?
stalemap scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 stalemap MCP server expose?
stalemap exposes 4 tools: search_changes, package_changes, project_changes, check_notes. Their descriptions and schemas cost roughly 871 tokens of context every time the server is loaded.
Is the stalemap MCP server still maintained?
stalemap is still listed as active in the MCP registry. We last reached this channel on 4 November 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 stalemap MCP server under?
stalemap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.