Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/XFuel

XFuel

I
by io.github.XFuel-Lab

Submit AI inference to XFuel, pay per task (USDC via x402 or TFUEL), fetch/verify ZK proofs.

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command
npx -y [email protected]
Credentials from the publisher
  • XFUEL_API_URL — XFuel API base URL. Defaults to the hosted testnet demo.
  • XFUEL_API_KEY — API key sent as X-API-Key. Defaults to the shared public demo key.
  • XFUEL_MCP_AUTH_TOKEN — Optional bearer token required on the HTTP transport (Authorization: Bearer <token>).
  • XFUEL_RPC_URL — Theta RPC URL enabling verify_proof's optional on-chain nullifier read.
  • ZK_VERIFIER_ADDRESS — ZKVerifierSP1 contract address (paired with XFUEL_RPC_URL).
  • XFUEL_PAYER_PRIVATE_KEY — Funded payer private key that enables the pay_with_usdc tool. Moves USDC — keep secret; use a low-balance wallet.
Provider
Claude Code
XFUEL_API_URL=<value> XFUEL_API_KEY=<secret> XFUEL_MCP_AUTH_TOKEN=<secret> XFUEL_RPC_URL=<value> ZK_VERIFIER_ADDRESS=<value> XFUEL_PAYER_PRIVATE_KEY=<secret> claude mcp add io.github.xfuel-lab-xfuel-mcp -- npx -y [email protected]

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.xfuel-lab-xfuel-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "XFUEL_API_URL": "<value>",
        "XFUEL_API_KEY": "<secret>",
        "XFUEL_MCP_AUTH_TOKEN": "<secret>",
        "XFUEL_RPC_URL": "<value>",
        "ZK_VERIFIER_ADDRESS": "<value>",
        "XFUEL_PAYER_PRIVATE_KEY": "<secret>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Questions

How do I install XFuel?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does XFuel need an API key?
The publisher lists these environment variables: XFUEL_API_URL, XFUEL_API_KEY, XFUEL_MCP_AUTH_TOKEN, XFUEL_RPC_URL, ZK_VERIFIER_ADDRESS, XFUEL_PAYER_PRIVATE_KEY.
What transport does XFuel use?
XFuel runs locally over stdio.
When was XFuel last checked?
Last checked 2026-10-16. Submit AI inference to XFuel, pay per task (USDC via x402 or TFUEL), fetch/verify ZK proofs.

Submit AI inference to XFuel, pay per task (USDC via x402 or TFUEL), fetch/verify ZK proofs.

Chit402

Chit402 is the book. This agent spent Y on this job. You hold hub, model, and amount.

POST /v1/chat/completions returns a signed receipt: hub, model, amount, verify_url. Cost-plus, quoted, receipted — pay USDC on Base or Solana. GET|POST /v1/agents/:agent_id/book is possession-gated last-N collected spend. Signed receipt is table stakes (ES256 issuer signature); SP1 settlement proof is on demand. The issuer signature does not prove USDC moved. The product is the collected row — sidecar + ingest if you already pay a provider; without a collected USDC payment.ref the receipt is client-attested only. Register is fail-closed: a collected HMAC-valid receipt plus a plain EOA (personal_sign), AAWP official, or smart-account agentWallet.

To learn more about the protocol design, read the whitepaper. For live endpoints and what is real vs mock today, see runtime state. Full documentation hub: docs/.

Live app: https://chit402.com
Public API: https://api.chit402.com

Table of Contents

  • Setup
  • Using the API
  • Agent toolkit
  • Documentation
  • Security

Setup

Prerequisites

Install Node.js 20+ and npm 10+. A Rust toolchain is required if you build CosmWasm, SP1, or zkLLM crates.

Build and test

Clone the repository, install dependencies, compile contracts, and run the test suite:

git clone https://github.com/XFuel-Lab/chit402.git
cd chit402
npm install
npx hardhat compile
npx hardhat test

Agent gateway

The agent-facing API (settlement, payments, proving, receipts) runs from services/gateway:

cd services/gateway
npm install
npm run m2m-server

The gateway listens on http://localhost:3002 by default. Env examples live under services/gateway/. Production layout is documented in deployment.

Website

cd apps/web
npm install
npm run dev

Try the paid door

