Physical Capability Cloud

Connect Remote server

claude mcp add --transport http physical-capability-cloud https://capability.network/mcp

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

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

Settings > Connectors > Add custom connector
URL: https://capability.network/mcp

Tools 80 found in our last check

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

• 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

  List 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 assurance tiers or availability. The gateway does not read the qu…

• get_build_options

  Get 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_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 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.

• 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

  Record a capability as an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Any ipId, NFT token id or transaction hash in the reply is a placeholder, and no royalty is paid.

• register_job_evidence_ip

  Record job evidence as a derivative of a capability's IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Any id or transaction hash in the reply is a placeholder, and no royalty is paid.

• distribute_royalties

  Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No revenue is paid…

• pay_ip_royalty

  Record a royalty payment to an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No tokens move, and any transaction hash in the reply is a placeholder.

• claim_ip_revenue

  Claim an IP asset's recorded revenue. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Nothing is paid out: any amount or transaction hash in the reply is a placeholder.

• get_ip_revenue

  Get the revenue PCC has recorded for an IP asset. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. No revenue has been paid: any figure in the reply is a placeholder.

• get_ip_lineage

  Get the IP lineage PCC has recorded for an asset: parent capabilities and derivative job records. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain.

• get_capability_ip

  Get the IP record PCC holds for a capability by its capability ID. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain. Any id or transaction hash in it is a placeholder.

• raise_ip_dispute

  Record an IP dispute against an asset. Provide evidence hash and reason. Story Protocol (now The DATA Foundation). These tools make no on-chain call: nothing is registered, claimed or disputed on chain.

• get_operator_dashboard

  Not available: no route answers GET /api/operator on this gateway. The operator's real kernels, devices and in-flight jobs are at GET /api/agent/me.

• get_operator_machines

  Answers 501 not_available: operator machines with utilization and uptime are not recorded on this gateway. The operator's real kernels, devices and in-flight jobs are at GET /api/agent/me.

• get_operator_earnings

  Answers 501 not_available: operator earnings history is not recorded on this gateway. Per-job payment state is at GET /api/jobs/:jobId/execution.

• get_operator_certs

  Answers 501 not_available: operator certifications are not recorded on this gateway (there is no certification store; certifications typed at registration are the operator's own claim and are not checked).

• get_sensor_channels

  List all registered sensor channels across kernels. Returns channel descriptors with units and ranges.

• get_kernel_sensors

  Get sensor channels for a specific kernel. Returns live channel descriptors.

• get_settlement_status

  Get settlement pipeline status including pending operations count, total value queued, and smart account address.

• get_settlement_epochs

  Get settlement epoch history showing past batch settlements with timing and operation counts.

• onboard_machine

  Register a new machine on the PCC network. Provide machine details to create a registration record. Include `operator` ({walletAddress, displayName, email}): without it the registration is recorded as operator 0x0000000000000000000000000000000000000000 / "Unknown", and prove can…

• analyze_machine_docs

  AI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.

• redeem_invite

  One-click agent onboarding with an invite code. Provisions wallet, identity, LLM access, and PCC tools in a single call.

• check_invite

  Validate an invite code before redeeming it. Returns whether the code is valid and what it includes.

• list_batches

  List active and completed settlement batches.

• list_evidence

  List encrypted evidence bundles stored in the gateway.

• submit_demand

  Record that you want a capability no operator offers yet. The gateway keeps the signal in memory, publishes no demand yet, and creates no bounty.

• list_bounties

  List bounties. No gateway route creates a bounty and none is funded, so expect an empty list; no bounty pays anything.

• claim_bounty

  Ask to take on a bounty as the authenticated operator. No gateway route creates a bounty, so the request finds none (409); no bounty is funded or pays anything.

• verify_bounty

  Retired: the gateway answers 410 and changes no state. No caller can mark a bounty verified.

• get_top_demand

  Get demand aggregated by capability type. The gateway doesn't publish demand yet: it answers an empty list marked `suppressed`.

• get_bounty_leaderboard

  Get the bounty leaderboard. No gateway route creates or verifies a bounty, so expect an empty list.

Details

More developer tools servers See all

• AGILEX Docs

  Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.

• Echoo public catalog

  Read-only Echoo product facts, pricing, documentation and published writing skills.

• 99tests

  Order human-run real-device app tests from your coding agent; verified bugs return as fix prompts.

• LimitReceipts by aiw3b

  Find the AI coding/app-builder plan that fits your usage: limits, prices and plan-fit picks.

• Candor UI docs

  Candor UI docs and component suggestions. Read-only, no key, never serves paid source.

• MoneyTools Tools

  Call for a cheap read-only utility: 100+ tools; free daily tier; not charged on failure