# stalemap (npm · stalemap)

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

- Trust score: 76/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `stalemap`: 76/100 (this document), [markdown](https://verifymcp.io/servers/umair-stalemap/stalemap.md), [page](https://verifymcp.io/servers/umair-stalemap/stalemap)

## Channel facts

- Registry: `npm`
- Package: `stalemap`
- Version: `0.4.1`
- 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-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 36 of 109 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/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 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 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.

### Claude

```bash
claude mcp add umair-stalemap -- npx -y stalemap
```

### Cursor

```json
{
  "mcpServers": {
    "umair-stalemap": {
      "command": "npx",
      "args": [
        "-y",
        "stalemap"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "umair-stalemap": {
      "command": "npx",
      "args": [
        "-y",
        "stalemap"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add umair-stalemap -- npx -y stalemap
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "umair-stalemap": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stalemap"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add umair-stalemap --command npx --arg -y --arg stalemap
```

### Hermes

```yaml
mcp_servers:
  umair-stalemap:
    command: "npx"
    args: ["-y", "stalemap"]
```

### Netclaw

```json
{
  "McpServers": {
    "umair-stalemap": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stalemap"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add umair-stalemap -t stdio -c npx -a -y stalemap
```

### Other

```json
{
  "mcpServers": {
    "umair-stalemap": {
      "command": "npx",
      "args": [
        "-y",
        "stalemap"
      ]
    }
  }
}
```

## 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-11-05 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 75, +7)

- [functional improvement] Stability: unverified → 0.50

### 2026-10-21 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-20 (score 53)

First indexed and scored.

## MCP tools (4)

### `search_changes` (~406 tokens)

Search what changed in this project's dependencies

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.

Input parameters:

- `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, required): 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.

### `package_changes` (~203 tokens)

What changed in a package since my training data

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.

Input parameters:

- `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, required): npm package name, e.g. `ai`, `next`, `@tanstack/react-query`
- `version` (string): Version or range the project uses (default: latest)

### `project_changes` (~153 tokens)

Dependency changes since my training data (whole project)

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.

Input parameters:

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

### `check_notes` (~109 tokens)

Is the stalemap block in AGENTS.md / CLAUDE.md current?

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

Input parameters:

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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/umair-stalemap/stalemap#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 53

## Common questions

### 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 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 5 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.

## Links

- npm package: https://www.npmjs.com/package/stalemap
- Socket report: https://socket.dev/npm/package/stalemap
- Repository: https://github.com/Umair/stalemap
- Website: https://stalemap.com/
- Changelog RSS feed: https://verifymcp.io/servers/umair-stalemap/stalemap.xml
- Changelog JSON feed: https://verifymcp.io/servers/umair-stalemap/stalemap.json
- HTML version of this page: https://verifymcp.io/servers/umair-stalemap/stalemap