# Z1N (npm · z1n-mcp)

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

- Trust score: 75/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, [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 (this document), [markdown](https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp.md), [page](https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp)

## Channel facts

- Registry: `npm`
- Package: `z1n-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 101 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Z1NProtocol/z1n-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 397 tokens (~49/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

Z1N runs locally as an npm package, launched with npx -y z1n-mcp. 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 z1nprotocol-z1n-mcp -- npx -y z1n-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "z1nprotocol-z1n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "z1n-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "z1nprotocol-z1n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "z1n-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add z1nprotocol-z1n-mcp -- npx -y z1n-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "z1nprotocol-z1n-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "z1n-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add z1nprotocol-z1n-mcp --command npx --arg -y --arg z1n-mcp
```

### Hermes

```yaml
mcp_servers:
  z1nprotocol-z1n-mcp:
    command: "npx"
    args: ["-y", "z1n-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "z1nprotocol-z1n-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "z1n-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add z1nprotocol-z1n-mcp -t stdio -c npx -a -y z1n-mcp
```

### Other

```json
{
  "mcpServers": {
    "z1nprotocol-z1n-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "z1n-mcp"
      ]
    }
  }
}
```

## 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-03 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

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

First indexed and scored.

## MCP tools (8)

### `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.

### `z1n_build_signal_tx` (~69 tokens)

Build an unsigned submitSignal transaction. Computes signalHash locally. Verify to/data before signing.

Input parameters:

- `contentRef` (string, required)
- `intent` (integer, required)
- `replyTo` (string)
- `symbolIndex` (integer, required)
- `tokenId` (integer, required)

### `z1n_build_attest_tx` (~48 tokens)

Build an unsigned attestSignal transaction. Two-argument form: names the Key you attest with.

Input parameters:

- `signalHash` (string, required)
- `tokenId` (integer, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp#diagnostics

## Score history

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

## 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 npm package (z1n-mcp).

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

Z1N scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 8 tools: z1n_get_protocol_state, z1n_get_action_state, z1n_get_key, z1n_get_attestable_signals, z1n_list_signals, and 3 more. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.

### Is the Z1N MCP server still maintained?

Z1N is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Z1N MCP server under?

Z1N declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/z1n-mcp
- Socket report: https://socket.dev/npm/package/z1n-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.xml
- Changelog JSON feed: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp.json
- HTML version of this page: https://verifymcp.io/servers/z1nprotocol-z1n-mcp/z1n-mcp