Name: Physical Capability Cloud
Author: network.capability

Tools observed via MCP handshake

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 reque
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
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 befor
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 adapterTyp
setup_test_job — Submit a test job to verify the full pipeline works end-to-end (Step 4 of onboarding). Returns job ID and result.
setup_status — Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
list_capability_types — List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
search_capabilities — Search capability templates by type or keyword. Returns templates with pricing, assurance tiers, and availability.
get_build_options — Get configuration options for a capability type (materials, dimensions, tolerances, assurance tiers). Use before calling calculate_price.
calculate_price — Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
build_contract — Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
list_kernels — List all Shop Kernels on the network with status and capability types. Optionally filter by status.
get_kernel — Get kernel details including full capability objects, devices, and queue.
get_kernel_devices — List all devices registered under a specific kernel, including adapter configs and device types.
get_kernel_jobs — List all jobs submitted to a specific kernel, including job status and progress.
create_kernel — Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
list_jobs — List all jobs with status. Optionally filter by kernelId or status.
get_job — Get job details including progress, evidence bundles, and milestones.
update_job_status — Update a job's status and optional progress percentage. Used by kernels to report job progress.
list_escrows — List escrow contracts with milestones and bonds. Optionally filter by status.
get_escrow — Get escrow details. Pass a DB ID for database record (with milestones and disputes), or an EVM address (0x...) to read directly from the blockchain.
get_escrow_chain_state — Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
get_escrow_events — Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
get_token_balance — Read an ERC-20 token balance for an account address from the blockchain.
get_token_allowance — Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
get_escrow_dispute — Read dispute state for a specific milestone from the blockchain.
get_write_status — Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
fund_escrow — Fund a protocol-created escrow on-chain. Approval is handled INTERNALLY by the gateway for protocol-created escrows (audit C-03 removed the public approve step)
release_milestone — Release a milestone payment on-chain after the challenge window has expired. Returns transaction hash.
file_escrow_dispute — File a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
deposit_bond — Deposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
submit_evidence_hash — Submit an evidence bundle hash for a milestone on-chain. Links the physical evidence to the on-chain settlement record. Returns transaction hash.
submit_attestation — Submit a verifier attestation for a milestone on-chain. Used by third-party verifiers (Bittensor subnet) to confirm evidence quality. Returns transaction hash.
archive_evidence — Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
get_evidence_bundle — Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
grant_evidence_access — Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
list_evidence_grants — List all evidence access grants for an address. Returns bundles the address has been granted access to.
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 — 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 — 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 — Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100.
pay_ip_royalty — Pay royalties to an IP asset vault. The payer sends tokens that flow to stakeholders via the royalty splits.
claim_ip_revenue — Claim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
get_ip_revenue — Get a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
get_ip_lineage — Get the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
get_capability_ip — Get the Story Protocol IP registration for a capability by its capability ID.
raise_ip_dispute — Raise a Story Protocol IP dispute against an asset. Provide evidence hash and reason.
list_protocols — List protocol templates in the library. Filter by tags, required capabilities, search query, or status.
get_protocol — Get protocol template details by ID. Returns steps, transfers, parameters, and metadata.
create_protocol — Create a new protocol template draft. Returns the new template ID.
update_protocol — Update an existing protocol template (must be in draft status). Returns updated name and version.
publish_protocol — Publish a draft protocol template, making it visible in the protocol library for others to discover and use.
fork_protocol — Fork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
get_protocol_forks — List all forks of a protocol template. Shows who forked it and what parameters they changed.
validate_protocol — Validate a protocol template against a specific kernel — checks capability availability, transfer compatibility, and automation level feasibility.
list_protocol_runs — List protocol runs. Filter by status or kernelId.
get_protocol_run — Get protocol run status including step progress, transfer status, current phase, and evidence hashes.
create_protocol_run — Instantiate a protocol template as a run on a specific kernel with given parameter values.
start_protocol_run — Start execution of a protocol run that is in 'ready' or 'binding' state.
pause_protocol_run — Pause a running protocol run. Use resume_protocol_run to continue.
resume_protocol_run — Resume a paused protocol run from where it stopped.
cancel_protocol_run — Cancel a protocol run. Cannot be cancelled once completed or already cancelled.
get_workflows — List active instrument workflows in the orchestrator. Optionally filter by status.
get_workflow — Get detailed workflow information including steps, node assignments, and progress.
get_transfer_graphs — Get resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
list_automation_status — List automation status for all instrument transfer pairs. Shows current automation level, episode count, and training readiness. Filter by kernelId.
get_automation_status — Get automation status for a specific instrument-to-instrument transfer pair.
record_episode — Record a transfer episode for a node pair. Increments episode count toward VLA training threshold.
advance_automation — Advance the automation level for a transfer pair (manual → teleoperated → pilot_operated → vla_assisted → fully_autonomous). Requires sufficient training episod
list_transfer_agents — List all transfer agents (robots and human operators) available for instrument-to-instrument transfers.
get_logistics_overview — Logistics hub overview: active shipments, pending installations, and upcoming bookings.
get_shipments — List equipment shipments with tracking status. Optionally filter by status.
create_shipment — Create a new equipment shipment with origin, destination, package details, and provider.
get_shipment_quote — Get shipping quotes from logistics providers based on origin, destination, weight, and priority.
get_installations — List equipment installation orders with step progress and status.
get_space_bookings — List space bookings for hosting equipment. Optionally filter by status or space.
search_spaces — Search for lab/workshop hosting spaces. Filter by size, access schedule, and other requirements.
get_space — Get detailed information about a hosting space including power, amenities, safety features, and pricing.
match_spaces — Find hosting spaces that match specific machine requirements (voltage, area, etc.). Returns scored matches.
get_marketplace_overview — Equipment marketplace overview with demand/supply metrics across all capability types.
get_equipment_classes — List equipment classes (FDM printers, CNC mills, etc.) with market snapshot data including utilization, demand, and pricing.

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	314 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
10 h ago	mcp initialize	ok	200	180 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
17 h ago	mcp initialize	ok	200	180 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
23 h ago	mcp initialize	ok	200	233 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
29 h ago	mcp initialize	ok	200	207 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
35 h ago	mcp initialize	ok	200	206 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
2 d ago	mcp initialize	ok	200	289 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
2 d ago	mcp initialize	ok	200	190 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
2 d ago	mcp initialize	ok	200	190 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools
3 d ago	mcp initialize	ok	200	216 ms	server Physical Capability Cloud 2.19.3+sha256.737720f44f32d183f5cf0dce0d · protocol 2025-06-18 · 256 tools

Physical Capability Cloud

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from