mcpcost

io.github.Servosity/hudu-mcp

Hudu MCP

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

Every Hudu cmdlet, plus an offline SQLite mirror, cross-entity audits, and agent-native output no

alive probed 2026-11-14

37tools
34ktokens in Claude Opus 5.5
17.2 %of Claude's 200k window
14×the median server
72 msto initialize
11 msto list tools
Bundle
https://github.com/Servosity/msp-skills/releases/download/hudu-v0.1.21/hudu-mcp.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host
github.com
Reports itself as
Hudu 0.1.21
Capabilities
tools
Instructions
none
Of a 1M window
3.4 % of a 1M context window
Count
34k tokens in Claude Opus 5.5, exact, measured 2026-11-14. With the Claude Code prefix mcp__…__ on each tool name: 35k. The o200k_base estimate is 21k. Counted again when the tool definitions change. Method.
Repository
https://github.com/servosity/msp-skills
Registry
active, updated 2026-11-14 · registry entry
Changes
2 recorded, reachable in 2 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.67×.

Tool≈ Claude tokenso200k estimateShare of this server
sync1 9561 1746 %
teach1 3007804 %
audit_summary1 2357414 %
learnings_list1 1837103 %
teach_pattern1 1737043 %

Compare this server with others.

More servers

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

Servers that mention hudu.

History

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

ProbedResultInitToolsClaudeo200k
2026-11-14 08:10alive62 ms3734k21k
2026-10-29 07:50alive72 ms3734k21k

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