# FractalAI Post-Quantum Proofs (npm · fractalai-mcp-server)

Post-quantum (ML-DSA-65/Dilithium-3) proof, provenance & AI-decision receipts, paid via x402.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `fractalai-mcp-server`: 66/100 (this document), [markdown](https://verifymcp.io/servers/johninarti-fractalai/fractalai-mcp-server.md), [page](https://verifymcp.io/servers/johninarti-fractalai/fractalai-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `fractalai-mcp-server`
- Version: `0.1.1`
- 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-09-21.

- **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 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1056 tokens (~211/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pqc_sign" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 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.

## Install

### How do I install the FractalAI Post-Quantum Proofs MCP server?

FractalAI Post-Quantum Proofs runs locally as an npm package, launched with npx -y fractalai-mcp-server. 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 johninarti-fractalai -- npx -y fractalai-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "johninarti-fractalai": {
      "command": "npx",
      "args": [
        "-y",
        "fractalai-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "johninarti-fractalai": {
      "command": "npx",
      "args": [
        "-y",
        "fractalai-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add johninarti-fractalai -- npx -y fractalai-mcp-server
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add johninarti-fractalai --command npx --arg -y --arg fractalai-mcp-server
```

### Hermes

```yaml
mcp_servers:
  johninarti-fractalai:
    command: "npx"
    args: ["-y", "fractalai-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "johninarti-fractalai": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "fractalai-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add johninarti-fractalai -t stdio -c npx -a -y fractalai-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "johninarti-fractalai": {
      "command": "npx",
      "args": [
        "-y",
        "fractalai-mcp-server"
      ]
    }
  }
}
```

## 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-09-21 (score 66, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-14 (score 62, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 47)

First indexed and scored.

## MCP tools (5)

### `verify_proof` (~172 tokens)

Verify a post-quantum signature

Verify a post-quantum (ML-DSA-65 / Dilithium-3, NIST FIPS 204) signature against its public key. Free, no payment. Returns { valid, verdict }. A valid result proves the exact bytes in signed_message_b64 were signed by the given key; it says nothing about their truthfulness. For a signature from pqc_sign over a hex digest D, signed_message_b64 = base64(utf8(D)).

Input parameters:

- `public_key` (string, required): Base64 ML-DSA-65 / Dilithium-3 public key.
- `signature` (string, required): Base64 ML-DSA-65 / Dilithium-3 signature to check.
- `signed_message_b64` (string, required): Base64 of the exact bytes that were signed.

### `x402_checkout` (~128 tokens)

Get x402 payment requirements

Return the live x402 (HTTP 402) payment requirements for a paid FractalAI resource: price, network, USDC asset, payTo address and the accepts[] entries (EIP-3009 gasless and txHash fallback). Free — it never moves funds. Use it before pqc_sign / seal_provenance / attest_decision to learn exactly how much and how to pay. Pass resource='manifest' for the full .well-known/x402.json.

Input parameters:

- `resource` (string, required): Which paid resource to price, or 'manifest' for the whole x402 manifest.

### `pqc_sign` (~236 tokens)

Buy a post-quantum signature

Pay $0.02 USDC (x402) for one post-quantum ML-DSA-65 / Dilithium-3 (NIST FIPS 204) signature over your message (its sha256 is signed) or a hex hash (signed directly). Returns { digest, signature, public_key, payment }. Without payment_tx_hash you get the payment challenge, not a signature. The signature proves these exact bytes were signed by this server's PQC key — nothing about their truthfulness, and 'quantum-resistant per NIST' is not 'unbreakable'.

Input parameters:

- `hash` (string): Hex digest signed directly. Provide message OR hash.
- `message` (string): UTF-8 string; sha256(message) is signed.
- `payer` (string): Optional payer address hint.
- `payment_tx_hash` (string): A confirmed USDC-on-Base transaction hash paying the required amount to the treasury. If omitted, the tool returns the x402 payment challenge (accepts[]) instead of a result — pay first, then call ag…

### `seal_provenance` (~241 tokens)

Buy a PQC + drand provenance seal

Pay $0.05 USDC (x402) for a post-quantum provenance seal over content: a drand round (League of Entropy, not backdateable) + a self-contained ML-DSA-65 / Dilithium-3 signature over the seal + an on-chain anchor attempt (this server's node-bound Dilithium-2 key) over the content hash. Useful for EU AI Act (Art. 10/50/53) provenance. It is a provenance record, not a content audit. Without payment_tx_hash you get the payment challenge.

Input parameters:

- `content` (string): UTF-8 content; sha256(content) is sealed.
- `content_hash` (string): Sha256 hex you already computed. Provide content OR content_hash.
- `payer` (string): Optional payer address hint.
- `payment_tx_hash` (string): A confirmed USDC-on-Base transaction hash paying the required amount to the treasury. If omitted, the tool returns the x402 payment challenge (accepts[]) instead of a result — pay first, then call ag…

### `attest_decision` (~279 tokens)

Seal an AI agent decision (VAID-1)

Pay $0.05 USDC (x402) to seal an AI agent's declared decision: its input hash, output, model and timestamp are chained in an append-only Black Box and anchored on-chain (VAID-1, this server's node-bound Dilithium-2 key). You also get back a self-contained ML-DSA-65 / Dilithium-3 signature over the same canonical decision bytes for independent offline verification. Returns a re-verifiable receipt. Built for EU AI Act Art.12 record-keeping. It notarizes the decision as declared; it does not judge whether the decision was correct. Without payment_tx_hash you get the payment challenge.

Input parameters:

- `agent_id` (string, required): Stable identifier of the agent whose decision is sealed.
- `input` (string, required): The decision input (or its hash).
- `model` (string): Model/agent version that produced the decision.
- `output` (string, required): The decision output the agent produced.
- `payer` (string): Optional payer address hint.
- `payment_tx_hash` (string): A confirmed USDC-on-Base transaction hash paying the required amount to the treasury. If omitted, the tool returns the x402 payment challenge (accepts[]) instead of a result — pay first, then call ag…

## Diagnostics

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

## Score history

- 2026-09-21: 66
- 2026-09-20: 62
- 2026-09-19: 62
- 2026-09-18: 62
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 62
- 2026-09-13: 47

## Common questions

### What is the FractalAI Post-Quantum Proofs MCP server?

FractalAI Post-Quantum Proofs is an MCP server listed in the public MCP registry as io.github.johnInarti/fractalai. Post-quantum (ML-DSA-65/Dilithium-3) proof, provenance & AI-decision receipts, paid via x402. This page covers its npm package (fractalai-mcp-server).

### Is the FractalAI Post-Quantum Proofs MCP server safe to use?

FractalAI Post-Quantum Proofs scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 FractalAI Post-Quantum Proofs MCP server expose?

FractalAI Post-Quantum Proofs exposes 5 tools: verify_proof, x402_checkout, pqc_sign, seal_provenance, attest_decision. Their descriptions and schemas cost roughly 1,056 tokens of context every time the server is loaded.

### Is the FractalAI Post-Quantum Proofs MCP server still maintained?

FractalAI Post-Quantum Proofs is still listed as active in the MCP registry. We last reached this channel on 21 September 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 FractalAI Post-Quantum Proofs MCP server under?

FractalAI Post-Quantum Proofs 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/fractalai-mcp-server
- Socket report: https://socket.dev/npm/package/fractalai-mcp-server
- Website: https://fractalai.net.co/
- Changelog RSS feed: https://verifymcp.io/servers/johninarti-fractalai/fractalai-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/johninarti-fractalai/fractalai-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/johninarti-fractalai/fractalai-mcp-server