MCP server

Physical Capability Cloud

network.capability/physical-capability-cloud

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

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

Website Source

At a glance

Type

MCP server

Publisher

capability.network (verified by the MCP Registry)

Status

Working at last check

Tools

256

Token cost

About 45,368 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.physical-capability-cloud]
url = "https://capability.network/mcp"

Gemini CLI

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

Cursor

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

VS Code

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

Antigravity

agy mcp add physical-capability-cloud https://capability.network/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"physical-capability-cloud","server_url":"https://capability.network/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"physical-capability-cloud","server_url":"https://capability.network/mcp"}

Tools

• activate_registration ~88 tokens
  Activate an approved registration, making the operator's equipment live on the network and ready to accept jobs.
• advance_automation ~127 tokens
  Advance the automation level for a transfer pair (manual → teleoperated → pilot_operated → vla_assisted → fully_autonomous). Requires sufficient training episodes.
• analyze_machine_docs ~92 tokens
  AI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.
• approve_registration ~105 tokens
  Approve a submitted machine registration. Moves it from 'submitted' to 'approved' status, enabling the operator to activate and start accepting jobs.
• archive_encrypted_bundle ~98 tokens
  Archive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.
• archive_evidence ~88 tokens
  Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
• build_contract ~159 tokens
  Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
• calculate_price ~137 tokens
  Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
• calculate_roi ~132 tokens
  Calculate ROI projection for onboarding equipment. Returns month-by-month revenue, cost, and break-even analysis.
• cancel_protocol_run ~76 tokens
  Cancel a protocol run. Cannot be cancelled once completed or already cancelled.
• check_invite ~78 tokens
  Validate an invite code before redeeming it. Returns whether the code is valid and what it includes.
• claim_bounty ~116 tokens
  Claim a bounty to onboard a new capability. The operator commits to registering the capability and completing verification.
• claim_ip_revenue ~114 tokens
  Claim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
• claim_pool ~94 tokens
  Operator claims an investment pool reward after capability verification.
• close_pool ~67 tokens
  Close an investment pool to new stakes. Pool enters sunset phase.
• commit_evidence ~93 tokens
  Create a Merkle commitment for an evidence bundle hash. Used as the first step in ZK proof generation for Tier 3 assurance.
• convert_bounty_to_pool ~88 tokens
  Convert an existing bounty into an investment pool. Allows community staking toward the bounty's capability.
• create_investment_pool ~178 tokens
  Create an investment pool for a capability bounty. Stakers earn future protocol fees when the capability goes live.
• create_kernel ~158 tokens
  Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
• create_protocol ~208 tokens
  Create a new protocol template draft. Returns the new template ID.
• create_protocol_run ~160 tokens
  Instantiate a protocol template as a run on a specific kernel with given parameter values.
• create_shipment ~195 tokens
  Create a new equipment shipment with origin, destination, package details, and provider.
• deposit_bond ~118 tokens
  Deposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
• dispute_verification ~176 tokens
  File a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.
• distribute_royalties ~219 tokens
  Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100.
• emit_telemetry ~241 tokens
  Manually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.
• file_escrow_dispute ~209 tokens
  File a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
• fork_protocol ~131 tokens
  Fork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
• fund_escrow ~122 tokens
  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.
• get_active_telemetry ~56 tokens
  List currently active jobs with their current pipeline phase and telemetry status.
• get_agent_anomalies ~73 tokens
  Get anomalies involving a specific agent, plus their trust impact score.
• get_anomaly_stats ~54 tokens
  Get aggregate anomaly statistics — total, unresolved, by severity, by category.
• get_automation_status ~103 tokens
  Get automation status for a specific instrument-to-instrument transfer pair.
• get_bounty_leaderboard ~82 tokens
  Get the bounty hunter leaderboard showing top operators by bounties claimed and verified.
• get_build_options ~145 tokens
  Get configuration options for a capability type (materials, dimensions, tolerances, assurance tiers). Use before calling calculate_price.
• get_bundle_ipfs ~81 tokens
  Get IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
• get_capability_ip ~84 tokens
  Get the Story Protocol IP registration for a capability by its capability ID.
• get_demand_supply ~57 tokens
  Get network-wide demand vs supply timeline data for capacity planning and market analysis.
