Physical Capability Cloud MCP server
2026년 11월 14일 커밋검증 가능한 프로토콜을 통해 AI agent가 3D 프린팅 및 실험실 자동화와 같은 실제 물리적 서비스를 검색, 협상 및 예약할 수 있도록 지원합니다.
다른 이름 LamaSu/physical-capability-cloud, physical-capability-cloud
- 스타
- 3
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 2.19.0
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- Apache-2.0
Physical Capability Cloud MCP란?
검증 가능한 프로토콜을 통해 AI agent가 3D 프린팅 및 실험실 자동화와 같은 실제 물리적 서비스를 검색, 협상 및 예약할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Physical Capability Cloud MCP server 정보
Physical Capability Cloud는 물리적 하드웨어를 프로그래밍 가능한 서비스로 전환하기 위한 개방형 프로토콜을 제공합니다. AI agent와 개발자는 이를 통해 3D 프린팅, CNC 밀링, 실험실 자동화와 같은 실제 작업을 검색, 협상 및 예약할 수 있습니다. 이 시스템은 운영자가 하드웨어를 실행하고 고객이 HTTP를 통해 작업을 계약하는 기반 역할을 하며, 실행 단계에서 양측을 보호하기 위해 온체인 에스크로를 사용합니다.
사용자는 JSON schema 패키지를 가져와 AI agent를 연결하거나 Claude Code와 같은 도구에서 사용할 MCP server를 배포할 수 있습니다. 운영자는 하드웨어를 자동 검색하고 API key를 프로비저닝하는 Python 노드를 사용하여 장비를 통합할 수 있습니다. 이 프로토콜은 단순한 자기 증명 방식의 장치 스냅샷부터 의료 또는 항공우주 제조와 같은 규제 산업을 위한 주권적 ZK-anchored 증명에 이르기까지 다양한 assurance tier를 통해 신뢰를 보장합니다. 암호화된 증거가 합의된 계약 요구 사항을 충족하면 정산이 자동으로 완료됩니다.
활용 사례
- 1자동 3D 프린팅 조달AI agent가 유휴 상태인 FDM 프린터를 찾아 에스크로에 자금을 예치하고, 스트리밍되는 증거를 통해 프린팅 과정을 모니터링할 수 있습니다.
- 2원격 실험실 분석개발자는 agent를 사용하여 다른 국가에 위치한 규제 대상 실험실에 화학 화합물 분석 작업을 예약할 수 있습니다.
- 3복잡한 다단계 제조agent가 대규모 제조 요청을 개별 단계로 분해하고 프로세스의 각 부분에 대해 서로 다른 제공업체를 고용할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Physical Capability Cloud MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Physical Capability Cloud MCP 설치
$ claude mcp add --transport http physical-capability-cloud https://capability.network/mcpCursor에 Physical Capability Cloud MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"physical-capability-cloud": {
"url": "https://capability.network/mcp"
}
}
}VS Code에 Physical Capability Cloud MCP 설치
.vscode/mcp.json
{
"servers": {
"physical-capability-cloud": {
"type": "http",
"url": "https://capability.network/mcp"
}
}
}VS Code CLI에 Physical Capability Cloud MCP 설치
$ code --add-mcp '{"name":"physical-capability-cloud","type":"http","url":"https://capability.network/mcp"}'Codex에 Physical Capability Cloud MCP 설치
$ codex mcp add physical-capability-cloud --url https://capability.network/mcpCodex config.toml에 Physical Capability Cloud MCP 설치
~/.codex/config.toml
[mcp_servers.physical-capability-cloud] url = "https://capability.network/mcp"
Gemini CLI에 Physical Capability Cloud MCP 설치
$ gemini mcp add -s user --transport http physical-capability-cloud https://capability.network/mcpGemini settings.json에 Physical Capability Cloud MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"physical-capability-cloud": {
"url": "https://capability.network/mcp",
"type": "http"
}
}
}구성
PCC_URL
| 이름 | 설명 | 유형 |
|---|---|---|
| PCC_URL | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능lamasu/physical-capability-cloud is public and reachablegithub.com/lamasu/physical-capability-cloud ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-11github.com/lamasu/physical-capability-cloud ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답initialize answered with protocol 2025-06-18 in 531 ms통과
README
GitHub에서 보기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 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.
Physical Capability Cloud MCP 질문
Physical Capability Cloud MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http physical-capability-cloud https://capability.network/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Physical Capability Cloud MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
PCC로 어떤 종류의 물리적 기능을 사용할 수 있나요?
이 프로토콜은 3D 프린터, CNC 밀링 머신, HPLC 장비, 액체 핸들러, PCB 조립 라인 및 화물 운송업체를 포함한 다양한 기능을 지원합니다.
작업 검증과 정산은 어떻게 이루어지나요?
작업은 암호화되어 IPFS/Storacha에 저장되고 ZK-anchored된 증거를 통해 검증됩니다. 증거가 합의된 assurance tier를 충족하면 정산이 자동으로 이루어집니다.