mcpcost

io.github.Alpha-Park/genpark-voice-vad

genpark-voice-vad

Is the genpark-voice-vad MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.

Energy and transcript heuristics for voice turn endpoint detection.

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

4tools
465tokens in Claude Opus 5.5
0.2 %of Claude's 200k window
0.2×the median server
76 msto initialize
2 msto list tools
Bundle
https://github.com/Alpha-Park/genpark-voice-turn-taking-endpoint-detector-skill/releases/download/v1.0.1/genpark-voice-vad.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host
github.com
Reports itself as
genpark-voice-vad 1.0.1
Capabilities
tools
Instructions
none
Of a 1M window
<0.1 % of a 1M context window
Count
465 tokens in Claude Opus 5.5, exact, measured 2026-10-30. With the Claude Code prefix mcp__…__ on each tool name: 521. The o200k_base estimate is 222. Counted again when the tool definitions change. Method.
Repository
https://github.com/Alpha-Park/genpark-voice-turn-taking-endpoint-detector-skill
Registry
active, updated 2026-09-27 · registry entry

Most expensive tools

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

Tool≈ Claude tokenso200k estimateShare of this server
analyze_turn_status1868940 %
calibrate_acoustic_thresholds1115324 %
predict_semantic_closure944520 %
run_benchmark_turn_detection733516 %

Compare this server with others, or with the servers that share its tool set.

Same tool set as 1 other server

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

More servers

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

Servers that mention genpark.

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