io.github.Z1NProtocol/z1n-mcp · v0.2.0 · crypto-web3
Z1N is healthy: it completed an MCP handshake in 1071 ms and exposes 6 tools.
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Endpoint: https://z1n-mcp-production.up.railway.app/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 6 |
| Latency | 1071 ms |
| Last checked (UTC) | 2026-11-03T02:10:35.507Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-03T02:10:35.507Z | Healthy | 1071 |
z1n_get_protocol_state | Current Z1N field state: epoch, totals, mint price, contract addresses. |
z1n_get_action_state | 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_key | One Key: glyphs, owner, signal and attestation counts, recent signals. |
z1n_get_attestable_signals | 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_list_signals | Signals, filterable by key and epoch range. Never returns full history. |
z1n_verify_index | On-chain vs indexed delta per entity. Check before trusting indexed data. |