Physical Capability Cloud MCP server

Physical Capability Cloud (PCC)

An open protocol for verifiable, settleable physical work. Operators run hardware. Customers (or their AI agents) discover, negotiate, escrow, and settle — all over HTTP, all anchored on-chain.

Live: capability.network · License: Apache-2.0 · Discord: PCC Network

What is PCC?

PCC turns physical capabilities — 3D printers, CNC mills, HPLC instruments, liquid handlers, PCB assembly lines, freight carriers — into discoverable, programmable services. Every job is contracted over HTTP, escrowed on-chain, executed on real hardware, evidenced cryptographically, and settled when the evidence meets the agreed assurance tier.

It's substrate, not platform: anyone can run an operator node, contribute a capability adapter, or build an integration. The protocol charges 2.35% on settlement — that's the entire business model.

30-second start

Connect an AI agent (no install):

curl https://capability.network/agent-package.json
# 230+ tools as JSON Schema. Paste into Claude, GPT, or any LLM tool harness.

Connect a machine (Python operator node):

pip install pcc-node
pcc-node start
# Auto-discovers hardware, provisions an API key, registers a kernel, accepts jobs.

MCP server (Claude Code / Codex):

{ "pcc": { "command": "node", "args": ["packages/mcp-server/dist/index.js"], "env": { "PCC_URL": "https://capability.network" } } }

What it actually does

Tell an agent what you need. PCC handles the rest:

• 3D-print a bracket — an operator with idle FDM capacity gets the job, escrow locks before the print starts, evidence streams while it's running, escrow releases when the print passes verification.
• HPLC compound analysis — a regulated lab in Buenos Aires has open instrument time. A startup in Austin queues a sample. The protocol routes the work, anchors the evidence, settles in USDC.
• Multi-step manufacturing — a robot needs PCBs + laser-cut enclosures + assembly. PCC decomposes the request into a capability DAG and orchestrates the supply chain across operators.

Operators set their own pricing. Customers pay only on verified completion.

How it works

YOUR AGENT
        │
        │  "analyze this compound and print the report"
        ▼
   ┌─────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐    ┌──────────┐
   │DISCOVER │───▶│   BID    │───▶│ ESCROW   │───▶│ EXECUTE  │───▶│ VERIFY   │───▶│ SETTLE   │
   │ DHT     │    │ Auction  │    │ On-chain │    │ Real     │    │ Evidence │    │ Auto     │
   │ gossip  │    │ pricing  │    │ milestone│    │ hardware │    │ pipeline │    │ release  │
   └─────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘    └──────────┘

1. Discover — your agent broadcasts what it needs. The network finds operators with matching capabilities.
2. Bid — operators compete on price. No phone calls, no RFQs, no waiting.
3. Escrow — funds lock on-chain before work starts. Both sides are protected.
4. Execute — the operator's hardware runs the job. Evidence streams in real time.
5. Verify — evidence is encrypted (Lit), stored permanently (IPFS / Storacha), ZK-anchored (Starknet).
6. Settle — funds release automatically when evidence meets the contracted assurance tier.

Assurance tiers

Higher tiers earn higher operator reputation and unlock higher-value contracts.

Built on

Shortened. The full README is on GitHub.