Home / MCP registry index / io.github.srotzin/hive-mcp-attest
HiveAttest
io.github.srotzin/hive-mcp-attest in the official MCP registry.
Endpoint https://hive-mcp-attest.onrender.com/mcp. Source: github.com/srotzin/hive-mcp-attest.
The registry describes it as: Pre-action attestation perimeter for AI agents — 8 primitives, signed C18 receipt per call.
We read its 18 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
attest_passport_issue attest_passport_verify attest_custody_append attest_custody_verify attest_custody_proof attest_cargo_register attest_cargo_validate attest_cargo_snapshot attest_warranty_issue attest_warranty_breach attest_warranty_get attest_gate_evaluate attest_inspect_sample attest_smsh_verify attest_absence_build attest_absence_prove attest_absence_verify attest_meta
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-srotzin-hive-mcp-attest)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.