No account. No API key. A wallet that can pay the 402 is enough. Register is only to hold the book after a collected receipt.

curl.exe -sS -D - -X POST https://api.chit402.com/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{}'

Unauthenticated /v1 returns HTTP 402 with payment requirements (USDC on Base or Solana). The receipt prices the next call. Working copy: docs/CHAT_COMPLETIONS_GATEWAY.md.

npm install chit402-sdk
npx chit402-mcp

flagship-demo.ts is the paid /task-request path (402 without a payer). Do not start there.

  • TypeScript SDK — packages/sdk
  • MCP server — packages/mcp
  • Agent playbook — packages/agent-skills

Windows note: if you use raw HTTP, call curl.exe — PowerShell’s curl is not real curl.

API reference: M2M API · Chat completions: docs here · Payments: x402 adapter.

Dual anchoring

Each UTC day the gateway signs the receipt Merkle root and publishes it in two places. GET /v1/receipts/tree/head returns both under anchors.base and anchors.solana (signature, slot, cluster, memo). A missing key or a failed send leaves that side pending. A day that already has a Solana signature is not posted again. Details: docs/product/receipt-merkle.md.

ChainEnvWhat is posted
BaseRECEIPT_ANCHOR_PRIVATE_KEY, optional RECEIPT_ANCHOR_FROM, BASE_RPC_URL or SETTLEMENT_RPC_URLZero-value transaction, calldata = 32-byte root
SolanaSOLANA_ANCHOR_SECRET_KEY (base58 or JSON array), SOLANA_RPC_URL, optional SOLANA_ANCHOR_CLUSTER (default mainnet-beta; devnet for tests)SPL Memo chit402:root:v1:<book_or_global>:<yyyy-mm-dd>:<root_hex>:<prev_root_hex>

Keys stay in the host environment. They are not read from a file in this repo.

GET /v1/receipts/:task_id/inclusion proves one leaf against a signed head. When that head is not itself anchored and a later anchored signed head contains the leaf, the JSON adds optional covered_by. It names the smallest such head: epoch, tree_size, root, inclusion_url (/v1/receipts/<task_id>/inclusion?tree_size=<N>), and anchors (anchors.base.tx, and anchors.solana.slot / anchors.solana.signature when Solana is present). The field is omitted when the head is itself anchored. A quarantined head is not served and is not used as covered_by. Existing fields stay as they are. Detail: docs/product/receipt-merkle.md.

npx chit402-verify receipt.json inclusion.json head.json --rpc

That checks the inclusion proof, fetches the Solana transaction and requires the memo to contain the root, and checks the Base calldata the same way. It prints what this proves and what it does not prove.

One memo costs the Solana base fee: 5,000 lamports, 0.000005 SOL. No account is created, so there is no rent, and the sender does not add a priority fee. At about $120 per SOL that is under $0.001.

Devnet smoke (export the variables in the shell; the script does not load an env file):

export SOLANA_ANCHOR_SECRET_KEY   # base58 or JSON array, host env only
export SOLANA_ANCHOR_CLUSTER=devnet
export SOLANA_RPC_URL=https://api.devnet.solana.com
node scripts/solana-anchor-smoke

Documentation

DocDescription
WHITEPAPER.mdProtocol design
docs/README.mdDocumentation hub
docs/POSITIONING.mdMessaging
docs/DEPLOYMENT.mdDeployment
docs/TESTING.mdTests
AGENTS.mdAgent / LLM index
CONTRIBUTING.mdContributing

Security

Responsible disclosure (safe harbour; no cash bounty until the first audit): docs/bug-bounty.md.
Reporting policy: SECURITY.md.


Apache-2.0 — see LICENSE.

How do I install XFuel?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does XFuel need an API key?
The publisher lists these environment variables: XFUEL_API_URL, XFUEL_API_KEY, XFUEL_MCP_AUTH_TOKEN, XFUEL_RPC_URL, ZK_VERIFIER_ADDRESS, XFUEL_PAYER_PRIVATE_KEY.
What transport does XFuel use?
XFuel runs locally over stdio.
When was XFuel last checked?
Last checked 2026-10-16. Submit AI inference to XFuel, pay per task (USDC via x402 or TFUEL), fetch/verify ZK proofs.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Pricing
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • MCP Apps
  • Tools
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • Club
  • Work with us
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA