Z1N
REMOTE · Z1N-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Available components
Last scanned (7 hours ago)
Scores higher than 43% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Nov 26 +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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://z1n-mcp-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of z1n-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://z1n-mcp-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://z1n-mcp-production.up.railway.app/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
z1n_get_action_state ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | integer | yes | – |
No output schema declared.
No examples provided.
z1n_get_attestable_signals ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | integer | – | – |
No output schema declared.
No examples provided.
z1n_get_key ~36
One Key: glyphs, owner, signal and attestation counts, recent signals.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | integer | yes | – |
No output schema declared.
No examples provided.
z1n_get_protocol_state ~29
Current Z1N field state: epoch, totals, mint price, contract addresses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
z1n_list_signals ~58
Signals, filterable by key and epoch range. Never returns full history.
| Name | Type | Req | Description |
|---|---|---|---|
| keyId | integer | – | – |
| limit | integer | – | – |
| maxEpoch | integer | – | – |
| minEpoch | integer | – | – |
No output schema declared.
No examples provided.
z1n_verify_index ~25
On-chain vs indexed delta per entity. Check before trusting indexed data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · z1n-mcp-production.up.railway.app
claude mcp add --transport http z1nprotocol-z1n-mcp 'https://z1n-mcp-production.up.railway.app/mcp'
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.