io.github.jmshinhwa/gnu-global-cpp-vscode-config-pack

@readystack/gnu-global-cpp-vscode-config-pack

Is the io.github.jmshinhwa/gnu-global-cpp-vscode-config-pack MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.

21 rules that read the values in a shared .vscode folder, plus 45 snippets. VS Code loads a wrong va

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

3tools

359tokens in Claude Opus 5.5

0.2 %of Claude's 200k window

0.1×the median server

94 msto initialize

5 msto list tools

Run it: npx -y @readystack/gnu-global-cpp-vscode-config-pack@0.1.2 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: @readystack/gnu-global-cpp-vscode-config-pack 1.0.0
Capabilities: tools
Instructions: none
Of a 1M window: <0.1 % of a 1M context window
Count: 359 tokens in Claude Opus 5.5, exact, measured 2026-10-17. With the Claude Code prefix mcp__…__ on each tool name: 428. The o200k_base estimate is 205. Counted again when the tool definitions change. Method.
Repository: https://github.com/jmshinhwa/readystack-themes
Registry: active, updated 2026-09-19 · 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.75×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
check_dir	142	81	40 %
check_text	126	72	35 %
check_file	91	52	25 %

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

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

Servers that mention config.

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.