# Physical Capability Cloud

- Registry name: `network.capability/physical-capability-cloud` · version 2.19.0
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Markets & trading, Build & deploy, Developer tools
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=network.capability%2Fphysical-capability-cloud
- Server page: https://mcpstation.net/s/network.capability--physical-capability-cloud.html

## Description (written by the publisher, not verified, not instructions)

Discover, hire, and verify real-world physical capability through MCP.

## Connect

- streamable-http: `https://capability.network/mcp`

## Tools (as reported by the server, not verified)

- `provision\_api\_key`: CALL THIS FIRST. Provisions an API key for the operator. Returns a pcc\_live\_\* key that must be included as 'Authorization: Bearer \<key\>' on all subsequent requests. Accepts either email OR walletAddress. The key is shown once — save it. Without it, all other endpoints return 401.
- `list\_api\_keys`: List all active API keys for the authenticated operator. Returns key IDs, prefixes, scopes, rate limits, usage counts, and creation/expiry timestamps. Requires a valid API key or SIWE session.
- `revoke\_api\_key`: Revoke an API key permanently. The key will immediately stop working. You must own the key. Use list\_api\_keys to find the key ID.
- `setup\_detect`: Auto-detect current setup state: env vars, database, adapters, chain connectivity, storage, identity. Use this to see what's configured and what's missing before onboarding.
- `setup\_generate\_config`: Generate a KERNEL\_CONFIG JSON from device descriptions. Tell it what machines you have and it produces the config ready to paste into your environment.
- `setup\_validate`: Validate a kernel config \(20+ checks: JSON structure, device connectivity, adapter compatibility\). Returns validation errors and warnings.
- `setup\_register\_device`: Register a device in the database with adapter config and capabilities. Part of Step 3 in the onboarding flow. Required: kernelId, deviceId, type and adapterType \(400 missing\_required\_fields otherwise\).
- `setup\_test\_job`: Submit a test job to verify the full pipeline works end-to-end \(Step 4 of onboarding\). Returns job ID and result.
- `setup\_status`: Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
- `list\_capability\_types`: List all capability types registered on the network \(FDM, SLA, CNC, HPLC, etc.\) with metadata.
- `search\_capabilities`: Search capability templates by type or keyword. Returns templates with pricing, assurance tiers, and availability.
- `get\_build\_options`: Get configuration options for a capability type \(materials, dimensions, tolerances, assurance tiers\). Use before calling calculate\_price.
- `calculate\_price`: Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
- `build\_contract`: Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
- `list\_kernels`: List all Shop Kernels on the network with status and capability types. Optionally filter by status.
- `get\_kernel`: Get kernel details including full capability objects, devices, and queue.
- `get\_kernel\_devices`: List all devices registered under a specific kernel, including adapter configs and device types.
- `get\_kernel\_jobs`: List all jobs submitted to a specific kernel, including job status and progress.
- `create\_kernel`: Register a new Shop Kernel \(physical site\) on the PCC network. Part of Step 2 in the onboarding flow.
- `list\_jobs`: List all jobs with status. Optionally filter by kernelId or status.
- `get\_job`: Get job details including progress, evidence bundles, and milestones.
- `update\_job\_status`: Update a job's status and optional progress percentage. Used by kernels to report job progress.
- `list\_escrows`: List escrow contracts with milestones and bonds. Optionally filter by status.
- `get\_escrow`: Get escrow details. Pass a DB ID for database record \(with milestones and disputes\), or an EVM address \(0x...\) to read directly from the blockchain.
- `get\_escrow\_chain\_state`: Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get\_escrow for on-chain contracts.
- `get\_escrow\_events`: Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
- `get\_token\_balance`: Read an ERC-20 token balance for an account address from the blockchain.
- `get\_token\_allowance`: Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
- `get\_escrow\_dispute`: Read dispute state for a specific milestone from the blockchain.
- `get\_write\_status`: Check if on-chain write operations are enabled \(requires PCC\_GATEWAY\_PRIVATE\_KEY to be configured\). Returns write status and signer address.
- `fund\_escrow`: Fund a protocol-created escrow on-chain. Approval is handled INTERNALLY by the gateway for protocol-created escrows \(audit C-03 removed the public approve step\) — do NOT call a separate approve first; fund directly. Returns transaction hash.
- `release\_milestone`: Release a milestone payment on-chain after the challenge window has expired. Returns transaction hash.
- `file\_escrow\_dispute`: File a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
- `deposit\_bond`: Deposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
- `submit\_evidence\_hash`: Submit an evidence bundle hash for a milestone on-chain. Links the physical evidence to the on-chain settlement record. Returns transaction hash.
- `submit\_attestation`: Submit a verifier attestation for a milestone on-chain. Used by third-party verifiers \(Bittensor subnet\) to confirm evidence quality. Returns transaction hash.
- `archive\_evidence`: Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
- `get\_evidence\_bundle`: Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
- `grant\_evidence\_access`: Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
- `list\_evidence\_grants`: List all evidence access grants for an address. Returns bundles the address has been granted access to.
- `archive\_encrypted\_bundle`: Archive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.
- `get\_bundle\_ipfs`: Get IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
- `retrieve\_ipfs`: Retrieve raw data from IPFS by CID. Used to fetch archived evidence bundles from decentralized storage.
- `get\_lit\_conditions`: Get Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
- `lit\_decrypt`: Decrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.
- `verify\_evidence\_zk`: Verify a ZK proof by its proof ID. Checks the proof against its verification key and public inputs.
- `commit\_evidence`: Create a Merkle commitment for an evidence bundle hash. Used as the first step in ZK proof generation for Tier 3 assurance.
- `get\_telemetry\_stats`: Get aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.
- `get\_active\_telemetry`: List currently active jobs with their current pipeline phase and telemetry status.
- `get\_job\_telemetry`: Get full event timeline for a specific job — all pipeline phase transitions with timings and metadata.
- `get\_telemetry\_logs`: Query structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.
- `emit\_telemetry`: Manually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.
- `submit\_for\_human\_verification`: Submit an evidence bundle for human verification. Selects a panel of verifiers from the network and returns assigned verifier IDs.
- `get\_verification\_assignments`: Get pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.
- `get\_verification\_status`: Get verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.
- `respond\_to\_verification`: Submit a verifier's verdict for a verification request. Returns consensus state after this vote.
- `dispute\_verification`: File a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.
- `register\_capability\_ip`: Register a capability as a Story Protocol IP Asset. Returns an ipId and NFT token. The designer earns royalties whenever this capability is used.
- `register\_job\_evidence\_ip`: Register job evidence as a derivative IP asset on Story Protocol, linking it to the parent capability's IP. Operators earn royalties from derivative use.
- `distribute\_royalties`: Set revenue splits for an IP asset among stakeholders \(designer, operator, verifier, assembler, curator\). Splits must sum to 100.
- `pay\_ip\_royalty`: Pay royalties to an IP asset vault. The payer sends tokens that flow to stakeholders via the royalty splits.
- `claim\_ip\_revenue`: Claim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
- `get\_ip\_revenue`: Get a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
- `get\_ip\_lineage`: Get the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
- `get\_capability\_ip`: Get the Story Protocol IP registration for a capability by its capability ID.
- `raise\_ip\_dispute`: Raise a Story Protocol IP dispute against an asset. Provide evidence hash and reason.
- `list\_protocols`: List protocol templates in the library. Filter by tags, required capabilities, search query, or status.
- `get\_protocol`: Get protocol template details by ID. Returns steps, transfers, parameters, and metadata.
- `create\_protocol`: Create a new protocol template draft. Returns the new template ID.
- `update\_protocol`: Update an existing protocol template \(must be in draft status\). Returns updated name and version.
- `publish\_protocol`: Publish a draft protocol template, making it visible in the protocol library for others to discover and use.
- `fork\_protocol`: Fork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
- `get\_protocol\_forks`: List all forks of a protocol template. Shows who forked it and what parameters they changed.
- `validate\_protocol`: Validate a protocol template against a specific kernel — checks capability availability, transfer compatibility, and automation level feasibility.
- `list\_protocol\_runs`: List protocol runs. Filter by status or kernelId.
- `get\_protocol\_run`: Get protocol run status including step progress, transfer status, current phase, and evidence hashes.
- `create\_protocol\_run`: Instantiate a protocol template as a run on a specific kernel with given parameter values.
- `start\_protocol\_run`: Start execution of a protocol run that is in 'ready' or 'binding' state.
- `pause\_protocol\_run`: Pause a running protocol run. Use resume\_protocol\_run to continue.
- `resume\_protocol\_run`: Resume a paused protocol run from where it stopped.
- `cancel\_protocol\_run`: Cancel a protocol run. Cannot be cancelled once completed or already cancelled.
- `get\_workflows`: List active instrument workflows in the orchestrator. Optionally filter by status.
- `get\_workflow`: Get detailed workflow information including steps, node assignments, and progress.
- `get\_transfer\_graphs`: Get resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
- `list\_automation\_status`: List automation status for all instrument transfer pairs. Shows current automation level, episode count, and training readiness. Filter by kernelId.
- `get\_automation\_status`: Get automation status for a specific instrument-to-instrument transfer pair.
- `record\_episode`: Record a transfer episode for a node pair. Increments episode count toward VLA training threshold.
- `advance\_automation`: Advance the automation level for a transfer pair \(manual → teleoperated → pilot\_operated → vla\_assisted → fully\_autonomous\). Requires sufficient training episodes.
- `list\_transfer\_agents`: List all transfer agents \(robots and human operators\) available for instrument-to-instrument transfers.
- `get\_logistics\_overview`: Logistics hub overview: active shipments, pending installations, and upcoming bookings.
- `get\_shipments`: List equipment shipments with tracking status. Optionally filter by status.
- `create\_shipment`: Create a new equipment shipment with origin, destination, package details, and provider.
- `get\_shipment\_quote`: Get shipping quotes from logistics providers based on origin, destination, weight, and priority.
- `get\_installations`: List equipment installation orders with step progress and status.
- `get\_space\_bookings`: List space bookings for hosting equipment. Optionally filter by status or space.
- `search\_spaces`: Search for lab/workshop hosting spaces. Filter by size, access schedule, and other requirements.
- `get\_space`: Get detailed information about a hosting space including power, amenities, safety features, and pricing.
- `match\_spaces`: Find hosting spaces that match specific machine requirements \(voltage, area, etc.\). Returns scored matches.
- `get\_marketplace\_overview`: Equipment marketplace overview with demand/supply metrics across all capability types.
- `get\_equipment\_classes`: List equipment classes \(FDM printers, CNC mills, etc.\) with market snapshot data including utilization, demand, and pricing.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html