MCP.Market

stalemap MCP server

by Umair·io.github.Umair/stalemap·v0.4.1·103 stars
No reviews yet

Tells coding agents which npm dependencies changed after their training cutoff, and what changed.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

103 stars0 downloads/wk

Reviews

Write one

Nobody has reviewed stalemap yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

stalemap tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_notes

    Check whether the project's stalemap notes block is missing or out of date for the current dependencies and model. Offline and fast.

  • package_changes

    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.

  • project_changes

    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.

  • search_changes

Public scan report

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan61 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How stalemap compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
103
more than 95% of 28,688 servers

What its tools let an agent do: 4 read

Install stalemap in Claude Code, Cursor or VS Code

Runs npx -y stalemap on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add stalemap -- npx -y stalemap
Add to Cursor

What the publisher says

From the stalemap repository's README, as published. We do not edit it. Read it on GitHub

Install · 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, required_error 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

/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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

stalemap: common questions

Is stalemap MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the stalemap safety report
How do I install stalemap?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does stalemap need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is stalemap maintained?
The last commit was 14 days ago (2026-10-21). The latest release is v0.4.1.
How does stalemap compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.