# Z1N (remote · z1n-mcp-production.up.railway.app)

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

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `z1n-mcp-production.up.railway.app`: 60/100 (this document), [markdown](https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production.md), [page](https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production)
- npm · `z1n-mcp`: 75/100, [markdown](https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp.md), [page](https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp)

## Channel facts

- Endpoint: `https://z1n-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Z1N MCP server?

Z1N is a hosted endpoint at https://z1n-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http z1nprotocol-z1n-mcp 'https://z1n-mcp-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "z1nprotocol-z1n-mcp": {
      "url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "z1nprotocol-z1n-mcp": {
      "type": "http",
      "url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.z1nprotocol-z1n-mcp]
url = "https://z1n-mcp-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "z1nprotocol-z1n-mcp": {
      "type": "remote",
      "url": "https://z1n-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add z1nprotocol-z1n-mcp --url 'https://z1n-mcp-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  z1nprotocol-z1n-mcp:
    url: "https://z1n-mcp-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "z1nprotocol-z1n-mcp": {
      "Transport": "http",
      "Url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add z1nprotocol-z1n-mcp -t streamable-http -u 'https://z1n-mcp-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "z1nprotocol-z1n-mcp": {
      "type": "http",
      "url": "https://z1n-mcp-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 60, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-04 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 59)

First indexed and scored.

## MCP tools (6)

### `z1n_get_protocol_state` (~29 tokens)

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

### `z1n_get_action_state` (~65 tokens)

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 parameters:

- `keyId` (integer, required)

### `z1n_get_key` (~36 tokens)

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

Input parameters:

- `keyId` (integer, required)

### `z1n_get_attestable_signals` (~67 tokens)

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 parameters:

- `keyId` (integer)

### `z1n_list_signals` (~58 tokens)

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

Input parameters:

- `keyId` (integer)
- `limit` (integer)
- `maxEpoch` (integer)
- `minEpoch` (integer)

### `z1n_verify_index` (~25 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production#diagnostics

## Score history

- 2026-11-05: 60
- 2026-11-04: 60
- 2026-11-03: 59
- 2026-11-02: 59

## Common questions

### What is the Z1N MCP server?

Z1N is an MCP server listed in the public MCP registry as io.github.Z1NProtocol/z1n-mcp. MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon. This page covers its hosted endpoint (https://z1n-mcp-production.up.railway.app/mcp).

### Is the Z1N MCP server safe to use?

Z1N scores 60 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Z1N MCP server expose?

Z1N exposes 6 tools: z1n_get_protocol_state, z1n_get_action_state, z1n_get_key, z1n_get_attestable_signals, z1n_list_signals, z1n_verify_index. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.

### Does the Z1N MCP server require authentication?

Its publisher declares no required credentials for Z1N. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Z1N MCP server still maintained?

Z1N is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Z1N MCP server?

VerifyMCP ran 3 checks on Z1N, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Z1N: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://z1n-mcp-production.up.railway.app/mcp
- Repository: https://github.com/Z1NProtocol/z1n-mcp
- Website: https://www.z1nprotocol.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production.json
- HTML version of this page: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp-production