Categories › AI & Agents › Multi-agent, orchestration & workflows
Discover, hire, and verify real-world physical capability through MCP.
Remote server: your requests and data go to capability.network. Claude Code: claude mcp add --transport http physical-capability-cloud https://capability.network/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 list_api_keys — List all active API keys for the authenticated operator. Returns key IDs, prefixes, scopes, rate limits, usage counts, and creation/expiry trevoke_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 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 esetup_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,setup_test_job — Submit a test job for one device on a kernel (Step 4 of onboarding). The gateway runs it only for a kernel it operates in-process; for any osetup_status — Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green belist_capability_types — List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.search_capabilities — List the built-in capability type templates: each type's name, version, description, parameter count, parameter group names and a base priceget_build_options — Get configuration options for a capability type: parameter groups, each parameter's definition, and a base price hint. It includes no assuracalculate_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 their milestone counts. Optionally filter by escrow 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 bloget_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.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 archiget_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.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.