It is unusually explicit about what it cannot see, which is what makes the numbers usable: the hook observes surface errors only, so zero failures means zero visible failures, and retry counts, queue wait, chain structure and token usage stay blank unless the agent reports them through log_interaction. Population comparisons hold back until at least five persistent agents exist for a target, saying you are the baseline rather than inventing one. Anomaly signals are observations propagated across agents, not judgments — the decision stays yours.
The query side of ACR, a behavioral registry for agents. Tool calls are captured as receipts and compiled into an interaction profile, which this server lets the agent read back and add to.
- A state-aware starting point: it reads your profile, coverage and unread signals and returns the single most useful next step for wherever you are
- The friction lens: where time and tokens go — chain overhead, amplification between targets, retry waste, and per-target bottlenecks
- Your identity card — agent ID, dashboard link, provider class, registration state
- Manually reported receipts for the things automatic capture cannot infer: chain structure, retry counts, token usage, whether the result was actually used
- Anomaly-signal notifications about components in your composition — a behavioral pattern several unrelated agents reported, not a security verdict
- Acknowledgement of a signal once you have reviewed it with your operator, which records the review without removing the observation from the network
No account and no API key to manage — identity is minted for the agent and persists across sessions. Run it with npx -y @tethral/acr-mcp@latest over stdio, from the npm package @tethral/acr-mcp, currently 2.14.0. ACR_API_URL points elsewhere than the default https://acr.nfkey.ai. The default surface is deliberately small because every tool schema costs context; ACR_ADVANCED=1 in the MCP config loads the full 29-tool set, including the secondary lenses, composition management and network views. Most capture does not come from this server: the companion hook, installed with npm i -g @tethral/acr-hook && acr-hook init, wires into the client's tool hooks and records calls automatically, and the two share one identity file.
One command — npx -y @tethral/acr-mcp@latest