• get_depin_stats ~54 tokens
  DePIN treasury, soulbound capability certificates, and current reward epoch stats.
• get_equipment_classes ~68 tokens
  List equipment classes (FDM printers, CNC mills, etc.) with market snapshot data including utilization, demand, and pricing.
• get_escrow ~101 tokens
  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 ~97 tokens
  Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
• get_escrow_dispute ~101 tokens
  Read dispute state for a specific milestone from the blockchain.
• get_escrow_events ~110 tokens
  Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
• get_evidence_bundle ~81 tokens
  Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
• get_installations ~83 tokens
  List equipment installation orders with step progress and status.
• get_ip_lineage ~76 tokens
  Get the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
• get_ip_revenue ~73 tokens
  Get a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
• get_job ~64 tokens
  Get job details including progress, evidence bundles, and milestones.
• get_job_telemetry ~84 tokens
  Get full event timeline for a specific job — all pipeline phase transitions with timings and metadata.
• get_kernel ~68 tokens
  Get kernel details including full capability objects, devices, and queue.
• get_kernel_devices ~77 tokens
  List all devices registered under a specific kernel, including adapter configs and device types.
• get_kernel_jobs ~72 tokens
  List all jobs submitted to a specific kernel, including job status and progress.
• get_kernel_sensors ~77 tokens
  Get sensor channels for a specific kernel. Returns live channel descriptors.
• get_lit_conditions ~92 tokens
  Get Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
• get_logistics_overview ~58 tokens
  Logistics hub overview: active shipments, pending installations, and upcoming bookings.
• get_marketplace_overview ~58 tokens
  Equipment marketplace overview with demand/supply metrics across all capability types.
• get_operator_certs ~90 tokens
  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_operator_dashboard ~75 tokens
  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_earnings ~103 tokens
  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_machines ~86 tokens
  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_pool ~75 tokens
  Get details of a specific investment pool including stakes, status, and revenue share terms.
• get_pool_earnings ~74 tokens
  Check earnings from capability investment pools for a staker address.
• get_protocol ~73 tokens
  Get protocol template details by ID. Returns steps, transfers, parameters, and metadata.
• get_protocol_forks ~76 tokens
  List all forks of a protocol template. Shows who forked it and what parameters they changed.
• get_protocol_run ~78 tokens
  Get protocol run status including step progress, transfer status, current phase, and evidence hashes.
• get_registration ~89 tokens
  Get details of a specific machine registration by ID, including capabilities, pricing, operator info, and current status.
• get_sensor_channels ~61 tokens
  List all registered sensor channels across kernels. Returns channel descriptors with units and ranges.
• get_settlement_epochs ~59 tokens
  Get settlement epoch history showing past batch settlements with timing and operation counts.
• get_settlement_status ~65 tokens
  Get settlement pipeline status including pending operations count, total value queued, and smart account address.
• get_shipment_quote ~147 tokens
  Get shipping quotes from logistics providers based on origin, destination, weight, and priority.
• get_shipments ~85 tokens
  List equipment shipments with tracking status. Optionally filter by status.
• get_space ~73 tokens
  Get detailed information about a hosting space including power, amenities, safety features, and pricing.
• get_space_bookings ~92 tokens
  List space bookings for hosting equipment. Optionally filter by status or space.
• get_subnet_miners ~65 tokens
  List verification subnet miners on the Bittensor network. Returns miner addresses, scores, and leaderboard positions.
• get_subnet_status ~56 tokens
  Get Bittensor verification subnet health, agent bridge status, and network connectivity.
• get_telemetry_logs ~231 tokens
  Query structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.
• get_telemetry_stats ~67 tokens
  Get aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.
• get_token_allowance ~129 tokens
  Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
• get_token_balance ~109 tokens
  Read an ERC-20 token balance for an account address from the blockchain.
• get_top_demand ~88 tokens
  Get top demand signals aggregated by capability type. Shows which capabilities are most wanted on the network.
• get_transfer_graphs ~62 tokens
  Get resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
• get_unresolved_anomalies ~125 tokens
  List all unresolved anomalies on the network. Filter by severity, category, or target agent.
• get_verification_assignments ~94 tokens
  Get pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.
• get_verification_status ~93 tokens
  Get verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.
