mcpcost

io.github.BargLabs/dunstan

Dunstan

Is the Dunstan MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-15.

Checks a coding agent's handback against the pull request's GitHub record. No model decides.

alive probed 2026-11-15

3tools
3.2ktokens in Claude Opus 5.5
1.6 %of Claude's 200k window
1.3×the median server
194 msto initialize
10 msto list tools
Run it
npx -y dunstan@0.1.22 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
dunstan 0.1.22
Capabilities
tools
Instructions
787 characters
Of a 1M window
0.3 % of a 1M context window
Count
3.2k tokens in Claude Opus 5.5, exact, measured 2026-11-12. With the Claude Code prefix mcp__…__ on each tool name: 3.2k. The o200k_base estimate is 2.0k. Counted again when the tool definitions change. Method.
Repository
https://github.com/BargLabs/dunstan
Website
https://barglabs.ai/dunstan
Registry
active, updated 2026-11-14 · registry entry
Changes
3 recorded, reachable in 3 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.60×.

Tool≈ Claude tokenso200k estimateShare of this server
dunstan_template_handback1 7761 10756 %
dunstan_check_handback1 12570136 %
dunstan_suggest_declarations2651658 %

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention handback or against.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-11-12 08:53alive207 ms33.2k2.0k
2026-11-04 08:02alive214 ms32.2k1.4k
2026-10-17 06:14alive194 ms2961613

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher