stalemap
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Transport (tested 2026-10-26): stdio
Score 70/100 · Tools 4 · Token cost ~1,043 · Compare · Last tested 2026-10-26 · Version tested 0.4.1 · Package stalemap · Repo Umair/stalemap
Summary: stalemap completed an MCP handshake without credentials and exposed 4 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 4
- Context cost
- 1,043 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 141 tokens; raw tools/list total 1,184. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key to connect (handshake passed)
- Tested
- 2026-10-26
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install stalemap (Node 20, Linux) succeeded in 3s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 4 tools listed in 0.9s. |
| maintenance | pass | 25 | Repo pushed 5 days before test; 103 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Schema context cost: ~1,043 tokens for 4 tools (4,712 bytes) · about 13% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-10-26
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 4 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Checked on 2026-10-27 for version 0.4.1 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.
No published advisories found in OSV and GitHub advisories for stalemap 0.4.1 as of 2026-10-27. This is not a security audit.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-10-26 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
ee1730efb331: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "stalemap",
"version": "0.4.1",
"registry": "npm",
"status": "working",
"tested": "2026-10-26",
"tools_count": 4,
"tools_schema_tokens_est": 1043,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install stalemap` (Node 20, Linux) succeeded in 3s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 4 tools listed in 0.9s."
],
"maintenance": [
"pass",
25,
"Repo pushed 5 days before test; 103 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y stalemap mcp
Tools listed
search_changes, package_changes, project_changes, check_notes
Quick config
{
"mcpServers": {
"stalemap": {
"command": "npx",
"args": [
"-y",
"stalemap",
"mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install stalemap(Node 20). This is the exact command we ran on 2026-10-26. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (4 in our test).
{
"mcpServers": {
"stalemap": {
"command": "npx",
"args": [
"-y",
"stalemap",
"mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is stalemap deprecated?
No. stalemap was not deprecated or archived when we last tested it on 2026-10-26.
What replaces stalemap?
Nothing; stalemap is not deprecated as of 2026-10-26.
Does stalemap need an API key?
No. It completed an MCP handshake with no credentials and listed 4 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.