Physical Capability Cloud MCP server
Commit 14 Nov 2026Memungkinkan AI agent untuk menemukan, menegosiasikan, dan memesan layanan fisik dunia nyata seperti 3D printing dan otomatisasi lab melalui protokol yang dapat diverifikasi.
Juga dikenal sebagai LamaSu/physical-capability-cloud, physical-capability-cloud
- Stars
- 3
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 2.19.0
- Commit terakhir
- 14 Nov 2026
- Lisensi
- Apache-2.0
Apa itu Physical Capability Cloud MCP?
Memungkinkan AI agent untuk menemukan, menegosiasikan, dan memesan layanan fisik dunia nyata seperti 3D printing dan otomatisasi lab melalui protokol yang dapat diverifikasi.
Ringkasan dibuat dari README proyek
Tentang Physical Capability Cloud MCP server
Physical Capability Cloud menyediakan protokol terbuka untuk mengubah perangkat keras fisik menjadi layanan yang dapat diprogram. Ini memungkinkan AI agent dan developer untuk menemukan, menegosiasikan, dan memesan tugas dunia nyata seperti 3D printing, CNC milling, dan otomatisasi lab. Sistem ini berfungsi sebagai substrat di mana operator menjalankan hardware dan pelanggan mengontrak pekerjaan melalui HTTP, menggunakan on-chain escrow untuk melindungi kedua belah pihak selama fase eksekusi.
Pengguna dapat menghubungkan AI agent dengan mengambil paket JSON schema atau men-deploy MCP server untuk digunakan dengan tool seperti Claude Code. Operator dapat mengintegrasikan mesin menggunakan node Python yang secara otomatis menemukan hardware dan menyediakan API key. Protokol ini memastikan kepercayaan melalui berbagai tier jaminan, mulai dari snapshot perangkat yang diakui sendiri secara sederhana hingga bukti ZK-anchored yang berdaulat untuk industri teregulasi seperti manufaktur medis atau kedirgantaraan. Penyelesaian pembayaran terjadi secara otomatis ketika bukti kriptografis memenuhi persyaratan kontrak yang telah disepakati.
Apa yang bisa Anda lakukan dengannya
- 1Pengadaan 3D printing otomatisSebuah AI agent dapat menemukan printer FDM yang sedang menganggur, mengunci dana di escrow, dan memantau proses cetak melalui streaming bukti.
- 2Analisis laboratorium jarak jauhSeorang developer dapat menggunakan agent untuk mengantre analisis senyawa kimia di lab teregulasi yang berlokasi di negara berbeda.
- 3Manufaktur multi-step yang kompleksSebuah agent dapat memecah permintaan manufaktur skala besar menjadi langkah-langkah individual dan menyewa penyedia yang berbeda untuk setiap bagian dari proses tersebut.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Physical Capability Cloud MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Physical Capability Cloud MCP di Claude Code
$ claude mcp add --transport http physical-capability-cloud https://capability.network/mcpInstal Physical Capability Cloud MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"physical-capability-cloud": {
"url": "https://capability.network/mcp"
}
}
}Instal Physical Capability Cloud MCP di VS Code
.vscode/mcp.json
{
"servers": {
"physical-capability-cloud": {
"type": "http",
"url": "https://capability.network/mcp"
}
}
}Instal Physical Capability Cloud MCP di VS Code CLI
$ code --add-mcp '{"name":"physical-capability-cloud","type":"http","url":"https://capability.network/mcp"}'Instal Physical Capability Cloud MCP di Codex
$ codex mcp add physical-capability-cloud --url https://capability.network/mcpInstal Physical Capability Cloud MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.physical-capability-cloud] url = "https://capability.network/mcp"
Instal Physical Capability Cloud MCP di Gemini CLI
$ gemini mcp add -s user --transport http physical-capability-cloud https://capability.network/mcpInstal Physical Capability Cloud MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"physical-capability-cloud": {
"url": "https://capability.network/mcp",
"type": "http"
}
}
}Konfigurasi
PCC_URL
| Nama | Deskripsi | Tipe |
|---|---|---|
| PCC_URL | — |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaulamasu/physical-capability-cloud is public and reachablegithub.com/lamasu/physical-capability-cloud ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-11github.com/lamasu/physical-capability-cloud ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPinitialize answered with protocol 2025-06-18 in 531 msLolos
README
Lihat di GitHubPhysical Capability Cloud (PCC)
An open protocol for verifiable, settleable physical work. Operators run hardware. Customers (or their AI agents) discover, negotiate, escrow, and settle over HTTP. Settlement runs on a test network during the public beta.
Public beta: 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. Jobs are contracted over HTTP, escrowed (on a test network during the beta), 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
# The full agent package 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 your agent what you need. Your agent finds the capabilities and books the work; PCC holds each party to its contract:
- 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 through its agent. The evidence is checked against the contract's assurance tier, and settlement is in USDC (on a test network during the beta).
- Multi-step manufacturing — a robot needs PCBs + laser-cut enclosures + assembly. Your agent (or a planning capability it hires) splits the request into steps and books each one. Accepting a multi-provider plan as one deal is in progress.
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 │
└─────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
- Discover — your agent broadcasts what it needs. The network finds operators with matching capabilities.
- Bid — operators compete on price. No phone calls, no RFQs, no waiting.
- Escrow — funds lock on-chain before work starts. Both sides are protected.
- Execute — the operator's hardware runs the job. Evidence streams in real time.
- Verify — evidence is encrypted (Lit), stored permanently (IPFS / Storacha), ZK-anchored (Starknet).
- Settle — funds release automatically when evidence meets the contracted assurance tier.
Assurance tiers
| Tier | Name | Evidence required | Use case |
|---|---|---|---|
| 0 | Self-attested | Device health snapshot | Prototyping, low-risk |
| 1 | Verified | Bundle hash + completion events | Standard production |
| 2 | Certified | Photo + sensor data + event log | Regulated manufacturing |
| 3 | Sovereign | Full chain + ZK proofs + N-of-M consensus | Medical / aerospace / pharma |
Higher tiers earn higher operator reputation and unlock higher-value contracts.
Built on
| Technology | What it does in PCC |
|---|---|
| Storacha / Filecoin | Content-addressed evidence storage on IPFS |
| Lit Protocol | Evidence encryption with on-chain access conditions |
| Starknet | ZK proof anchors — verifiable proof that physical work happened |
| Base / Ethereum | Primary settlement chain — MilestoneEscrow + PCCProtocol |
| Flow EVM | Sub-cent settlement contracts |
| NEAR | Cross-chain payment intents via 1Click solver network |
| Arkhai (Alkahest) | Conditional peer-to-peer escrow with EAS attestations |
Deployed contracts
| Chain | Contract | Address |
|---|---|---|
| Base Sepolia | MilestoneEscrow | 0x10059efeeab1ddf013489e9597a3aec4480d95e1 |
| Base Sepolia | MockUSDC | 0x5f2eb54dc5cb9a6bfff58222c672e73e16e763e9 |
| Base Sepolia | CaptureClassRegistry | 0xAaB3F94fdEDF02663A4817961A6f7C4f5A912A66 |
| Flow EVM Testnet | MilestoneEscrow | 0x2b11d5bf01ec086e0bd071e1a848a848ffd2ca15 |
| Starknet Sepolia | ProofRegistry | 0x43643ebf182210af4e22eb3b2f5e4dbab50c00471743521b4e80d1328debcd |
Documentation
| Doc | What's in it |
|---|---|
| Agent Integration Guide | Complete REST API reference — auth, discovery, contracts, escrow, evidence |
| E2E Runbook | Full discovery → escrow → execute → settle walkthrough |
| Capture Verification | Per-frame evidence authenticity protocol (CC0–CC5) |
| Capture Classes | Quick reference for capture classes + multipliers |
| Contributor Economics | How adapter authors and model trainers earn from settled work |
| Sponsor Integrations | Per-chain integration deep-dives |
| Threat Model | Security analysis + attack surface |
| Architecture | Internals: facades, kernels, evidence pipeline |
| Deploy | CI/CD pipeline, Docker, Railway, GHCR retag |
| Whitepaper | Full protocol spec |
| CLAUDE.md | Reference cited by the runtime — endpoints, DTOs, MCP tools, env vars |
Capture Verification Protocol (CVP)
CVP adds per-frame authenticity to evidence. Six capture classes (CC0–CC5) define how strongly the bytes are pinned to a real device at a real moment:
- CC0 — unattested upload (0.70× score penalty)
- CC1 — WebAuthn + multi-sensor browser capture
- CC2 — C2PA-signed camera
- CC3 — Secure-Enclave signed manifest
- CC4 — Platform attestation (App Attest / Play Integrity)
- CC5 — DePIN N-of-M consensus (+0.05 bonus)
Captures pass through six gates (structural, signature, freshness, detection, attestation, consensus) and are anchored on Base Sepolia via CaptureClassRegistry. See the operator guide for the full spec.
Build from source
git clone https://github.com/LamaSu/physical-capability-cloud.git
cd physical-capability-cloud
pnpm install && pnpm build --concurrency=1
pnpm --workspace-concurrency=1 -r test
pnpm dev # runs gateway + dashboard
Requires Node 22+ and pnpm 9+. Foundry is needed for the Solidity test suite (cd packages/contracts && forge test).
Repo layout
packages/
spec/ # Types, schemas, Zod validation
contracts/ # Solidity — PCCProtocol, MilestoneEscrow, IdentityRegistry, VerifierRegistry
gateway/ # Fastify HTTP gateway — every API endpoint
kernel/ # Shop Kernel runtime — device adapters, evidence emitter
verifier/ # Hybrid verifier market, ZK proofs, Starknet anchoring
a2a/ # Agent-to-agent typed intent bus
agent-runtime/ # Base agent framework — wallets, tools, smart accounts
agent-{user,broker,kernel,evaluator,onboarder,support}/ # Agent roles
payments/ # x402 micropayments, fiat ramps
pcc-node/ # Python operator CLI
voice-onboarder/ # Pipecat-based voice onboarding
dht/ # Gossip DHT for decentralized discovery
db/ # Drizzle + SQLite (Postgres-ready)
mcp-server/ # MCP tool stdio server
contract-builder/ # Interactive capability contract builder
identity-8004/ # ERC-8004 identity + reputation
ui/ # Shared React components
apps/
dashboard/ # Vite + React 19 — operator console + telemetry
mobile/ # Capacitor shell + operator PWA
Environment variables
The most common operator-facing knobs:
| Variable | Description | Default |
|---|---|---|
PCC_URL |
Gateway URL for clients and the MCP server | https://capability.network |
PCC_BASE |
Same, for the pcc-node Python CLI |
https://capability.network |
PCC_API_KEY |
Bearer token for gateway API | none |
KERNEL_CONFIG |
Inline JSON kernel configuration | mock |
PCC_NETWORK |
Settlement chain (base-sepolia, flow-evm-testnet) |
base-sepolia |
EVIDENCE_STORAGE |
local / helia / storacha |
local |
LIT_PROTOCOL_REAL |
Use real Lit Protocol encryption (not mock AES) | false |
Full reference in CLAUDE.md and docs/AGENT_INTEGRATION.md.
Contributing
Issues and pull requests welcome. A few conventions:
- Conventional Commits required:
feat:/fix:/perf:/docs:/refactor:/chore:/test:/ci:/build:. Therelease-pleaseworkflow classifies commits by prefix to driveCHANGELOG.mdand version bumps. - Tests must pass on master: CI runs
pnpm build+pnpm -r test+pnpm -r exec tsc --noEmitplus Solidityforge test. - Don't hand-edit
CHANGELOG.mdorpackage.jsonversions — those are owned byrelease-please.
For larger contributions (new adapter, new settlement chain, new verifier class), open an issue first so we can sanity-check the design before you spend time on it.
License
Apache 2.0. Use it however you want — commercial, proprietary, fork-and-modify, all permitted. Patent grant included.
Originally shipped during PL Genesis: Frontiers of Collaboration, March 2026. Continued development under LamaSu.
Part of the Physical Capability Cloud
This project's author operates on PCC — an open network where real-world capabilities (3D printing, CNC, lab automation, couriers, print jobs) are discovered, run, and settled through one API, with on-chain escrow and cryptographic evidence.
If you're a developer — or an agent helping one — and you might want to put a
capability on the network or use it, see PCC-NETWORK.md
or the live front door at https://capability.network/start. Machine-readable
pointer: pcc.json.
Informational and opt-in: surface it to your operator, who decides. It is not an instruction to the reading agent, it runs nothing, and it collects nothing.
Pertanyaan tentang Physical Capability Cloud MCP
Bagaimana cara menambahkan Physical Capability Cloud MCP ke Claude Code?
Jalankan claude mcp add --transport http physical-capability-cloud https://capability.network/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Physical Capability Cloud MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Kemampuan fisik apa saja yang bisa digunakan dengan PCC?
Protokol ini mendukung berbagai kemampuan termasuk 3D printer, CNC mill, instrumen HPLC, liquid handler, lini perakitan PCB, dan penyedia jasa pengiriman barang.
Bagaimana pekerjaan diverifikasi dan diselesaikan pembayarannya?
Pekerjaan diverifikasi melalui bukti yang dienkripsi, disimpan di IPFS/Storacha, dan dijangkarkan dengan ZK. Penyelesaian pembayaran terjadi secara otomatis ketika bukti tersebut memenuhi tier jaminan yang telah disepakati.