• get_workflow ~73 tokens
  Get detailed workflow information including steps, node assignments, and progress.
• get_workflows ~80 tokens
  List active instrument workflows in the orchestrator. Optionally filter by status.
• get_write_status ~71 tokens
  Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
• grant_evidence_access Changes accounts · ~153 tokens
  Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
• list_api_keys ~85 tokens
  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.
• list_automation_status ~93 tokens
  List automation status for all instrument transfer pairs. Shows current automation level, episode count, and training readiness. Filter by kernelId.
• list_batches ~43 tokens
  List active and completed settlement batches.
• list_bounties ~123 tokens
  List open bounties for capabilities the network needs. Operators can claim these to earn rewards by onboarding new capabilities.
• list_capability_types ~59 tokens
  List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
• list_conversations ~57 tokens
  List agent-to-agent conversations showing topic, participants, message count, and status.
• list_escrows ~71 tokens
  List escrow contracts with milestones and bonds. Optionally filter by status.
• list_evidence ~46 tokens
  List encrypted evidence bundles stored in the gateway.
• list_evidence_grants ~88 tokens
  List all evidence access grants for an address. Returns bundles the address has been granted access to.
• list_jobs ~103 tokens
  List all jobs with status. Optionally filter by kernelId or status.
• list_kernels ~86 tokens
  List all Shop Kernels on the network with status and capability types. Optionally filter by status.
• list_pools ~106 tokens
  List all investment pools. Optionally filter by status or capability type.
• list_protocol_runs ~105 tokens
  List protocol runs. Filter by status or kernelId.
• list_protocols ~170 tokens
  List protocol templates in the library. Filter by tags, required capabilities, search query, or status.
• list_registrations ~72 tokens
  List all machine registrations on the network. See pending, approved, active, and rejected registrations. Public endpoint — no auth required.
• list_transfer_agents ~62 tokens
  List all transfer agents (robots and human operators) available for instrument-to-instrument transfers.
• lit_decrypt ~166 tokens
  Decrypt a Lit Protocol-encrypted evidence bundle using a Lit auth signature. Returns the decrypted bundle payload.
• marketplace_categories ~102 tokens
  List all supplies and materials marketplace categories with the count of active listings in each. Categories cover the full spectrum of physical production inputs: raw metals, plastics, lab reagents, consumables, electronics, tooling, and more.
• marketplace_create_listing ~382 tokens
  Create a new supplies/materials listing in the marketplace. Suppliers post available raw materials, lab reagents, tooling, or consumables for other operators to purchase.
• marketplace_delete_listing Deletes data · ~84 tokens
  Remove a supplies/materials listing from the marketplace. The listing is immediately hidden from search results.
• marketplace_get_listing ~94 tokens
  Get full details of a specific supplies/materials marketplace listing by ID. Returns pricing, availability, lead time, location, and tags.
• marketplace_get_order ~93 tokens
  Get details of a specific supply order including the associated listing details, quantity, total price, status, and optional escrow address.
• marketplace_list_listings ~235 tokens
  Search and filter supplies/materials marketplace listings. Operators buy raw materials here to fulfill capability contracts. Filter by category, in-stock status, location, or free-text query.
• marketplace_list_orders ~152 tokens
  List marketplace supply orders. Filter by buyerId, sellerId, or status. Returns order history with pricing and status.
• marketplace_place_order Moves money · ~206 tokens
  Place a purchase order for supplies or materials. Calculates total price automatically (quantity × pricePerUnit). Returns an order with 'pending' status. Optionally links to an on-chain escrow for trustless settlement.
• marketplace_update_listing ~194 tokens
  Update an existing supplies/materials listing (price, stock status, description, etc.). Pass only the fields you want to change.
• match_spaces ~104 tokens
  Find hosting spaces that match specific machine requirements (voltage, area, etc.). Returns scored matches.
• mint_certificate ~193 tokens
  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 onboarding.
• near_intent ~192 tokens
  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_quote first to obtain a quoteId. Intents typically settle within 30-60 seconds — poll near_intent_status to track progress.
• near_intent_status ~110 tokens
  Check the settlement status of a submitted NEAR 1Click cross-chain payment intent. Statuses progress: pending → submitted → settled | failed. Returns txHash and explorerUrl when settled.
