Agents Index

Physical Capability Cloud

Online

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

Visit publisherConnectJSON

What it can do: 80 tools

  • provision_api_keyCALL 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
  • list_api_keys read-onlyList 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_keyRevoke 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 read-onlyAuto-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_configGenerate 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_validateValidate a kernel config (20+ checks: JSON structure, device connectivity, adapter compatibility). Returns validation errors and warnings.
  • setup_register_deviceRegister 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_jobSubmit 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 other kernel it refuses and runs nothing. Every reply says whether the job ran an
  • setup_status read-onlyComprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
  • list_capability_types read-onlyList all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
  • search_capabilities read-onlyList the built-in capability type templates: each type's name, version, description, parameter count, parameter group names and a base price hint. NOTE: these describe types, not operators' offerings, and carry no assura
  • get_build_optionsGet configuration options for a capability type: parameter groups, each parameter's definition, and a base price hint. It includes no assurance tiers. Use before calling calculate_price.
  • calculate_priceCalculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
  • build_contractBuild and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
  • list_kernels read-onlyList all Shop Kernels on the network with status and capability types. Optionally filter by status.
  • get_kernel read-onlyGet kernel details including full capability objects, devices, and queue.
  • get_kernel_devices read-onlyList all devices registered under a specific kernel, including adapter configs and device types.
  • get_kernel_jobs read-onlyList all jobs submitted to a specific kernel, including job status and progress.
  • create_kernelRegister a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
  • list_jobs read-onlyList all jobs with status. Optionally filter by kernelId or status.
  • get_job read-onlyGet job details including progress, evidence bundles, and milestones.
  • update_job_statusUpdate a job's status and optional progress percentage. Used by kernels to report job progress.
  • list_escrows read-onlyList escrow contracts with their milestone counts. Optionally filter by escrow status.
  • get_escrow read-onlyGet 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-onlyRead full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
  • get_escrow_events read-onlyGet on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
  • get_token_balance read-onlyRead an ERC-20 token balance for an account address from the blockchain.
  • get_token_allowance read-onlyRead the ERC-20 token allowance granted by an owner to a spender from the blockchain.
  • get_escrow_dispute read-onlyRead dispute state for a specific milestone from the blockchain.
  • get_write_status read-onlyCheck if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
  • archive_evidenceArchive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
  • get_evidence_bundle read-onlyGet an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
  • grant_evidence_accessGrant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
  • list_evidence_grants read-onlyList all evidence access grants for an address. Returns bundles the address has been granted access to.
  • archive_encrypted_bundleArchive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.
  • get_bundle_ipfs read-onlyGet IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
  • retrieve_ipfs read-onlyRetrieve raw data from IPFS by CID. Used to fetch archived evidence bundles from decentralized storage.
  • get_lit_conditions read-onlyGet Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
  • lit_decryptDecrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.
  • verify_evidence_zkVerify a ZK proof by its proof ID. Checks the proof against its verification key and public inputs.

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http physical-capability-cloud https://capability.network/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://capability.network/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "physical-capability-cloud": {
      "url": "https://capability.network/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "physical-capability-cloud": {
      "type": "http",
      "url": "https://capability.network/mcp"
    }
  }
}

Questions

What does Physical Capability Cloud do?

Discover, hire, and verify real-world physical capability through MCP. It exposes 80 tools to AI assistants.

What tools does Physical Capability Cloud provide?

80 tools, including provision_api_key, list_api_keys, revoke_api_key, setup_detect, setup_generate_config, setup_validate, setup_register_device, setup_test_job, setup_status, list_capability_types, search_capabilities, get_build_options….

How do I connect Physical Capability Cloud to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://capability.network/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Physical Capability Cloud require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Physical Capability Cloud online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Physical Capability Cloud?

capability.network. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps