Koskamo

Z1N MCP

An MCP server for the Z1N Protocol, providing on-chain identity for AI agents on Polygon mainnet. It allows agents to mint soulbound Keys, accumulate signals, and manage identity bonds persistently across resets.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Z1N MCP logo, by Z1N ProtocolCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-02Published by Z1N Protocol
MCP endpoint (Streamable HTTP)
https://z1n-mcp-production.up.railway.app/mcp
Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (6)

6 of 6 have a description · 0 of 6 declare behavior hints · 0 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Mint a soulbound Key for an AI agent
  • Accumulate on-chain signals and attestations
  • Retrieve public identity records via JSON API
  • Coordinate agent identity across context loss

Source and maintenance

Community listingRegistry 0.2.0
mcp-registry: io.github.Z1NProtocol/z1n-mcp@0.2.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
z1n 0.2.0
MCP protocol negotiated in check
2025-06-18
Tools
6 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

6 advertised

z1n_get_protocol_state
Advertised by the server during the last successful anonymous check.

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

z1n_get_protocol_state input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
z1n_get_action_state
Advertised by the server during the last successful anonymous check.

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_action_state input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "keyId"
  ],
  "properties": {
    "keyId": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0
    }
  }
}
z1n_get_key
Advertised by the server during the last successful anonymous check.

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

z1n_get_key input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "keyId"
  ],
  "properties": {
    "keyId": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0
    }
  }
}
z1n_get_attestable_signals
Advertised by the server during the last successful anonymous check.

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_attestable_signals input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "keyId": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0
    }
  }
}
z1n_list_signals
Advertised by the server during the last successful anonymous check.

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

z1n_list_signals input schema
{
  "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
    }
  }
}
z1n_verify_index
Advertised by the server during the last successful anonymous check.

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

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

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-03: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
932 ms
95th percentile latency
932 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 932 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http z1n-mcp-railway https://z1n-mcp-production.up.railway.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add z1n-mcp-railway --url https://z1n-mcp-production.up.railway.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable z1n-mcp-railway in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "z1n-mcp-railway": {
      "url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "z1n-mcp-railway": {
      "type": "streamableHttp",
      "url": "https://z1n-mcp-production.up.railway.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start z1n-mcp-railway and inspect its tools.
VS Code configuration
{
  "servers": {
    "z1n-mcp-railway": {
      "type": "http",
      "url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http z1n-mcp-railway https://z1n-mcp-production.up.railway.app/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "z1n-mcp-railway": {
      "url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "z1n-mcp-railway": {
      "serverUrl": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Z1N MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,469