MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh 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.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http z1n-mcp https://z1n-mcp-production.up.railway.app/mcp
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.
| Argument | Type | Description |
|---|---|---|
| keyId* | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keyId"
],
"properties": {
"keyId": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| keyId | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"keyId": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
}
}
}One Key: glyphs, owner, signal and attestation counts, recent signals.
| Argument | Type | Description |
|---|---|---|
| keyId* | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"keyId"
],
"properties": {
"keyId": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
}
}
}Current Z1N field state: epoch, totals, mint price, contract addresses.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Signals, filterable by key and epoch range. Never returns full history.
| Argument | Type | Description |
|---|---|---|
| keyId | integer | |
| limit | integer | |
| maxEpoch | integer | |
| minEpoch | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"keyId": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 100,
"minimum": 1
},
"maxEpoch": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
"minEpoch": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
}
}
}On-chain vs indexed delta per entity. Check before trusting indexed data.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 2, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.