Physical Capability Cloud

Last 30 days

Uptime

100%

Response time

352 ms typical, 404 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "physical-capability-cloud": {
      "type": "http",
      "url": "https://capability.network/mcp"
    }
  }
}

256 tools

• 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.

Security scan

• Mentions credentials or secret files in tool:get_write_status
  tions are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
• Mentions credentials or secret files in tool:protocol_create_escrow
  tracking built in. Requires PCC_GATEWAY_PRIVATE_KEY write access.

Recent checks