FractalAI Post-Quantum Proofs

io.github.johnInartiPublished by GitHub account johnInartiv0.1.3Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant verify post-quantum ML-DSA-65 signatures and buy paid signing, provenance and AI-decision attestation services over x4

What you can do
Verify post-quantum ML-DSA-65/Dilithium-3 signatures against a public key, free of charge, returning a validity verdict. Fetch live x402 payment requirements and the service's discovery manifest for a paid resource. Buy a post-quantum signature over a message or hash for a small USDC fee. Buy a provenance seal over content, combining a drand round, a signature and an on-chain anchor attempt. Buy an attestation of an AI agent's declared decision, chained in an append-only log and returned with a signature for offline verification.
When to use it
Use it when you need to check a post-quantum signature offline-style, or when you want paid, signed provenance or decision receipts for content and agent decisions. The free verification and checkout tools are useful on their own; the paid tools only make sense if you are prepared to send USDC on Base.
Requirements
Runs as a local Node.js process over stdio, installed from the npm package and built before use. Network access to the FractalAI endpoint, which defaults to the public deployment and can be overridden with the FRACTALAI_BASE_URL environment variable. Paid tools need a USDC balance on Base and a confirmed transaction hash; no account or API key is declared.
Before you install
Paid tools cost USDC on Base (about $0.02 to $0.05 per call) and require you to send a real transfer yourself, then pass the transaction hash; one hash buys one call. The paid tools write on-chain anchors using the server's node-bound key. A signature only proves the exact bytes were signed by that key, not that the content is true, and attestation records a decision as declared without judging it. Requests go to a third-party endpoint.

Installation

In SourceWeft

  1. Open FractalAI Post-Quantum Proofs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

FractalAI MCP Server

A Model Context Protocol (MCP) server that exposes FractalAI's live post-quantum cryptography and x402 micropayment capabilities as tools any MCP client (Claude Desktop, IDEs, agent frameworks) can call over stdio.

It talks to the real, public FractalAI deployment at https://fractalai.net.co — nothing here is mocked.

What it does

ToolCostWhat it does
verify_prooffreeVerify a post-quantum ML-DSA-65 / Dilithium-3 / NIST FIPS 204 signature against its public key. Returns { valid, verdict }.
x402_checkoutfreeReturn live x402 (HTTP 402) payment requirements for a paid resource — price, network, USDC asset, payTo, and the accepts[] entries. Also fetches the full .well-known/x402.json manifest.
pqc_sign$0.02 USDCBuy one ML-DSA-65 / Dilithium-3 signature over a message (its sha256 is signed) or a hex hash (signed directly).
seal_provenance$0.05 USDCBuy a PQC + drand provenance seal over content: a drand round + a self-contained ML-DSA-65 / Dilithium-3 signature + an on-chain anchor attempt (this server's node-bound Dilithium-2 key) over the content hash.
attest_decision$0.05 USDCSeal an AI agent's declared decision (input hash, output, model, timestamp) — chained in an append-only Black Box, anchored on-chain (VAID-1, node-bound Dilithium-2 key), and returned with a self-contained ML-DSA-65 / Dilithium-3 signature for independent offline verification.

Honest scope (read this)

  • The signature every tool here serves/verifies directly is ML-DSA-65 / Dilithium-3 (NIST FIPS-204, Cat-3). seal_provenance and attest_decision ALSO write a separate on-chain anchor (VAID-1) using this server's node-bound Dilithium-2 key — additive, not the signature returned to you.
  • Dilithium-3 is resistant to known classical and quantum attacks per NIST FIPS 204 — it is NOT "unbreakable". A signature proves the exact bytes you submitted were signed by this server's post-quantum key. It says nothing about the truthfulness of the signed content.
  • seal_provenance produces a provenance record, not a content audit.
  • attest_decision notarizes a decision as declared; it does not judge whether the decision was correct.
  • The paid tools run a real HTTP 402 flow. Without a payment_tx_hash they return the payment challenge (accepts[]) — they never fabricate a result.

Payment model (x402)

Paid tools are gated by x402: pay in USDC on Base to the service's treasury, then the tool returns the resource. This server uses the facilitator-less txHash settlement path, which needs no facilitator account:

  1. Call the tool once with no payment_tx_hash. You get back the accepts[] block: the exact USDC amount, the asset (USDC on Base), and the payTo treasury address.
  2. Send that USDC transfer on Base yourself.
  3. Call the tool again with payment_tx_hash set to the confirmed transaction hash. One txHash buys exactly one call (anti-replay is enforced server-side).

verify_proof and x402_checkout are always free.

Install & build

bash
cd integrations/mcpnpm installnpm run build

Configure in an MCP client

Claude Desktop (claude_desktop_config.json)

json
{  "mcpServers": {    "fractalai": {      "command": "node",      "args": ["/absolute/path/to/integrations/mcp/dist/index.js"]    }  }}

Any stdio MCP client

Run the built entrypoint: node dist/index.js. It speaks MCP over stdio; all logging goes to stderr so stdout stays a clean JSON-RPC channel.

Environment

  • FRACTALAI_BASE_URL — override the endpoint base (defaults to https://fractalai.net.co).

Example flows

Verify a signature (free):

json
{  "name": "verify_proof",  "arguments": {    "signed_message_b64": "<base64 of the exact bytes that were signed>",    "signature": "<base64 ML-DSA-65 / Dilithium-3 signature>",    "public_key": "<base64 ML-DSA-65 / Dilithium-3 public key>"  }}

Price a signature (free), then buy it (paid):

json
{ "name": "x402_checkout", "arguments": { "resource": "sign" } }
json
{ "name": "pqc_sign", "arguments": { "message": "hello world" } }

The first pqc_sign call (no payment_tx_hash) returns the payment challenge. Pay the USDC, then call again:

json
{  "name": "pqc_sign",  "arguments": { "message": "hello world", "payment_tx_hash": "0x…" }}

About FractalAI

FractalAI is an AI-native Layer 1 blockchain (chain id 62124) written in Rust with post-quantum cryptography (ML-DSA-65 / Dilithium-3 signatures, Kyber encryption). These x402 endpoints sell post-quantum proof, provenance and decision-attestation services to autonomous agents. See https://fractalai.net.co and the discovery manifest at https://fractalai.net.co/.well-known/x402.json.

License

MIT

Source: README.md at commit b469d75

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.3LatestOct 9, 2026
  2. v0.1.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts