io.github.hybridforgelab/specwise-mcp

specwise

Is the io.github.hybridforgelab/specwise-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-07.

OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs for AI agents.

alive probed 2026-11-15 · unchanged since 2026-11-07

3tools

1.5ktokens in Claude Opus 5.5

0.8 %of Claude's 200k window

0.6×the median server

1.2 sto initialize

3 msto list tools

Run it: uvx hybridforgelab-specwise-mcp@0.2.3 (stdio, probed in a container with the network off)
Host: pypi.org
Reports itself as: specwise
Capabilities: prompts, resources, tools
Instructions: 471 characters
Of a 1M window: 0.2 % of a 1M context window
Count: 1.5k tokens in Claude Opus 5.5, exact, measured 2026-11-03. With the Claude Code prefix mcp__…__ on each tool name: 1.5k. The o200k_base estimate is 836. Counted again when the tool definitions change. Method.
Repository: https://github.com/hybridforgelab/specwise-mcp
Website: https://specwise.hybridforgelab.com/integration.html#mcp-server
Registry: deprecated, updated 2026-11-06 · registry entry

Most expensive tools

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

Tool	≈ Claude tokens	o200k estimate	Share of this server
diff_openapi	641	357	43 %
validate_json_schema	539	300	36 %
validate_openapi	322	179	21 %

These registry entries have the same tool names and the same schema sizes.

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

Servers that mention specwise or validation or breaking.

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

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