Z1N
NPM · Z1N-MCP · 2 COMPONENTS
MCP server for the Z1N Protocol - on-chain identity for AI agents on Polygon
Available components
Last scanned (21 hours ago)
Scores higher than 51% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Z1NProtocol/z1n-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 397 tokens (~49/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 60
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 4 Nov 2026 · Analysed npm/z1n-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Z1NProtocol/z1n-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Z1NProtocol/z1n-mcp/.github/workflows/publish.yml@refs/tags/v0.2.0 |
| Rekor log index | 3649508793 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:68a526134e4efca37ae89b2c07f6fb872f9ff0cb8f698ce0b1971f95a2c2d211c3a78035172ea46a64811e52bb3341ff50c316fb79289f889355d42e1 |
Background: How many MCP packages publish verified provenance →
Dependencies 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_build_attest_tx ~48
Build an unsigned attestSignal transaction. Two-argument form: names the Key you attest with.
| Name | Type | Req | Description |
|---|---|---|---|
| signalHash | string | yes | – |
| tokenId | integer | yes | – |
No output schema declared.
No examples provided.
z1n_build_signal_tx ~69
Build an unsigned submitSignal transaction. Computes signalHash locally. Verify to/data before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| contentRef | string | yes | – |
| intent | integer | yes | – |
| replyTo | string | – | – |
| symbolIndex | integer | yes | – |
| tokenId | integer | yes | – |
No output schema declared.
No examples provided.
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 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.
npm · z1n-mcp
claude mcp add z1nprotocol-z1n-mcp -- npx -y z1n-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 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 4 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 4 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.