mcpcost

io.github.JTCHE/houdini-mcp

Houdini MCP

Is the Houdini MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.

Connect agents to SideFX Houdini: edit the scene, cook, render, see the viewport, read the docs.

alive probed 2026-11-15 · unchanged since 2026-10-31

20tools
30ktokens in Claude Opus 5.5
14.9 %of Claude's 200k window
12×the median server
1.9 sto initialize
9 msto list tools
Run it
uvx houdini-mcp-server@0.8.1 (stdio, probed in a container with the network off)
Host
pypi.org
Reports itself as
HoudiniMCP
Capabilities
prompts, resources, tools
Instructions
5 382 characters
Of a 1M window
3.0 % of a 1M context window
Count
30k tokens in Claude Opus 5.5, exact, measured 2026-10-31. With the Claude Code prefix mcp__…__ on each tool name: 30k. The o200k_base estimate is 20k. Counted again when the tool definitions change. Method.
Repository
https://github.com/JTCHE/houdini-mcp
Registry
active, updated 2026-10-23 · registry entry
Changes
2 recorded, reachable in 1 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.51×.

Tool≈ Claude tokenso200k estimateShare of this server
geometry_inspect4 3622 89415 %
node_edit3 2792 17511 %
capture3 1142 06610 %
parm_set2 4471 6238 %
node_inspect1 9461 2917 %

Compare this server with others.

More servers

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

Servers that mention houdini or viewport or connect.

History

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

ProbedResultInitToolsClaudeo200k
2026-10-31 07:35alive1.9 s2030k20k
2026-10-17 06:21install failed

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