mcpcost

io.github.eduplopez/mcp-voice-summary

VoiceSummaryServer

Is the io.github.eduplopez/mcp-voice-summary MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-01.

Reads a summary out loud when an AI coding task finishes. Offline or neural voices.

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

3tools
532tokens in Claude
0.3 %of Claude's 200k window
0.2×the median server
3.0 sto initialize
6 msto list tools
Run it
uvx mcp-voice-summary@0.1.1 (stdio, probed in a container with the network off)
Host
pypi.org
Reports itself as
VoiceSummaryServer 0.1.1
Capabilities
prompts, resources, tools
Instructions
none
Of a 1M window
<0.1 % of a 1M context window
Count
532 tokens in Claude, exact, measured 2026-10-25. With the Claude Code prefix mcp__…__ on each tool name: 574. The o200k_base estimate is 323. Counted again when the tool definitions change. Method.
Repository
https://github.com/eduplopez/mcp-voice-summary
Website
https://github.com/eduplopez/mcp-voice-summary
Registry
active, updated 2026-10-04 · 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.65×.

Tool≈ Claude tokenso200k estimateShare of this server
set_language25415448 %
speak_summary1559429 %
list_voices1247523 %

Compare this server with others.

More servers

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

Servers that mention summary.

History

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

ProbedResultInitToolsClaudeo200k
2026-10-25 06:53alive2.9 s3532323
2026-10-18 06:40alive3.0 s3323

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