dev.verimand/mcp-authority-server
Verimand MCP Authority Server
Agent-native access to verifiable VAGP authority.
alive probed 2026-10-19
6tools
≈ 1.2ktokens, estimate
≈ 0.6 %of Claude's 200k window
0.8×the median server
1.0 sto initialize
7 msto list tools
- Run it
- npx -y @verimand/mcp-authority-server@0.1.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- verimand-mcp-authority-server 0.1.0
- Capabilities
- tools
- Instructions
- 138 characters
- 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/verimand/mcp-authority-server
- Website
- https://verimand.dev/protocol
- Registry
- active, updated 2026-09-21 · 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 |
|---|---|---|
| verimand.resolve | 351 | 29 % |
| verimand.get_authority | 295 | 24 % |
| verimand.verify_permit | 288 | 24 % |
| verimand.explain | 104 | 9 % |
| verimand.get_mandate | 90 | 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
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.