• near_quote ~294 tokens
  Get a cross-chain payment quote from the NEAR 1Click solver network (chaindefuser.com). Provides optimal routing and fee estimates for funding PCC escrow contracts using any source asset on any supported chain. Call near_status first to confirm available chains/assets.
• near_status ~110 tokens
  Get NEAR Protocol chain-abstraction integration status. Returns supported chains (near, eth, base, arbitrum, optimism, polygon), supported assets (USDC, USDT, NEAR, ETH, WBTC), and capability flags. Use this to confirm cross-chain settlement is available before requesting quotes.
• onboard_machine ~332 tokens
  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 cannot match it to you.
• operator_heartbeat ~199 tokens
  Operator sends heartbeat with capability re-announcement. Keeps the kernel alive on the network and updates its own capability rows. Requires operate authority for this kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority.
• operator_poll_jobs ~206 tokens
  Operator polls jobs assigned to their kernel; status defaults to queued, and the route can filter any status. Requires operate authority for this kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority. Another identity gets
• operator_push_evidence ~284 tokens
  Operator pushes evidence bundle from a completed job execution. Requires decide authority for the stored job's kernel: its proven operator wallet or the gateway admin authority. A matching claimed operator key gets 403 operator_proof_required. Evidence takes decide, per DECISIONS 2026-10-04 01:25 (N
• operator_update_job_status ~415 tokens
  Operator reports a job's status (in_progress, completed, failed). Requires operate authority for the stored job's kernel: its recorded operator identity (the caller that registered it), its proven operator wallet, or the gateway admin authority. The body's kernelId cannot choose the authorization ta
• pause_protocol_run ~71 tokens
  Pause a running protocol run. Use resume_protocol_run to continue.
• pay_ip_royalty Moves money · ~128 tokens
  Pay royalties to an IP asset vault. The payer sends tokens that flow to stakeholders via the royalty splits.
• pcc_assign_node_operator ~150 tokens
  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 that capability.
• pcc_camera_latest ~99 tokens
  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_cancel_request ~102 tokens
  Cancel a capability request. Cancelled requests cannot be updated, decomposed, or published. This is a soft delete — the request remains visible with status 'cancelled'.
• pcc_chat_history ~110 tokens
  Get chat history with a kernel. Returns messages between agents, operators, and users for a specific kernel.
• pcc_chat_send Sends messages · ~150 tokens
  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_create_scope ~398 tokens
  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 time-to-live. Required before issuing SCOPED WRITE operations (protocol upload, run create, run action).
• pcc_decompose_request ~105 tokens
  Re-trigger decomposition of an existing capability request. Overwrites the existing capability DAG with a fresh decomposition. Useful after updating the description or budget.
• pcc_dht_announce ~244 tokens
  Announce capabilities to the DHT network. Signs the announcement with your node's Ed25519 key and broadcasts to connected peers.
• pcc_dht_metrics ~89 tokens
  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 metric events. Use for monitoring network health.
• pcc_dht_peers ~63 tokens
  List known DHT peers and their connection status. Shows which nodes are currently connected to the gossip network.
• pcc_dht_query ~209 tokens
  Query the DHT for capabilities matching your requirements. Returns announcements from operators whose equipment matches the type, materials, and price range you specify.
• pcc_get_request ~98 tokens
  Get a capability request by ID with the full decomposed DAG — all capability nodes, their dependencies, estimated costs/hours, assigned operators, and linked bounty IDs.
• pcc_get_request_critical_path ~123 tokens
  Get the critical path (longest dependency chain) for a capability request. The critical path determines the minimum calendar time to complete the request. Returns node IDs in order, the full node details, and total hours on the critical path.
• pcc_get_request_dag ~109 tokens
  Get the capability DAG (directed acyclic graph) for a request as adjacency data — nodes with all fields plus explicit edges showing dependency relationships. Useful for visualization or workflow planning.
• pcc_get_tool_manifest ~120 tokens
  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 input schemas. Use to understand what tools are available before making tool calls.
• pcc_get_tool_result ~97 tokens
  Get the result of a previously relayed tool call. Poll this endpoint until the executor has processed the call and posted results.
