HiveAttest MCP server
io.github.srotzin/hive-mcp-attestsrotzinstreamable-httpv1.0.0Scanned
Pre-action attestation perimeter for AI agents — 8 primitives, signed C18 receipt per call.
18 tools: 12 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
12 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the HiveAttest MCP server can do
The HiveAttest MCP server is published by the GitHub account srotzin. It has 18 tools. It can create or change data (12 tools: attest_passport_issue, attest_passport_verify, attest_custody_append, attest_custody_verify and 8 more), but cannot delete data. 6 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
18 tools
Changes things 12Claude Code: ask
attest_absence_buildBuild a sorted Merkle tree for an audit window (enables cryptographic non-membership proofs, C13: prov-absence).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Build a sorted Merkle tree for an audit window (enables cryptographic non-membership proofs, C13: prov-absence). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_absence_proveProve that a query event is NOT a member of a previously-built audit window (C13).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prove that a query event is NOT a member of a previously-built audit window (C13). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_absence_verifyVerify a non-membership proof against an expected Merkle root (C13).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify a non-membership proof against an expected Merkle root (C13). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_cargo_registerRegister a versioned cargo type in the HiveAttest registry (C17: hive-cargo-taxonomy).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Register a versioned cargo type in the HiveAttest registry (C17: hive-cargo-taxonomy). Pins a definition hash for version-anchoring. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_custody_appendAppend a node to a custody chain (C16: hive-custody).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Append a node to a custody chain (C16: hive-custody). Taint propagates: once tainted, always tainted. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_custody_verifyVerify a custody chain: hash linkage, Ed25519 signatures, and taint propagation (C16).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify a custody chain: hash linkage, Ed25519 signatures, and taint propagation (C16). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_gate_evaluateTHE HEADLINE TOOL.No findings
Why it is in this group
- The name "attest_gate_evaluate" says "evaluate": a word for a change.
Description, as the server wrote it THE HEADLINE TOOL. Evaluate whether an agent may proceed through the HiveAttest gate (C19: hive-gate-enforcer). Verifies passport signature + expiry, cargo registry membership, and warranty status. Every response (allow OR deny) includes a signed C18-format receipt of the gate decision. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_passport_issueIssue a Pre-Action Attestation Manifest (C15: hive-passport).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Issue a Pre-Action Attestation Manifest (C15: hive-passport). Signs with Ed25519 over RFC 8785 JCS-canonical body. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_passport_verifyVerify a Pre-Action Attestation Manifest (C15: hive-passport).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify a Pre-Action Attestation Manifest (C15: hive-passport). Checks Ed25519 signature, temporal validity, and optionally observed inputs hash. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_smsh_verifyVerify a SMSH-Stamp v1 receipt (C8/C12: smsh-stamp-verifier).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Verify a SMSH-Stamp v1 receipt (C8/C12: smsh-stamp-verifier). Validates schema, version, algorithm, timestamp, and Ed25519 signature. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_warranty_breachReport a warranty breach.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Report a warranty breach. Marks the warranty as breached and returns a signed breach record (C18). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_warranty_issueIssue an attestation warranty committing an agent to a claim (C18: hive-attestation-warranty).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Issue an attestation warranty committing an agent to a claim (C18: hive-attestation-warranty). Signed with Ed25519. Reference-grade implementation. Wire format normative; production-grade is Layer B.
Only reads 6Show 6 read-only tools
attest_cargo_snapshotGet a registry snapshot with Merkle root for version pinning (C17).No findings
Why it is in this group
- The name "attest_cargo_snapshot" says "snapshot": a word for reading.
Description, as the server wrote it Get a registry snapshot with Merkle root for version pinning (C17). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_cargo_validateValidate a payload against a registered cargo type schema (C17).No findings
Why it is in this group
- The name "attest_cargo_validate" says "validate": a word for reading.
Description, as the server wrote it Validate a payload against a registered cargo type schema (C17). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_custody_proofRetrieve a Merkle inclusion proof for a specific node in a custody chain (C16).No findings
Why it is in this group
- The description's first verb is "retrieve": a word for reading.
Description, as the server wrote it Retrieve a Merkle inclusion proof for a specific node in a custody chain (C16). Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_inspect_sampleProbabilistic secondary inspection of a record batch (C20: hive-secondary-inspection).No findings
Why it is in this group
- The name "attest_inspect_sample" says "inspect": a word for reading.
Description, as the server wrote it Probabilistic secondary inspection of a record batch (C20: hive-secondary-inspection). Returns a signed inspection record. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_metaReturn HiveAttest layer/spec/patent metadata for all claims.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return HiveAttest layer/spec/patent metadata for all claims. Useful for agent introspection. Reference-grade implementation. Wire format normative; production-grade is Layer B.
attest_warranty_getRetrieve a warranty by ID (C18).No findings
Why it is in this group
- The name "attest_warranty_get" says "get": a word for reading.
Description, as the server wrote it Retrieve a warranty by ID (C18). Reference-grade implementation. Wire format normative; production-grade is Layer B.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 12
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://hive-mcp-attest.onrender.com/mcp: tools/list returned 18 tools to an anonymous client, including attest_passport_issue (write), attest_passport_verify (write), attest_custody_append (write), attest_custody_verify (write), attest_cargo_register (write) and 7 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http hive-attest https://hive-mcp-attest.onrender.com/mcpclaude mcp add --transport http hive-attest https://hive-mcp-attest.onrender.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__hive-attest__attest_custody_proof",
"mcp__hive-attest__attest_cargo_validate",
"mcp__hive-attest__attest_cargo_snapshot",
"mcp__hive-attest__attest_warranty_get",
"mcp__hive-attest__attest_inspect_sample",
"mcp__hive-attest__attest_meta"
],
"ask": [
"mcp__hive-attest__attest_passport_issue",
"mcp__hive-attest__attest_passport_verify",
"mcp__hive-attest__attest_custody_append",
"mcp__hive-attest__attest_custody_verify",
"mcp__hive-attest__attest_cargo_register",
"mcp__hive-attest__attest_warranty_issue",
"mcp__hive-attest__attest_warranty_breach",
"mcp__hive-attest__attest_gate_evaluate",
"mcp__hive-attest__attest_smsh_verify",
"mcp__hive-attest__attest_absence_build",
"mcp__hive-attest__attest_absence_prove",
"mcp__hive-attest__attest_absence_verify"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hive-attest. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.srotzin/hive-mcp-attest/verify?hash=73707cf671d83ca05b3394c91a4721d8da937d6119d4084528fe970d65d677a7" | jq -e '.changed == false'Pinned hash 73707cf671d8, from Nov 20, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.srotzin/hive-mcp-attest/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.srotzin/hive-mcp-attest)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.
HiveAttest MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the HiveAttest MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the HiveAttest MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the HiveAttest MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the HiveAttest MCP server have?
- 18 tools: 12 write, 6 read. attest_passport_issue, attest_passport_verify, attest_custody_append, attest_custody_verify, attest_cargo_register, attest_warranty_issue, attest_warranty_breach, attest_gate_evaluate and 10 more.
Does the HiveAttest MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the HiveAttest MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the HiveAttest MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.