io.github.agenson-horrowitz/agent-output-guard
agent-output-guard
Validate and verify data from other agents before acting on it. Zero LLM costs.
alive probed 2026-10-19
5tools
≈ 833tokens, estimate
≈ 0.4 %of Claude's 200k window
0.6×the median server
512 msto initialize
8 msto list tools
- Run it
- npx -y @agenson-horrowitz/agent-output-guard-mcp@1.0.8 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- agent-output-guard 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- ≈ <0.1 % 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/agenson-tools/agent-output-guard-mcp
- Registry
- active, updated 2026-04-02 · 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 |
|---|---|---|
| cross_reference_check | 190 | 23 % |
| output_consistency_score | 173 | 21 % |
| validate_data_freshness | 170 | 20 % |
| detect_hallucination_markers | 168 | 20 % |
| verify_json_schema | 132 | 16 % |
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
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.