io.github.sapiom/mcp
sapiom-dev
Local Sapiom developer MCP for authoring, testing, deploying, and inspecting agents.
alive probed 2026-10-19
27tools
≈ 8.5ktokens, estimate
≈ 4.3 %of Claude's 200k window
6.0×the median server
6.0 sto initialize
13 msto list tools
- Run it
- npx -y @sapiom/mcp@0.20.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- sapiom-dev 0.1.0
- Capabilities
- tools
- Instructions
- 12 569 characters
- Of a 1M window
- ≈ 0.9 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/sapiom/sapiom-js
- Registry
- active, updated 2026-10-09 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| sapiom_dev_map | 954 | 11 % |
| sapiom_dev_app_publish | 884 | 10 % |
| sapiom_dev_agents_inspect | 681 | 8 % |
| sapiom_dev_agents_schedule | 654 | 8 % |
| sapiom_dev_app_settings | 566 | 7 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
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
- This server is in the heaviest 10 % of the registry. Its 5 most expensive tools are 44 % of the cost. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.