network.capability/physical-capability-cloud

up checked 2026-11-11T01:37:44.629Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Physical Capability Cloud

Publisher-provided description

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

Summary by lookupd

Lets agents price, contract, and track physical manufacturing jobs across registered sites, with on-chain escrow and milestone reads.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add physical-capability-cloud --url https://capability.network/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

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

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (showing 30 of 182)

Publisher-provided text

• 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 for one device on a kernel (Step 4 of onboarding). The gateway runs it only for a kernel it operates in-process; for any other kernel it refus
• setup_status Comprehensive setup status across 6 categories: gateway, database, adapters, chain, storage, identity. Use to confirm everything is green before going live.
• list_capability_types List all capability types registered on the network (FDM, SLA, CNC, HPLC, etc.) with metadata.
• search_capabilities List the built-in capability type templates: each type's name, version, description, parameter count, parameter group names and a base price hint. NOTE: these d
• get_build_options Get configuration options for a capability type: parameter groups, each parameter's definition, and a base price hint. It includes no assurance tiers. Use befor
• calculate_price Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
• build_contract Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
• list_kernels List all Shop Kernels on the network with status and capability types. Optionally filter by status.
• get_kernel Get kernel details including full capability objects, devices, and queue.
• get_kernel_devices List all devices registered under a specific kernel, including adapter configs and device types.
• get_kernel_jobs List all jobs submitted to a specific kernel, including job status and progress.
• create_kernel Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
• list_jobs List all jobs with status. Optionally filter by kernelId or status.
• get_job Get job details including progress, evidence bundles, and milestones.
• update_job_status Update a job's status and optional progress percentage. Used by kernels to report job progress.
• list_escrows List escrow contracts with their milestone counts. Optionally filter by escrow status.
• get_escrow Get escrow details. Pass a DB ID for database record (with milestones and disputes), or an EVM address (0x...) to read directly from the blockchain.
• get_escrow_chain_state Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
• get_escrow_events Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
• get_token_balance Read an ERC-20 token balance for an account address from the blockchain.
• get_token_allowance Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
• get_escrow_dispute Read dispute state for a specific milestone from the blockchain.
• get_write_status Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.

Details

• Version: 2.19.0
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 530 ms
• First indexed: 2026-11-01T10:07:48.083Z
• Last seen in registry: 2026-11-01T10:07:48.083Z
• Repository: https://github.com/LamaSu/physical-capability-cloud
• Website: https://capability.network

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/network.capability/physical-capability-cloud.svg)](https://lookupd.com/servers/network.capability/physical-capability-cloud)

• 62071 servers
• Last crawl: 2026-11-11T16:39:06.253Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp