io.github.mrfentmen/runtime-support-mcp

runtime-support-mcp

Is the io.github.mrfentmen/runtime-support-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-09.

Summarize runtime declarations across local m MCP: real tools for real work.

alive probed 2026-11-14 · unchanged since 2026-11-09

3tools

540tokens in Claude Opus 5.5

0.3 %of Claude's 200k window

0.2×the median server

337 msto initialize

8 msto list tools

Run it: npx -y runtime-support-mcp@1.0.1 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: runtime-support-mcp 1.0.0
Capabilities: tools
Instructions: none
Of a 1M window: <0.1 % of a 1M context window
Count: 540 tokens in Claude Opus 5.5, exact, measured 2026-11-09. With the Claude Code prefix mcp__…__ on each tool name: 582. The o200k_base estimate is 300. Counted again when the tool definitions change. Method.
Repository: https://github.com/mrfentmen/awesome-servers
Registry: active, updated 2026-11-08 · 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.80×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
runtime_support_matrix	203	113	38 %
runtime_constraint_spread	193	107	36 %
inspect_runtime_support	144	80	27 %

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

Servers that mention runtime.

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

Probed	Result	Init	Tools	Claude	o200k
2026-11-09 08:49	alive	217 ms	3	540	300
2026-10-16 06:27	alive	337 ms	1	148	80

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.