Z1N
io.github.Z1NProtocol/z1n-mcpZ1NProtocolstreamable-httpv0.2.0Scanned
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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.
6 tools
Changes things 1Claude Code: ask
z1n_verify_indexOn-chain vs indexed delta per entity.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 On-chain vs indexed delta per entity. Check before trusting indexed data.
Only reads 5Show 5 read-only tools
z1n_get_action_stateWhat one Key can do right now, with reasons.No findings
Why it is in this group
- The name "z1n_get_action_state" says "get": a word for reading.
Description, as the server wrote it What one Key can do right now, with reasons. Signals and attestations left this epoch, whether Canon can be anchored, mint price, contentRef limits. Read this before building any transaction — it replaces combining four endpoints.
z1n_get_attestable_signalsSignals inside their attestation window right now.No findings
Why it is in this group
- The name "z1n_get_attestable_signals" says "get": a word for reading.
Description, as the server wrote it Signals inside their attestation window right now. Pass keyId to remove the ones that would revert: your own wallet's signals, ones this wallet already attested, and signals that hit the 21 Key-attestation cap.
z1n_get_keyOne Key: glyphs, owner, signal and attestation counts, recent signals.No findings
Why it is in this group
- The name "z1n_get_key" says "get": a word for reading.
Description, as the server wrote it One Key: glyphs, owner, signal and attestation counts, recent signals.
z1n_get_protocol_stateCurrent Z1N field state: epoch, totals, mint price, contract addresses.No findings
Why it is in this group
- The name "z1n_get_protocol_state" says "get": a word for reading.
Description, as the server wrote it Current Z1N field state: epoch, totals, mint price, contract addresses.
z1n_list_signalsSignals, filterable by key and epoch range.No findings
Why it is in this group
- The name "z1n_list_signals" says "list": a word for reading.
Description, as the server wrote it Signals, filterable by key and epoch range. Never returns full history.
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.
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 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http z1n https://z1n-mcp-production.up.railway.app/mcpclaude mcp add --transport http z1n https://z1n-mcp-production.up.railway.app/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__z1n__z1n_get_protocol_state",
"mcp__z1n__z1n_get_action_state",
"mcp__z1n__z1n_get_key",
"mcp__z1n__z1n_get_attestable_signals",
"mcp__z1n__z1n_list_signals"
],
"ask": [
"mcp__z1n__z1n_verify_index"
],
"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 z1n. 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://anlyon.dev/api/v1/servers/io.github.Z1NProtocol/z1n-mcp/verify?hash=7cbbdfafda6a7f0b2d56a656b230b408486e760d7fab8a3e2a8c654df727518c" | jq -e '.changed == false'Pinned hash 7cbbdfafda6a, from Nov 2, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.Z1NProtocol/z1n-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.Z1NProtocol/z1n-mcp)Source: MCP Registry · repository. Synced Nov 2, 2026, 21:18 UTC.