MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Connect Remote server
claude mcp add --transport http z1n-mcp https://z1n-mcp-production.up.railway.app/mcp
{
"mcpServers": {
"z1n-mcp": {
"url": "https://z1n-mcp-production.up.railway.app/mcp"
}
}
}
{
"servers": {
"z1n-mcp": {
"type": "http",
"url": "https://z1n-mcp-production.up.railway.app/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://z1n-mcp-production.up.railway.app/mcp
Tools 6 found in our last check
z1n_get_protocol_stateCurrent Z1N field state: epoch, totals, mint price, contract addresses.
z1n_get_action_stateWhat 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_keyOne Key: glyphs, owner, signal and attestation counts, recent signals.
z1n_get_attestable_signalsSignals 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_list_signalsSignals, filterable by key and epoch range. Never returns full history.
z1n_verify_indexOn-chain vs indexed delta per entity. Check before trusting indexed data.
Details
| Endpoint | https://z1n-mcp-production.up.railway.app/mcp (Streamable HTTP) |
| Package | [email protected] (NPM, stdio) |
| First published | 2 Nov 2026 |
| Last updated | 2 Nov 2026 |
| Registry name | io.github.Z1NProtocol/z1n-mcp |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
