# Physical Capability Cloud

> Physical Capability Cloud, an MCP server by capability.network, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Discover, hire, and verify real-world physical capability through MCP.

- Canonical: https://www.anchorterminal.com/tools/physical-capability-cloud
- Markdown: https://www.anchorterminal.com/tools/physical-capability-cloud.md (~11,650 tokens)
- Slim: https://www.anchorterminal.com/tools/physical-capability-cloud.min.md (~11,580 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/physical-capability-cloud.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

# Physical Capability Cloud

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by capability.network (https://capability.network)
- Category: Cloud & infrastructure (https://www.anchorterminal.com/categories/infrastructure.md)
- Listed because: It's published in the registry under capability.network, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: Discover, hire, and verify real-world physical capability through MCP.

## Facts

- MCP registry: `network.capability/physical-capability-cloud` 2.19.0
- Endpoint: https://capability.network/mcp (streamable HTTP)
- Source: https://github.com/LamaSu/physical-capability-cloud
- Website: https://capability.network
- GitHub stars: 2
- Registry entry updated: 2026-07-13

## Tools

- Tools it lists (256, about 43,488 tokens of context, `tools/list` without credentials over MCP 2025-11-25, checked 2026-10-04 22:25 UTC):
  - `provision_api_key` (writes): 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…
  - `list_api_keys` (read-only): List all active API keys for the authenticated operator. Returns key IDs, prefixes, scopes, rate limits, usage counts, and creation/expiry timestamps. Requires…
  - `revoke_api_key` (writes): 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` (read-only): Auto-detect current setup state: env vars, database, adapters, chain connectivity, storage, identity. Use this to see what's configured and what's missing…
  - `setup_generate_config` (writes): 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` (writes): Validate a kernel config (20+ checks: JSON structure, device connectivity, adapter compatibility). Returns validation errors and warnings.
  - `setup_register_device` (writes): Register a device in the database with adapter config and capabilities. Part of Step 3 in the onboarding flow. Required: kernelId, deviceId, type and…
  - `setup_test_job` (writes): Submit a test job to verify the full pipeline works end-to-end (Step 4 of onboarding). Returns job ID and result.
  - `setup_status` (read-only): Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
  - `list_capability_types` (read-only): List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
  - `search_capabilities` (read-only): Search capability templates by type or keyword. Returns templates with pricing, assurance tiers, and availability.
  - `get_build_options` (writes): Get configuration options for a capability type (materials, dimensions, tolerances, assurance tiers). Use before calling calculate_price.
  - `calculate_price` (writes): Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
  - `build_contract` (writes): Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
  - `list_kernels` (read-only): List all Shop Kernels on the network with status and capability types. Optionally filter by status.
  - `get_kernel` (read-only): Get kernel details including full capability objects, devices, and queue.
  - `get_kernel_devices` (read-only): List all devices registered under a specific kernel, including adapter configs and device types.
  - `get_kernel_jobs` (read-only): List all jobs submitted to a specific kernel, including job status and progress.
  - `create_kernel` (writes): Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
  - `list_jobs` (read-only): List all jobs with status. Optionally filter by kernelId or status.
  - `get_job` (read-only): Get job details including progress, evidence bundles, and milestones.
  - `update_job_status` (writes): Update a job's status and optional progress percentage. Used by kernels to report job progress.
  - `list_escrows` (read-only): List escrow contracts with milestones and bonds. Optionally filter by status.
  - `get_escrow` (read-only): 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-only): 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` (read-only): Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
  - `get_token_balance` (read-only): Read an ERC-20 token balance for an account address from the blockchain.
  - `get_token_allowance` (read-only): Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
  - `get_escrow_dispute` (read-only): Read dispute state for a specific milestone from the blockchain.
  - `get_write_status` (read-only): Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
  - `fund_escrow` (writes): 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…
  - `release_milestone` (writes): Release a milestone payment on-chain after the challenge window has expired. Returns transaction hash.
  - `file_escrow_dispute` (writes): File a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
  - `deposit_bond` (writes): Deposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
  - `submit_evidence_hash` (writes): 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` (writes): 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` (writes): Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
  - `get_evidence_bundle` (read-only): Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
  - `grant_evidence_access` (writes): Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
  - `list_evidence_grants` (read-only): List all evidence access grants for an address. Returns bundles the address has been granted access to.
  - `archive_encrypted_bundle` (writes): 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` (read-only): Get IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
  - `retrieve_ipfs` (read-only): Retrieve raw data from IPFS by CID. Used to fetch archived evidence bundles from decentralized storage.
  - `get_lit_conditions` (read-only): Get Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
  - `lit_decrypt` (writes): Decrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.
  - `verify_evidence_zk` (writes): Verify a ZK proof by its proof ID. Checks the proof against its verification key and public inputs.
  - `commit_evidence` (writes): 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` (read-only): Get aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.
  - `get_active_telemetry` (read-only): List currently active jobs with their current pipeline phase and telemetry status.
  - `get_job_telemetry` (read-only): Get full event timeline for a specific job — all pipeline phase transitions with timings and metadata.
  - `get_telemetry_logs` (read-only): Query structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.
  - `emit_telemetry` (writes): Manually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.
  - `submit_for_human_verification` (writes): Submit an evidence bundle for human verification. Selects a panel of verifiers from the network and returns assigned verifier IDs.
  - `get_verification_assignments` (read-only): Get pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.
  - `get_verification_status` (read-only): Get verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.
  - `respond_to_verification` (writes): Submit a verifier's verdict for a verification request. Returns consensus state after this vote.
  - `dispute_verification` (writes): File a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.
  - `register_capability_ip` (writes): 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` (writes): 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` (writes): Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100.
  - `pay_ip_royalty` (writes): Pay royalties to an IP asset vault. The payer sends tokens that flow to stakeholders via the royalty splits.
  - `claim_ip_revenue` (writes): Claim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
  - `get_ip_revenue` (read-only): Get a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
  - `get_ip_lineage` (read-only): Get the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
  - `get_capability_ip` (read-only): Get the Story Protocol IP registration for a capability by its capability ID.
  - `raise_ip_dispute` (writes): Raise a Story Protocol IP dispute against an asset. Provide evidence hash and reason.
  - `list_protocols` (read-only): List protocol templates in the library. Filter by tags, required capabilities, search query, or status.
  - `get_protocol` (read-only): Get protocol template details by ID. Returns steps, transfers, parameters, and metadata.
  - `create_protocol` (writes): Create a new protocol template draft. Returns the new template ID.
  - `update_protocol` (writes): Update an existing protocol template (must be in draft status). Returns updated name and version.
  - `publish_protocol` (writes): Publish a draft protocol template, making it visible in the protocol library for others to discover and use.
  - `fork_protocol` (writes): Fork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
  - `get_protocol_forks` (read-only): List all forks of a protocol template. Shows who forked it and what parameters they changed.
  - `validate_protocol` (writes): Validate a protocol template against a specific kernel — checks capability availability, transfer compatibility, and automation level feasibility.
  - `list_protocol_runs` (read-only): List protocol runs. Filter by status or kernelId.
  - `get_protocol_run` (read-only): Get protocol run status including step progress, transfer status, current phase, and evidence hashes.
  - `create_protocol_run` (writes): Instantiate a protocol template as a run on a specific kernel with given parameter values.
  - `start_protocol_run` (writes): Start execution of a protocol run that is in 'ready' or 'binding' state.
  - `pause_protocol_run` (writes): Pause a running protocol run. Use resume_protocol_run to continue.
  - `resume_protocol_run` (writes): Resume a paused protocol run from where it stopped.
  - `cancel_protocol_run` (writes): Cancel a protocol run. Cannot be cancelled once completed or already cancelled.
  - `get_workflows` (read-only): List active instrument workflows in the orchestrator. Optionally filter by status.
  - `get_workflow` (read-only): Get detailed workflow information including steps, node assignments, and progress.
  - `get_transfer_graphs` (read-only): Get resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
  - `list_automation_status` (read-only): List automation status for all instrument transfer pairs. Shows current automation level, episode count, and training readiness. Filter by kernelId.
  - `get_automation_status` (read-only): Get automation status for a specific instrument-to-instrument transfer pair.
  - `record_episode` (writes): Record a transfer episode for a node pair. Increments episode count toward VLA training threshold.
  - `advance_automation` (writes): Advance the automation level for a transfer pair (manual → teleoperated → pilot_operated → vla_assisted → fully_autonomous). Requires sufficient training…
  - `list_transfer_agents` (read-only): List all transfer agents (robots and human operators) available for instrument-to-instrument transfers.
  - `get_logistics_overview` (read-only): Logistics hub overview: active shipments, pending installations, and upcoming bookings.
  - `get_shipments` (read-only): List equipment shipments with tracking status. Optionally filter by status.
  - `create_shipment` (writes): Create a new equipment shipment with origin, destination, package details, and provider.
  - `get_shipment_quote` (writes): Get shipping quotes from logistics providers based on origin, destination, weight, and priority.
  - `get_installations` (read-only): List equipment installation orders with step progress and status.
  - `get_space_bookings` (read-only): List space bookings for hosting equipment. Optionally filter by status or space.
  - `search_spaces` (read-only): Search for lab/workshop hosting spaces. Filter by size, access schedule, and other requirements.
  - `get_space` (read-only): Get detailed information about a hosting space including power, amenities, safety features, and pricing.
  - `match_spaces` (writes): Find hosting spaces that match specific machine requirements (voltage, area, etc.). Returns scored matches.
  - `get_marketplace_overview` (read-only): Equipment marketplace overview with demand/supply metrics across all capability types.
  - `get_equipment_classes` (read-only): List equipment classes (FDM printers, CNC mills, etc.) with market snapshot data including utilization, demand, and pricing.
  - `get_demand_supply` (read-only): Get network-wide demand vs supply timeline data for capacity planning and market analysis.
  - `calculate_roi` (writes): Calculate ROI projection for onboarding equipment. Returns month-by-month revenue, cost, and break-even analysis.
  - `get_operator_dashboard` (read-only): 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` (read-only): 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…
  - `get_operator_earnings` (read-only): 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` (read-only): Answers 501 not_available: operator certifications are not recorded on this gateway (there is no certification store; certifications typed at registration are…
  - `get_sensor_channels` (read-only): List all registered sensor channels across kernels. Returns channel descriptors with units and ranges.
  - `get_kernel_sensors` (read-only): Get sensor channels for a specific kernel. Returns live channel descriptors.
  - `get_settlement_status` (read-only): Get settlement pipeline status including pending operations count, total value queued, and smart account address.
  - `get_settlement_epochs` (read-only): Get settlement epoch history showing past batch settlements with timing and operation counts.
  - `get_depin_stats` (read-only): DePIN treasury, soulbound capability certificates, and current reward epoch stats.
  - `mint_certificate` (writes): Mint a soulbound capability certificate (cNFT via Metaplex Core) for a kernel. Proves a verified capability on-chain as an immutable credential. Step 5 of…
  - `onboard_machine` (writes): Register a new machine on the PCC network. Provide machine details to create a registration record. Include `operator` ({walletAddress, displayName, email}):…
  - `analyze_machine_docs` (writes): AI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.
  - `redeem_invite` (writes): One-click agent onboarding with an invite code. Provisions wallet, identity, LLM access, and PCC tools in a single call.
  - `check_invite` (read-only): Validate an invite code before redeeming it. Returns whether the code is valid and what it includes.
  - `list_batches` (read-only): List active and completed settlement batches.
  - `list_evidence` (read-only): List encrypted evidence bundles stored in the gateway.
  - `submit_demand` (writes): Signal that you want a capability that doesn't exist on the network yet. Creates a demand signal and may auto-create a bounty if enough demand accumulates.
  - `list_bounties` (read-only): List open bounties for capabilities the network needs. Operators can claim these to earn rewards by onboarding new capabilities.
  - `claim_bounty` (writes): Claim a bounty to onboard a new capability. The operator commits to registering the capability and completing verification.
  - `verify_bounty` (writes): Verify bounty completion by scoring the delivered capability against requirements.
  - `get_top_demand` (read-only): Get top demand signals aggregated by capability type. Shows which capabilities are most wanted on the network.
  - `get_bounty_leaderboard` (read-only): Get the bounty hunter leaderboard showing top operators by bounties claimed and verified.
  - `create_investment_pool` (writes): Create an investment pool for a capability bounty. Stakers earn future protocol fees when the capability goes live.
  - `stake_in_pool` (writes): Stake USDC or credits into a capability investment pool.
  - `get_pool_earnings` (read-only): Check earnings from capability investment pools for a staker address.
  - `get_pool` (read-only): Get details of a specific investment pool including stakes, status, and revenue share terms.
  - `list_pools` (read-only): List all investment pools. Optionally filter by status or capability type.
  - `close_pool` (writes): Close an investment pool to new stakes. Pool enters sunset phase.
  - `claim_pool` (writes): Operator claims an investment pool reward after capability verification.
  - `convert_bounty_to_pool` (writes): Convert an existing bounty into an investment pool. Allows community staking toward the bounty's capability.
  - `get_subnet_status` (read-only): Get Bittensor verification subnet health, agent bridge status, and network connectivity.
  - `get_subnet_miners` (read-only): List verification subnet miners on the Bittensor network. Returns miner addresses, scores, and leaderboard positions.
  - `list_conversations` (read-only): List agent-to-agent conversations showing topic, participants, message count, and status.
  - `submit_feedback` (writes): Submit a bug report, suggestion, or general feedback about the PCC network.
  - `report_anomaly` (writes): Report a detected anomaly — protocol failure, evidence mismatch, stuck job, or suspicious behavior. All agents on the network are notified.
  - `get_unresolved_anomalies` (read-only): List all unresolved anomalies on the network. Filter by severity, category, or target agent.
  - `get_agent_anomalies` (read-only): Get anomalies involving a specific agent, plus their trust impact score.
  - `resolve_anomaly` (writes): Mark an anomaly as resolved with a resolution note.
  - `get_anomaly_stats` (read-only): Get aggregate anomaly statistics — total, unresolved, by severity, by category.
  - `report_protocol_failure` (writes): Report a protocol failure — when a step in the evidence/escrow/verification pipeline breaks. System may auto-recover.
  - `pcc_dht_query` (writes): Query the DHT for capabilities matching your requirements. Returns announcements from operators whose equipment matches the type, materials, and price range…
  - `pcc_dht_announce` (writes): Announce capabilities to the DHT network. Signs the announcement with your node's Ed25519 key and broadcasts to connected peers.
  - `pcc_dht_peers` (read-only): List known DHT peers and their connection status. Shows which nodes are currently connected to the gossip network.
  - `pcc_create_scope` (writes): Create an execution scope for a job. Scopes define exactly which tool calls are allowed on a kernel during a job, with command budgets, retry limits, and…
  - `pcc_revoke_scope` (writes): Revoke an execution scope immediately (emergency stop). All pending tool calls under this scope are rejected. The kernel enters a stopped state. A new scope…
  - `pcc_scope_audit` (read-only): Get the audit trail for an execution scope — every tool call made under this scope, with validation results, timestamps, and outcomes.
  - `pcc_relay_tool_call` (writes): Relay a tool call to a device executor. The brain (LLM) posts tool calls here; the executor (on the device) polls for them and executes locally. Used for the…
  - `pcc_get_tool_result` (read-only): Get the result of a previously relayed tool call. Poll this endpoint until the executor has processed the call and posted results.
  - `pcc_camera_latest` (read-only): Get the latest camera frame from a kernel as a JSON snapshot (base64 JPEG + metadata). For raw JPEG image, use GET /api/ot2/camera/latest directly.
  - `pcc_chat_send` (writes): Send a chat message to a kernel's operator or agent. Used for human-in-the-loop communication during job execution, troubleshooting, and escalation.
  - `pcc_chat_history` (read-only): Get chat history with a kernel. Returns messages between agents, operators, and users for a specific kernel.
  - `approve_registration` (writes): Approve a submitted machine registration. Moves it from 'submitted' to 'approved' status, enabling the operator to activate and start accepting jobs.
  - `reject_registration` (writes): Reject a machine registration with a reason. The operator can see the rejection reason and resubmit.
  - `activate_registration` (writes): Activate an approved registration, making the operator's equipment live on the network and ready to accept jobs.
  - `prove_registration` (writes): Fast-track: submit evidence that your device works and get auto-approved + activated immediately. No manual review needed. Submit a photo of test output,…
  - `list_registrations` (read-only): List all machine registrations on the network. See pending, approved, active, and rejected registrations. Public endpoint — no auth required.
  - `get_registration` (read-only): Get details of a specific machine registration by ID, including capabilities, pricing, operator info, and current status.
  - `near_status` (read-only): Get NEAR Protocol chain-abstraction integration status. Returns supported chains (near, eth, base, arbitrum, optimism, polygon), supported assets (USDC, USDT,…
  - `near_quote` (writes): Get a cross-chain payment quote from the NEAR 1Click solver network (chaindefuser.com). Provides optimal routing and fee estimates for funding PCC escrow…
  - `near_intent` (writes): Submit a cross-chain payment intent to the NEAR 1Click solver network. Creates a signed intent that routes the payment atomically across chains. Call…
  - `near_intent_status` (read-only): Check the settlement status of a submitted NEAR 1Click cross-chain payment intent. Statuses progress: pending → submitted → settled | failed. Returns txHash…
  - `protocol_state` (read-only): Read the PCCProtocol root contract state: current fee rate, total protocol fees collected, total escrow count, and registry addresses. Requires…
  - `protocol_fee` (read-only): Calculate the protocol fee for a given USDC amount (6-decimal units). Returns the fee, the net amount after fee, and formatted versions of both. Use this…
  - `protocol_token_fees` (read-only): Get total protocol fees collected for a specific ERC-20 token address across all escrows. Returns raw wei amount and human-readable formatted value.
  - `protocol_escrow_fees` (read-only): Get protocol fees collected from a specific escrow contract. Also returns whether the escrow was deployed via the protocol factory. Useful for auditing fee…
  - `protocol_create_escrow` (writes): Create a new MilestoneEscrow contract via the PCCProtocol factory on-chain. Protocol-deployed escrows have fee collection and registry tracking built in.…
  - `pcc_dht_metrics` (read-only): Get a snapshot of DHT telemetry counters and recent events. Returns message counts, peer connection stats, query/announce rates, and a list of the last 50…
  - `marketplace_categories` (read-only): List all supplies and materials marketplace categories with the count of active listings in each. Categories cover the full spectrum of physical production…
  - `marketplace_list_listings` (read-only): Search and filter supplies/materials marketplace listings. Operators buy raw materials here to fulfill capability contracts. Filter by category, in-stock…
  - `marketplace_get_listing` (read-only): Get full details of a specific supplies/materials marketplace listing by ID. Returns pricing, availability, lead time, location, and tags.
  - `marketplace_create_listing` (writes): Create a new supplies/materials listing in the marketplace. Suppliers post available raw materials, lab reagents, tooling, or consumables for other operators…
  - `marketplace_update_listing` (writes): Update an existing supplies/materials listing (price, stock status, description, etc.). Pass only the fields you want to change.
  - `marketplace_delete_listing` (writes): Remove a supplies/materials listing from the marketplace. The listing is immediately hidden from search results.
  - `marketplace_place_order` (writes): Place a purchase order for supplies or materials. Calculates total price automatically (quantity × pricePerUnit). Returns an order with 'pending' status.…
  - `marketplace_list_orders` (read-only): List marketplace supply orders. Filter by buyerId, sellerId, or status. Returns order history with pricing and status.
  - `marketplace_get_order` (read-only): Get details of a specific supply order including the associated listing details, quantity, total price, status, and optional escrow address.
  - `system_telemetry` (read-only): Raw system state dump — actual DB rows for kernels, devices, jobs, evidence, registrations, capabilities, agent conversations, audit log. No fake numbers, no…
  - `operator_poll_jobs` (read-only): Operator polls for pending jobs assigned to their kernel. Returns queued jobs ready for execution. The pcc-node 0.1.1 daemon does not call it: it takes no jobs.
  - `operator_push_evidence` (writes): Operator pushes evidence bundle from a completed job execution. Contains device ID, execution timestamp, result payload, and event timeline. Success is a…
  - `operator_heartbeat` (writes): Operator sends heartbeat with capability re-announcement. Keeps the kernel alive on the network and updates available capabilities.
  - `operator_update_job_status` (writes): Operator reports a job's status (in_progress, completed, failed). The node path finishes a job in two calls: submit its evidence (POST /api/operator/evidence;…
  - `pcc_submit_paid_job` (writes): Fast-track paid job: one call from DHT discovery to funded escrow + active scope. Auto-negotiates, quotes, creates escrow with milestones, creates execution…
  - `pcc_job_complete` (writes): Complete a job: gathers tool call audit trail from execution scopes, builds evidence bundle with SHA-256 hash, stores evidence, revokes scopes, and settles…
  - `pcc_job_settlement` (read-only): Get a job's settlement status from its own escrow records: status (settled only when a settlement read confirms the release; reported_released when the…
  - `pcc_get_tool_manifest` (read-only): Get the tool manifest for a kernel's device type. Lists all available tools with their safety classification (read, safe_control, scoped_write, privileged) and…
  - `pcc_relay_generic_tool_call` (writes): Relay a tool call to any kernel's device executor via the generic relay (not OT-2 specific). Works with any device type. Safe tools (read/safe_control) don't…
  - `pcc_submit_request` (writes): Submit a high-level capability request in natural language. The system automatically decomposes it into a capability DAG with dependencies, timelines, and…
  - `pcc_list_requests` (read-only): List all capability requests with optional filtering. Shows status, decomposed DAG summary, estimated costs, and timelines.
  - `pcc_get_request` (read-only): Get a capability request by ID with the full decomposed DAG — all capability nodes, their dependencies, estimated costs/hours, assigned operators, and linked…
  - `pcc_decompose_request` (writes): Re-trigger decomposition of an existing capability request. Overwrites the existing capability DAG with a fresh decomposition. Useful after updating the…
  - `pcc_publish_request` (writes): Publish all pending capability nodes in a request as bounties. Each node becomes a bidding opportunity for operators. Returns the list of created bounty IDs…
  - `pcc_get_request_dag` (read-only): Get the capability DAG (directed acyclic graph) for a request as adjacency data — nodes with all fields plus explicit edges showing dependency relationships.…
  - `pcc_get_request_critical_path` (read-only): Get the critical path (longest dependency chain) for a capability request. The critical path determines the minimum calendar time to complete the request.…
  - `pcc_assign_node_operator` (writes): Assign an operator to a specific capability node within a request. The node status changes to 'assigned'. Operators claim nodes to indicate they will execute…
  - `pcc_update_node_status` (writes): Update the status of a capability node within a request. Valid transitions: pending → bidding → assigned → in_progress → completed (or failed). When all nodes…
  - `pcc_update_request` (writes): Update a capability request's title, description, budget, deadline, urgency, or contact info. Does not re-decompose — call pcc_decompose_request afterwards if…
  - `pcc_cancel_request` (writes): Cancel a capability request. Cancelled requests cannot be updated, decomposed, or published. This is a soft delete — the request remains visible with status…
  - `pcc_oracle_status` (read-only): Not served by the PCC gateway: GET /api/oracle/health returns 404 there. PCC's verification oracle runs as a separate service, and this route answers only…
  - `pcc_oracle_verify` (writes): Not served by the PCC gateway: POST /api/oracle/verify returns 404 there. PCC's verification oracle runs as a separate service, and this route answers only…
  - `pcc_protocol_fee` (read-only): Get the current protocol fee rate (2.35%, immutable) and fee recipient address. The fee is hardcoded in the PCCProtocol smart contract — no admin, no…
  - `create_capability` (writes): Register a capability instance for a kernel. Required before submitting jobs — the gateway needs at least one capability per kernel. Creates a liquid-handler,…
  - `kernel_heartbeat` (writes): Send a per-kernel heartbeat to keep the kernel marked online. Used by pcc-node daemons as an alternative to the operator relay heartbeat.
  - `kernel_announce_capabilities` (writes): Announce capabilities for a kernel. NOTE: the gateway currently acknowledges this call but stores nothing, so it does not put any capability on the network. To…
  - `send_diagnostics` (writes): Upload an encrypted diagnostic bundle when the operator's node has problems. The bundle is encrypted client-side with a retrieval code the operator must share…
  - `send_support_message` (writes): Send an operator support message to the PCC team. Creates a new support thread or appends to the operator's existing open thread. Can optionally attach a…
  - `check_support_replies` (read-only): Check for admin replies on the operator's support threads. Call this periodically or when the operator asks 'did they respond yet?'. Returns all threads for…
  - `reply_to_support_thread` (writes): Reply to an existing support thread. Use when the operator wants to add information to a thread started earlier. Needs the threadId from check_support_replies…
  - `pcc_capture_challenge` (writes): Issue a fresh block-anchored CaptureNonceChallenge for a job. The operator's device must render this nonce into the captured media (QR code, audio tone, etc.)…
  - `pcc_capture_upload` (writes): Upload a capture (photo / video / audio / sensor clip) with its CaptureManifest for G1..G6 verification. Bytes are base64-encoded inline; optional base64 C2PA…
  - `pcc_capture_anchor` (writes): Anchor a PASS + anchor-candidate capture verdict to CaptureClassRegistry on-chain (Base Sepolia by default). Rejects FAIL/PARTIAL verdicts. Idempotent —…
  - `pcc_capture_status` (read-only): Fetch the combined verdict + on-chain anchor view for a single capture. Mirrors the verifier's DB shape plus the anchor tx metadata (txHash, blockNumber,…
  - `pcc_list_verdicts` (read-only): List recent capture verdicts, newest first. Optionally filter by jobId. Default limit is 50, capped at 200 server-side. Returns {verdicts, count, limit, jobId}.
  - `pcc_capture_class_registry` (read-only): Look up a capture's on-chain anchor record in CaptureClassRegistry by its 32-byte captureHash. Returns the registry address, captureHash, and decoded anchor…
  - `pcc_verifier_health` (read-only): Report CaptureVerifier health: which adapters are loaded (c2pa, webauthn, appattest, playintegrity), their staleness status, in-memory challenge cache size,…
  - `pcc_orchestrator_list_templates` (read-only): List the orchestrator templates the dashboard's chat console can drive. Each entry includes slug, display_name, description, produces_kind, capability_class…
  - `pcc_orchestrator_match_capabilities` (writes): Heuristic template matcher. Pass a free-text description of what you want to onboard (e.g. 'I run a CNC milling shop' or 'I have a Postgres database with a…
  - `pcc_onboard_session_start` (writes): Start a new physical-operator onboarding session. Returns a session_id used by every subsequent /api/onboard/* call. Auth-required.
  - `pcc_onboard_session_scrape` (writes): Scrape a URL into the running physical-operator onboarding session. Triggers a stealth fetch + structured extraction (machines, hours, services,…
  - `pcc_onboard_session_ingest_docs` (writes): Queue documents (datasheets, SOPs, MOPs, certifications) for ingestion into a physical-operator onboarding session. Document URLs may be local:// for files…
  - `pcc_onboard_session_build_agent` (writes): Finalise a physical-operator onboarding session: registers the operator on PCC, mints a wallet, writes the SEO mirror, returns the publication payload…
  - `pcc_onboard_session_status` (read-only): Coarse status snapshot for a physical-operator onboarding session: current state, 0-100 progress, scraped_count, ingested_count, last_event, publication…
  - `pcc_onboard_session_live_data` (read-only): Full event log for a physical-operator onboarding session — feeds the chat console's activity sidebar. Supports incremental polling via ?since=<unix-millis>.…
  - `pcc_contributor_register` (writes): Register a contributor profile binding a wallet address to a role and a published RateSchedule. Body: address (0x40hex), role (10 ContributorRole values from…
  - `pcc_contributor_list` (read-only): List all contributor profiles for an address across roles. Returns an array of {id, address, role, scheduleHash, ipId, contributorNftTokenId, metadataUri,…
  - `pcc_schedule_publish` (writes): Publish a sealed off-chain RateSchedule. Computes scheduleHash server-side via the canonical sha256-over-canonical-JSON algorithm (matching the on-chain…
  - `pcc_schedule_get` (read-only): Fetch a published RateSchedule by its content hash. Returns {schedule, publishedBy} with segments re-validated via Zod, or 404 if not found.
  - `pcc_schedule_evaluate` (writes): Evaluate a published RateSchedule at a moment, returning the effective bps. Inputs: scheduleHash + now (unix seconds) + optional jobValueCents…
  - `pcc_training_manifest_set` (writes): Set (insert-or-replace) the TrainingManifest for a model IP — the dataset weight map the LicensingEngine walks when distributing payouts to a 'model-author'…
  - `pcc_training_manifest_get` (read-only): Fetch the TrainingManifest for a model IP. Returns the parsed datasets array + manifestHash + createdAt, or 404 if no manifest has been set.
  - `pcc_trilobio_build_config` (writes): Generate a complete KERNEL_CONFIG JSON for a Trilobio (tcode-api) fleet controller. Wraps `buildTrilobioConfig()` from the @pcc/trilobio npm package. Returns a…
  - `pcc_trilobio_validate_options` (writes): Sanity-check operator-supplied Trilobio options before generating a KERNEL_CONFIG. Wraps `validateTrilobioOptions()` from @pcc/trilobio. Catches the common…
  - `pcc_trilobio_validate_script` (writes): Quick lint of a tcode-api Python script before submission to a Trilobio fleet controller. Wraps `validateTcodeScript()` from @pcc/trilobio. Surface check only…
  - `pcc_trilobio_capability_template` (read-only): Return the `TRILOBIO_CAPABILITY` constant from @pcc/trilobio — a default capability template for a Trilobio fleet controller. Pass to POST /api/capabilities to…
  - `attach_operator_channel` (writes): Attach a notification/dispatch channel to an operator so PCC knows how to ping them when a job lands. The operator's onboarding agent calls this AFTER the…
  - `list_operator_channels` (read-only): List every channel attached to an operator. Returns the full channel records (id, transport, direction, endpoint, describe, enabled flags). Useful for an…
  - `update_operator_channel` (writes): Update an existing channel — toggle enabled, rewrite the describe contract, change the endpoint payload, etc. Merges into the existing record. The operator…
  - `delete_operator_channel` (writes): Remove a channel from an operator. Future jobs will not dispatch to it. Use update_operator_channel with enabled=false to silence temporarily without losing…
  - `test_operator_channels` (writes): Fire a synthetic job at every enabled channel for an operator so the onboarding agent (and the human watching) can confirm the integration end-to-end before a…
  - `suggest_csd_templates` (read-only): Bidirectional onboarding: the registry talks back. Describe in plain English what you are trying to set up — 'wood-fired pizza shop in SF', 'Opentrons OT-2…
  - `get_popular_csd_templates` (read-only): Return CSDs sorted by adoption (usage-count descending). Useful for first-time operators who want to see what kind of capabilities others are publishing. Each…
  - `get_operator_status` (read-only): Four-slot substrate view for an operator: kernels, capabilities (with sla + availability), notification channels, and the per-kernel A2A agent-card URLs.…
  - `propose_composition` (writes): Propose a composition — a sequenced DAG of capability instances to satisfy a multi-step outcome under a budget + assurance tier. Accepts either a flat `steps`…
  - `get_composition` (read-only): Retrieve a previously-proposed composition by id. Returns 404 if unknown, 410 if the 30-minute proposal window has expired. Use this to inspect a plan before…
  - `execute_composition` (writes): Commit a proposed composition: drives the DAG through the workflow engine, each step records a reputation outcome, the composition's reputation is finalized…
  - `pcc_report` (writes): Report a bug, friction, or dead-end you hit while using PCC. Call this the moment you get stuck and cannot recover: a 5xx (its response carries a `report_hint`…
  - `pcc_report_attempt` (writes): Report one phase of an onboarding attempt, success or failure (attempt reporting contract v1). Send one report when each runbook phase ends, and a final report…
  - `save_dashboard` (writes): Save a generated dashboard to the network so the user gets a live, shareable URL: https://capability.network/a/<slug>. Pass a `manifest` — a small declarative…
  - `get_dashboard` (read-only): Recall a saved dashboard by its id or slug. Returns the full artifact (manifest + metadata). Use this to reload a dashboard the user asks for again ('open my…
  - `search_dashboards` (read-only): Discover existing public dashboards before you generate a new one (recall-first — the library accrues; adopt > extend > build for UIs too). Filter by…
  - `fork_dashboard` (writes): Fork an existing dashboard into a new artifact you own, preserving lineage back to the original (the social remix verb). Use this to adapt a popular dashboard…
  - `update_dashboard` (writes): Modify a dashboard you own (owner-only). Replace the manifest or any metadata field; the version increments. Use this to edit a saved surface meaningfully —…
  - `render_pcc_dashboard` (read-only): Compose a live PCC dashboard for a physical-capability task — pass a DashboardManifest (windows + live data bindings + actions) and it renders as an…
  - `render_pcc_dashboard_ir` (read-only): Compose a live PCC dashboard rendered through the closed, PCC-owned IR (read-only). Pass a DashboardManifest; it renders as an interactive MCP App via the…
  - `pcc.op.capability.request_quote` (read-only): Price a configured PCC capability (typed operation). Returns the itemized quote for the given capability type + selections. Pure calculation — no funds move…
- How its tools read to an agent (0 errors, 56 warnings, 1 note, about 43,488 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - warn TC02 pcc.op.capability.request_quote: the name has a dot
  - warn TC11 operator_heartbeat: none of its 2 parameters has a description
  - warn TC11 operator_push_evidence: none of its 3 parameters has a description
  - warn TC11 operator_update_job_status: none of its 4 parameters has a description
  - warn TC11 pcc.op.capability.request_quote: 2 parameters without a description: capabilityId, profileId
  - warn TC11 pcc_dht_announce: none of its 3 parameters has a description
  - warn TC11 pcc_report_attempt: none of its 20 parameters has a description
  - warn TC11 pcc_trilobio_validate_options: 7 parameters without a description: allowArbitraryScripts, deviceId, kernelId, maxScriptTimeoutSec, mockMode, mockRunDurationMs and 1 more
  - warn TC11 pcc_update_request: 7 parameters without a description: budget, deadline, description, requesterEmail, requesterWallet, title and 1 more
  - warn TC11 render_pcc_dashboard: 4 parameters without a description: description, sections, theme, title
  - warn TC11 render_pcc_dashboard_ir: 4 parameters without a description: description, sections, theme, title
  - warn TC11 update_operator_channel: 7 parameters without a description: credentialRef, describe, direction, enabled, endpoint, label and 1 more
  - warn TC13 archive_evidence: bundle (object with no properties)
  - warn TC13 attach_operator_channel: endpoint (object with no properties)
  - warn TC13 build_contract: selections (object with no properties)
  - warn TC13 calculate_price: selections (object with no properties)
  - warn TC13 create_kernel: config (object with no properties), location (object with no properties)
  - warn TC13 create_protocol: parameters (array with no items), steps (array with no items), transfers (array with no items)
  - warn TC13 create_protocol_run: parameterValues (object with no properties)
  - warn TC13 create_shipment: destination (object with no properties), origin (object with no properties), package (object with no properties)
  - warn TC13 emit_telemetry: metadata (object with no properties)
  - warn TC13 fork_protocol: parameterOverrides (object with no properties)
  - warn TC13 get_build_options: selections (object with no properties)
  - warn TC13 kernel_announce_capabilities: capabilities[] (object with no properties)

- JSON: https://www.anchorterminal.com/api/v1/tools/physical-capability-cloud.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming