# io.github.zkarchitect/zkverify (npm · zkverify-mcp)

Cryptographically verifiable blockchain data with Merkle proofs + ECDSA signing.

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

## Components

- npm · `zkverify-mcp`: 60/100 (this document), [markdown](https://verifymcp.io/servers/zkarchitect-zkverify/zkverify-mcp.md), [page](https://verifymcp.io/servers/zkarchitect-zkverify/zkverify-mcp)

## Channel facts

- Registry: `npm`
- Package: `zkverify-mcp`
- Version: `0.3.2`
- 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-08-07.

- **Supply Chain Security**: 90/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 199 of 201 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 199 of 201 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 150 tokens (~50/item across 3 items; 3 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**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **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

### Claude

```bash
claude mcp add zkarchitect-zkverify -- npx -y zkverify-mcp
```

### Codex

```bash
codex mcp add zkarchitect-zkverify -- npx -y zkverify-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add zkarchitect-zkverify --command npx --arg -y --arg zkverify-mcp
```

### Hermes

```yaml
mcp_servers:
  zkarchitect-zkverify:
    command: "npx"
    args: ["-y", "zkverify-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "zkarchitect-zkverify": {
      "command": "npx",
      "args": [
        "-y",
        "zkverify-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-08-07 (score 60, +24)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 67
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Schema quality: pass

### 2026-08-06 (score 36)

First indexed and scored.

## MCP tools (3)

### `verify_balance` (~49 tokens)

Verify any blockchain address balance with Merkle proof and ECDSA signature. Returns cryptographically verified balance data.

Input parameters:

- `address` (string, required): EVM address to verify
- `chain` (string)

### `verify_contract` (~46 tokens)

Verify if an address is a smart contract and get its code hash with ECDSA signature.

Input parameters:

- `address` (string, required): EVM address to check
- `chain` (string)

### `verify_signature` (~55 tokens)

Verify a zkVerify ECDSA signature on a previous response. Checks signer authenticity.

Input parameters:

- `expectedSigner` (string, required): Expected signer address (from /health)
- `response` (string, required): JSON response from verify_balance or verify_contract

## Diagnostics

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

## Score history

- 2026-08-07: 60
- 2026-08-06: 36

## Links

- npm package: https://www.npmjs.com/package/zkverify-mcp
- Socket report: https://socket.dev/npm/package/zkverify-mcp
- Repository: https://github.com/zkarchitect/zkverify
- Changelog RSS feed: https://verifymcp.io/servers/zkarchitect-zkverify/zkverify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/zkarchitect-zkverify/zkverify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/zkarchitect-zkverify/zkverify-mcp