• pcc_job_complete ~191 tokens
  Complete a job: gathers tool call audit trail from execution scopes, builds evidence bundle with SHA-256 hash, stores evidence, revokes scopes, and settles escrow (mock or real). This is how a job run through execution scopes is finished. A node that submitted its evidence and set status completed (
• pcc_job_settlement ~190 tokens
  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 milestone record says released but nothing confirms it; simulated for a mock escrow; awaiting_settlement, no_settlement_record, unknown or unavailab
• pcc_list_requests ~157 tokens
  List all capability requests with optional filtering. Shows status, decomposed DAG summary, estimated costs, and timelines.
• pcc_oracle_status ~133 tokens
  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 where a deployment fronts it. Agents never call the oracle to settle a job: settlement is the gateway's step after pcc_job_complete. Where it is
• pcc_publish_request Sends messages · ~108 tokens
  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 linked to each capability node.
• pcc_relay_generic_tool_call ~206 tokens
  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 need a scope. Scoped write tools require an active execution scope. Returns a call ID — poll pcc_get_tool_result for the response.
• pcc_relay_tool_call ~194 tokens
  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 brain/executor split architecture.
• pcc_revoke_scope Changes accounts · ~104 tokens
  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 must be created to resume.
• pcc_scope_audit ~89 tokens
  Get the audit trail for an execution scope — every tool call made under this scope, with validation results, timestamps, and outcomes.
• pcc_submit_paid_job ~260 tokens
  Fast-track paid job: one call from DHT discovery to funded escrow + active scope. Auto-negotiates, quotes, creates escrow with milestones, creates execution scope. Returns jobId, scopeId, escrowId, quote with pricing adjustments, contract terms. For testnet, escrow is mock-funded automatically.
• pcc_submit_request ~367 tokens
  Submit a high-level capability request in natural language. The system automatically decomposes it into a capability DAG with dependencies, timelines, and budget allocation across fabrication, design, assembly, electronics, software, logistics, and verification nodes. Returns the request with full d
• pcc_update_node_status ~176 tokens
  Update the status of a capability node within a request. Valid transitions: pending → bidding → assigned → in_progress → completed (or failed). When all nodes complete, the request automatically moves to completed.
• pcc_update_request ~174 tokens
  Update a capability request's title, description, budget, deadline, urgency, or contact info. Does not re-decompose — call pcc_decompose_request afterwards if you want a fresh DAG.
• protocol_create_escrow ~199 tokens
  Create a new MilestoneEscrow contract via the PCCProtocol factory on-chain. Protocol-deployed escrows have fee collection and registry tracking built in. Requires PCC_GATEWAY_PRIVATE_KEY write access.
• protocol_escrow_fees ~106 tokens
  Get protocol fees collected from a specific escrow contract. Also returns whether the escrow was deployed via the protocol factory. Useful for auditing fee flows.
• protocol_fee ~129 tokens
  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 before building escrow contracts to understand the true cost.
• protocol_state ~87 tokens
  Read the PCCProtocol root contract state: current fee rate, total protocol fees collected, total escrow count, and registry addresses. Requires PCC_PROTOCOL_ADDRESS to be configured on the gateway.
• protocol_token_fees ~103 tokens
  Get total protocol fees collected for a specific ERC-20 token address across all escrows. Returns raw wei amount and human-readable formatted value.
• prove_registration ~461 tokens
  Fast-track: submit evidence that your device works and get auto-approved + activated immediately. No manual review needed. Submit a photo of test output, device health snapshot, or a full evidence bundle with completion events. If evidence meets requirements, registration jumps straight to 'active'.
• provision_api_key ~220 tokens
  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.
• publish_protocol Sends messages · ~83 tokens
  Publish a draft protocol template, making it visible in the protocol library for others to discover and use.
• raise_ip_dispute ~123 tokens
  Raise a Story Protocol IP dispute against an asset. Provide evidence hash and reason.
• record_episode ~148 tokens
  Record a transfer episode for a node pair. Increments episode count toward VLA training threshold.
• redeem_invite ~152 tokens
  One-click agent onboarding with an invite code. Provisions wallet, identity, LLM access, and PCC tools in a single call.
• register_capability_ip ~266 tokens
  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 ~238 tokens
  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.
• reject_registration ~102 tokens
  Reject a machine registration with a reason. The operator can see the rejection reason and resubmit.
• release_milestone ~114 tokens
  Release a milestone payment on-chain after the challenge window has expired. Returns transaction hash.
• report_anomaly ~231 tokens
  Report a detected anomaly — protocol failure, evidence mismatch, stuck job, or suspicious behavior. All agents on the network are notified.
• report_protocol_failure ~234 tokens
  Report a protocol failure — when a step in the evidence/escrow/verification pipeline breaks. System may auto-recover.
• resolve_anomaly ~93 tokens
  Mark an anomaly as resolved with a resolution note.
• respond_to_verification ~192 tokens
  Submit a verifier's verdict for a verification request. Returns consensus state after this vote.
• resume_protocol_run ~68 tokens
  Resume a paused protocol run from where it stopped.
• retrieve_ipfs ~81 tokens
  Retrieve raw data from IPFS by CID. Used to fetch archived evidence bundles from decentralized storage.
• revoke_api_key Changes accounts · ~92 tokens
  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.
• search_capabilities ~92 tokens
  Search capability templates by type or keyword. Returns templates with pricing, assurance tiers, and availability.
• search_spaces ~101 tokens
  Search for lab/workshop hosting spaces. Filter by size, access schedule, and other requirements.
• setup_detect ~79 tokens
  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 ~117 tokens
  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_register_device ~334 tokens
  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_status ~74 tokens
  Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
• setup_test_job ~107 tokens
  Submit a test job to verify the full pipeline works end-to-end (Step 4 of onboarding). Returns job ID and result.
• setup_validate ~93 tokens
  Validate a kernel config (20+ checks: JSON structure, device connectivity, adapter compatibility). Returns validation errors and warnings.
• stake_in_pool ~108 tokens
  Stake USDC or credits into a capability investment pool.
• start_protocol_run ~73 tokens
  Start execution of a protocol run that is in 'ready' or 'binding' state.
• submit_attestation ~160 tokens
  Submit a verifier attestation for a milestone on-chain. Used by third-party verifiers (Bittensor subnet) to confirm evidence quality. Returns transaction hash.
• submit_demand ~249 tokens
  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.
• submit_evidence_hash ~160 tokens
  Submit an evidence bundle hash for a milestone on-chain. Links the physical evidence to the on-chain settlement record. Returns transaction hash.
• submit_feedback ~130 tokens
  Submit a bug report, suggestion, or general feedback about the PCC network.
• submit_for_human_verification ~212 tokens
  Submit an evidence bundle for human verification. Selects a panel of verifiers from the network and returns assigned verifier IDs.
• system_telemetry ~75 tokens
  Raw system state dump — actual DB rows for kernels, devices, jobs, evidence, registrations, capabilities, agent conversations, audit log. No fake numbers, no summaries.
• update_job_status ~152 tokens
  Update a job's status and optional progress percentage. Used by kernels to report job progress.
• update_protocol ~170 tokens
  Update an existing protocol template (must be in draft status). Returns updated name and version.
• validate_protocol ~116 tokens
  Validate a protocol template against a specific kernel — checks capability availability, transfer compatibility, and automation level feasibility.
• verify_bounty ~120 tokens
  Verify bounty completion by scoring the delivered capability against requirements.
• verify_evidence_zk ~83 tokens
  Verify a ZK proof by its proof ID. Checks the proof against its verification key and public inputs.

Browse

• Databases
• Crypto and blockchains

Related MCP servers

• HumanEndpoint
  Human-only capabilities for AI agents: ground truth, verification, judgement and real-world action.
• Realask - verified answers from the physical world
  Ask a US local business a current question by phone. Typed, timestamped answers for agents; x402.
• Renthuman
  AI agents hire real humans in Russia: storefront photos, address checks, errands. Pay in USDT.
• Errand
  Dispatch nearby humans for on-site checks, photos, pickups and queues with verified evidence.
• Japan External Execution
  Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.
• NovaRail
  Discover, verify, and hire AI agents from the NovaRail marketplace, from your editor.
• Wingmanprotocol Gateway
  Durable self for AI agents: one-call resume, memory, a real browser, research, free chat.
• MEKU Human Cloud
  AI agents discover human capabilities, request real-world human execution, and track status.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/network.capability/physical-capability-cloud.svg)](https://aptlynx.net/servers/network.capability/physical-capability-cloud)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents