MCP MeasureMCP Measure

index observed

Z1N

MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon

Should I use this

Quality & Safety

B
Description quality
100%
Schema completeness
60%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~571Tokens (tool definitions)
~532 BTypical response size
Minimal attention impact (0.45% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "z1n-mcp": {
      "command": "npx",
      "args": [
        "z1n-mcp"
      ]
    }
  }
}

Runnable packages

npmz1n-mcp0.2.0stdio

Remote endpoints

https://z1n-mcp-production.up.railway.app/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢z1n_get_protocol_state

Current Z1N field state: epoch, totals, mint price, contract addresses.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢z1n_get_action_state(keyId)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "keyId": {
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "keyId"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢z1n_get_key(keyId)

One Key: glyphs, owner, signal and attestation counts, recent signals.

Input Schema

{
  "type": "object",
  "properties": {
    "keyId": {
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "keyId"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴z1n_get_attestable_signals(keyId)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "keyId": {
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢z1n_list_signals(keyId, minEpoch, maxEpoch, limit)

Signals, filterable by key and epoch range. Never returns full history.

Input Schema

{
  "type": "object",
  "properties": {
    "keyId": {
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "minEpoch": {
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "maxEpoch": {
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "limit": {
      "default": 20,
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢z1n_verify_index

On-chain vs indexed delta per entity. Check before trusting indexed data.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools