io.github.dan-fetch-studio/tidyports

tidyports

Is the io.github.dan-fetch-studio/tidyports MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.

See and kill the dev servers your coding agents leave running, and get collision-free ports.

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

4tools

665tokens in Claude

0.3 %of Claude's 200k window

0.3×the median server

346 msto initialize

10 msto list tools

Run it: npx -y @tidyports/mcp@0.1.2 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: tidyports 0.1.0
Capabilities: tools
Instructions: none
Of a 1M window: <0.1 % of a 1M context window
Count: 665 tokens in Claude, exact, measured 2026-10-25. With the Claude Code prefix mcp__…__ on each tool name: 701. The o200k_base estimate is 396. Counted again when the tool definitions change. Method.
Repository: https://github.com/dan-fetch-studio/tidyports-integrations
Registry: active, updated 2026-07-26 · 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.68×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
free_port	213	127	32 %
alloc_port	165	98	25 %
list_servers	148	88	22 %
kill_port	139	83	21 %

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

Servers that mention collision or running.

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

Probed	Result	Init	Tools	Claude	o200k
2026-10-25 06:52	alive	384 ms	4	665	396
2026-10-18 06:39	alive	346 ms	4		396

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.