U
Umair/stalemap
Tell your coding agent which dependencies changed after its training cutoff. Diffs types and changelogs, writes a short block into AGENTS.md / CLAUDE.md.
SECURITY.md ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"umair-stalemap": {
"command": "npx",
"args": ["-y", "stalemap@latest", "mcp"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"umair-stalemap": {
"command": "npx",
"args": ["-y", "stalemap@latest", "mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio umair-stalemap -- npx -y stalemap@latest mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 109 ★ · Umair/stalemap · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 109 ★ · 23 sources · mcp
- Install
npx -y stalemap@latest mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y stalemap@latest mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Umair/stalemap；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.Install ·
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Example ·
How it works ·
Results ·
Changelog
Coding agents learn libraries from training data that stops at a cutoff date. When your project pins newer versions, the agent writes code for the old API: maxSteps against AI SDK 7, requirederror against zod 4, middleware.ts against Next 16.
stalemap finds the dependencies that changed after your model's training cutoff and tells the agent what changed, in three ways:
Notes: a short, ranked list of changes written into AGENTS.md or CLAUDE.md, so the agent reads it before it starts.
Edit-time guard: after each edit, the project's own type-check. If the code uses an API that changed after the cutoff, the agent gets the compiler error and the matching note (or the release-note or upgrade-guide section that explains it) right away. It also reports the code that still compiles but uses something that moved.
searchchanges: an MCP tool the agent can ask in its own words, such as "resolve alias in next.config", to get the matching changes with their sources.
It works for JavaScript and TypeScript projects, with Claude Code, Cursor, Codex, OpenCode or any MCP client.
In a blind, pre-registered benchmark of 66 tasks built from changes released after June 2026, claude-sonnet-5-5 agents passed 89% of sessions with stalemap, against 68% with no help and 73% with a plain tsc --noEmit hook after each edit. See Results.
## Status
npm: the latest release is stalemap 0.4.1: the build tested in held-out v4 (0.4.0), plus a one-line footer in the notes block. npx stalemap, the Claude Code plugin and the GitHub Action all run it. See the changelog.
The project is early, and maintained by one person.
## Install
### Claude Code plugin
text
/plugin marketplace add Umair/stalemap
/plugin install stalemap@stalemap
The plugin adds:
a SessionStart hook that puts the notes into Claude's context for the session's model (on startup, after /clear and after compaction; it writes no files);
a PostToolUse hook that runs the edit-time guard after each Write or Edit;
the stalemap MCP server and two skills (/stalemap:sync writes the notes block; upgrade tells Claude to look up a package's changes before using or upgrading it).
The hooks and the MCP server run npx -y stalemap@latest, so they use the latest npm release. Its MCP tools are searchchanges, packagechanges, projectchanges and checknotes.
### Command line
bash
npx stalemap # preview what changed and the block it would write
npx stalemap sync # write the block into AGENTS.md or CLAUDE.md
npx stalemap check # for CI: exit 1 when the block is missing or stale
npx stalemap guard src//.ts # run the guard by hand
The block sits between and . Text outside it is never touched. Claude Code reads CLAUDE.md; if your notes live in AGENTS.md, add @AGENTS.md to CLAUDE.md or pass --target CLAUDE.md.
### Other agents: setup --agent
bash
stalemap setup --agent cursor # or codex, opencode, claude
stalemap setup --agent codex --dry-run # print the changes, write nothing
One command per agent writes the notes, registers the MCP server and installs the guard as the agent's post-edit hook, as project files you can commit. It merges into existing config files, keeps entries it didn't write, and re-running it changes nothing.
How it works ·
Results ·
Changelog
Coding agents learn libraries from training data that stops at a cutoff date. When your project pins newer versions, the agent writes code for the old API: maxSteps against AI SDK 7, requirederror against zod 4, middleware.ts against Next 16.
stalemap finds the dependencies that changed after your model's training cutoff and tells the agent what changed, in three ways:
Notes: a short, ranked list of changes written into AGENTS.md or CLAUDE.md, so the agent reads it before it starts.
Edit-time guard: after each edit, the project's own type-check. If the code uses an API that changed after the cutoff, the agent gets the compiler error and the matching note (or the release-note or upgrade-guide section that explains it) right away. It also reports the code that still compiles but uses something that moved.
searchchanges: an MCP tool the agent can ask in its own words, such as "resolve alias in next.config", to get the matching changes with their sources.
It works for JavaScript and TypeScript projects, with Claude Code, Cursor, Codex, OpenCode or any MCP client.
In a blind, pre-registered benchmark of 66 tasks built from changes released after June 2026, claude-sonnet-5-5 agents passed 89% of sessions with stalemap, against 68% with no help and 73% with a plain tsc --noEmit hook after each edit. See Results.
## Status
npm: the latest release is stalemap 0.4.1: the build tested in held-out v4 (0.4.0), plus a one-line footer in the notes block. npx stalemap, the Claude Code plugin and the GitHub Action all run it. See the changelog.
The project is early, and maintained by one person.
## Install
### Claude Code plugin
text
/plugin marketplace add Umair/stalemap
/plugin install stalemap@stalemap
The plugin adds:
a SessionStart hook that puts the notes into Claude's context for the session's model (on startup, after /clear and after compaction; it writes no files);
a PostToolUse hook that runs the edit-time guard after each Write or Edit;
the stalemap MCP server and two skills (/stalemap:sync writes the notes block; upgrade tells Claude to look up a package's changes before using or upgrading it).
The hooks and the MCP server run npx -y stalemap@latest, so they use the latest npm release. Its MCP tools are searchchanges, packagechanges, projectchanges and checknotes.
### Command line
bash
npx stalemap # preview what changed and the block it would write
npx stalemap sync # write the block into AGENTS.md or CLAUDE.md
npx stalemap check # for CI: exit 1 when the block is missing or stale
npx stalemap guard src//.ts # run the guard by hand
The block sits between and . Text outside it is never touched. Claude Code reads CLAUDE.md; if your notes live in AGENTS.md, add @AGENTS.md to CLAUDE.md or pass --target CLAUDE.md.
### Other agents: setup --agent
bash
stalemap setup --agent cursor # or codex, opencode, claude
stalemap setup --agent codex --dry-run # print the changes, write nothing
One command per agent writes the notes, registers the MCP server and installs the guard as the agent's post-edit hook, as project files you can commit. It merges into existing config files, keeps entries it didn't write, and re-running it changes nothing.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/umair-stalemap/)
- Source
- awesome · https://github.com/Umair/stalemap
- Browse by field
- MCP servers
- Traction
- 109 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.