Physical Capability Cloud
REMOTE · CAPABILITY.NETWORK
Discover, hire, and verify real-world physical capability through MCP.
Available components
Last scanned (5 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
Recent critical change
Authorization (1 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revoke_api_key). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 22909 tokens (~88/item across 260 items; 256 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- Structured output schemas are declared (3% of tools); any adoption earns full credit.Pass
Tool Safety97
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 13 of 15 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_transfer_graphs" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 258 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −1
- Stability: pass → 0.97 functional
- 3 Nov 26 0
- Stability: fail → pass ▲ security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 96 to 99.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 89 to 93.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 86.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 76 to 79.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 69 to 73.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 59 to 63.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://capability.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=capability.network | CN=YE1,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 61e79ee07e783aedc9770a1b1a54789ebd0 |
| SANs: *.capability.network, capability.network | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of capability.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 11416, 40414 | 8, 8 | Verified |
| capability.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://capability.network/mcp | Verified | 200 | |
| http (plaintext) | http://capability.network/mcp | HTTPS enforced | 301 | https://capability.network/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
activate_registration ~38
Activate an approved registration, making the operator's equipment live on the network and ready to accept jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| registrationId | string | yes | Registration ID |
No output schema declared.
No examples provided.
advance_automation ~68
Advance the automation level for a transfer pair (manual → teleoperated → pilot_operated → vla_assisted → fully_autonomous). Requires sufficient training episodes.
| Name | Type | Req | Description |
|---|---|---|---|
| fromNodeId | string | yes | Source instrument node ID |
| toNodeId | string | yes | Destination instrument node ID |
No output schema declared.
No examples provided.
analyze_machine_docs ~44
AI analysis of machine documentation. Upload docs to get suggested capabilities, extracted specs, materials, and tolerances.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | – | Document content or reference to analyze |
No output schema declared.
No examples provided.
approve_registration ~58
Approve a submitted machine registration. Moves it from 'submitted' to 'approved' status, enabling the operator to activate and start accepting jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| registrationId | string | yes | Registration ID (e.g. 'reg-1234567890') |
No output schema declared.
No examples provided.
archive_encrypted_bundle ~51
Archive an encrypted evidence bundle to IPFS and store the resulting CID in the database. Idempotent — returns existing CID if already archived.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleId | string | yes | Encrypted evidence bundle ID |
No output schema declared.
No examples provided.
archive_evidence ~43
Archive an evidence bundle to IPFS/Storacha for permanent decentralized storage. Returns the content-addressed CID.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | Evidence bundle object to archive |
No output schema declared.
No examples provided.
attach_operator_channel ~400
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 conversation that produced the channel record. Transport is a small stable enum (webhook|email|sms|voice|push|mqtt|file|manual) — vendor specifics live in the free-form `describe` field, written by the operator's agent. PCC the substrate stays neutral. Returns the channel record with a generated id.
| Name | Type | Req | Description |
|---|---|---|---|
| credentialRef | string | – | Reference to a secret in the credential vault (not the secret itself). PCC resolves it at dispatch time. |
| describe | string | yes | Plain-English instructions for how PCC should talk to whatever is on the other end. Written by the operator's onboarding agent. Required, ≥4 chars. Example: 'POST JSON with keys order_id, line_items[… |
| direction | string | – | out=PCC pushes only; in-out=operator's system also replies; in=operator pushes unsolicited. |
| enabled | boolean | – | Whether the channel is live (defaults to true). |
| endpoint | object | – | Transport-specific routing payload. webhook→{url}, email→{address}, sms/voice→{phoneE164}, push→{token,platform}, mqtt→{brokerUrl,topic}, file→{scheme,path}, manual→{}. |
| label | string | yes | Short human label shown to the operator and in admin UIs: 'Front counter printer', 'Owner's phone'. |
| replyContract | string | – | Optional operator-authored contract describing how the operator's system will respond to evidence requests, status pings, etc. |
| slug | string | yes | Operator slug (typically the operator's address or unique identifier). |
| transport | string | yes | Which wire does the message go over. `manual` = no machine endpoint (dashboard-only). |
No output schema declared.
No examples provided.
build_contract ~86
Build and submit a capability contract with on-chain milestone escrow. Returns job ID and escrow address.
| Name | Type | Req | Description |
|---|---|---|---|
| assuranceTier | number | yes | Assurance tier 0-3 (0=self-reported, 3=ZK-proven+bonds) |
| profileId | string | – | Optional capability profile ID |
| selections | object | yes | Configuration selections |
| type | string | yes | Capability type |
No output schema declared.
No examples provided.
calculate_price ~65
Calculate price for a capability configuration. Returns base price, tier premiums, and estimated total cost.
| Name | Type | Req | Description |
|---|---|---|---|
| profileId | string | – | Optional capability profile ID |
| selections | object | yes | Configuration selections (material, dimensions, quantity, etc.) |
| type | string | yes | Capability type |
No output schema declared.
No examples provided.
calculate_roi ~70
Calculate ROI projection for onboarding equipment. Returns month-by-month revenue, cost, and break-even analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| avgJobValue | number | – | Average revenue per job in USD |
| monthlyCost | number | – | Monthly operating cost in USD |
| utilization | number | – | Expected utilization percentage (0-100) |
No output schema declared.
No examples provided.
cancel_protocol_run ~36
Cancel a protocol run. Cannot be cancelled once completed or already cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | Protocol run ID to cancel |
No output schema declared.
No examples provided.
check_invite ~40
Validate an invite code before redeeming it. Returns whether the code is valid and what it includes.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Invite code to check |
No output schema declared.
No examples provided.
check_support_replies ~65
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 this kernel and a hasUnreadReplies boolean indicating new admin messages.
| Name | Type | Req | Description |
|---|---|---|---|
| kernelId | string | yes | Operator's kernel ID |
No output schema declared.
No examples provided.
claim_bounty ~58
Claim a bounty to onboard a new capability. The operator commits to registering the capability and completing verification.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | ID of the bounty to claim |
| operatorId | string | yes | ID of the operator claiming the bounty |
No output schema declared.
No examples provided.
claim_ip_revenue ~59
Claim earned revenue from an IP asset vault. Returns the claimed amount and transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
| tokenIds | array | – | Specific royalty token IDs to claim (optional — claims all if omitted) |
No output schema declared.
No examples provided.
claim_pool ~43
Operator claims an investment pool reward after capability verification.
| Name | Type | Req | Description |
|---|---|---|---|
| operatorId | string | yes | Operator ID making the claim |
| poolId | string | yes | Pool ID to claim |
No output schema declared.
No examples provided.
close_pool ~33
Close an investment pool to new stakes. Pool enters sunset phase.
| Name | Type | Req | Description |
|---|---|---|---|
| poolId | string | yes | Pool ID to close |
No output schema declared.
No examples provided.
commit_evidence ~52
Create a Merkle commitment for an evidence bundle hash. Used as the first step in ZK proof generation for Tier 3 assurance.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleHash | string | yes | SHA-256 hash of the evidence bundle |
No output schema declared.
No examples provided.
convert_bounty_to_pool ~45
Convert an existing bounty into an investment pool. Allows community staking toward the bounty's capability.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | Bounty ID to convert to a pool |
No output schema declared.
No examples provided.
create_capability ~120
Register a capability instance for a kernel. Required before submitting jobs — the gateway needs at least one capability per kernel. Creates a liquid-handler, fdm, cnc-3axis, or other capability type.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description of what this capability does |
| kernelId | string | yes | Kernel ID to register capability for |
| name | string | – | Human-readable name for the capability |
| type | string | yes | Capability type (e.g. liquid-handler, fdm, cnc-3axis, laser-cut, document-printing) |
No output schema declared.
No examples provided.
create_investment_pool ~91
Create an investment pool for a capability bounty. Stakers earn future protocol fees when the capability goes live.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityType | string | yes | Type of capability to invest in (e.g. cnc-milling, sla-printing) |
| currency | string | – | Currency for the pool |
| description | string | yes | Description of the capability pool |
| targetAmount | number | – | Funding target amount |
No output schema declared.
No examples provided.
create_kernel ~92
Register a new Shop Kernel (physical site) on the PCC network. Part of Step 2 in the onboarding flow.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Kernel configuration JSON |
| description | string | – | Description of the site and its capabilities |
| location | object | – | Location object with address and geo coordinates |
| name | string | yes | Kernel/site name (e.g. 'BioPunk Lab - Bay A') |
No output schema declared.
No examples provided.
create_protocol ~96
Create a new protocol template draft. Returns the new template ID.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Protocol description |
| name | string | yes | Protocol name |
| parameters | array | – | Array of parameter definitions |
| requiredCapabilities | array | – | Required capability types |
| steps | array | – | Array of protocol step objects |
| tags | array | – | Tags for discovery |
| transfers | array | – | Array of transfer objects between steps |
No output schema declared.
No examples provided.
create_protocol_run ~81
Instantiate a protocol template as a run on a specific kernel with given parameter values.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Protocol template ID |
| kernelId | string | – | Kernel ID to run the protocol on |
| parameterValues | object | – | Runtime parameter values (overrides template defaults) |
| sampleIds | array | – | Sample IDs being processed in this run |
No output schema declared.
No examples provided.
create_shipment ~99
Create a new equipment shipment with origin, destination, package details, and provider.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | object | – | Destination location with label, address, geo coordinates |
| equipmentDescription | string | yes | Description of equipment being shipped |
| origin | object | – | Origin location with label, address, geo coordinates |
| package | object | – | Package details (weightKg, dimensions, fragile, etc.) |
| providerId | string | – | Logistics provider ID |
No output schema declared.
No examples provided.
delete_operator_channel ~51
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 the recipe in `describe`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Channel id. |
No output schema declared.
No examples provided.
deposit_bond ~63
Deposit an operator bond for a milestone on-chain. Required for Assurance Tier 3 jobs. Returns transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index to post bond for (0-based) |
No output schema declared.
No examples provided.
dispute_verification ~92
File a dispute against the consensus verdict. Only verifiers who submitted a response can dispute. Requires additional evidence CID.
| Name | Type | Req | Description |
|---|---|---|---|
| disputerId | string | yes | Verifier node ID filing the dispute |
| evidenceCid | string | yes | IPFS CID of the counter-evidence |
| reason | string | yes | Reason for disputing the consensus |
| requestId | string | yes | Verification request ID (hvreq_...) |
No output schema declared.
No examples provided.
distribute_royalties ~64
Set revenue splits for an IP asset among stakeholders (designer, operator, verifier, assembler, curator). Splits must sum to 100.
| Name | Type | Req | Description |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
| splits | array | yes | Revenue splits — must sum to 100 |
No output schema declared.
No examples provided.
emit_telemetry ~119
Manually emit a telemetry event for a job pipeline phase. Used by kernels and agents to report execution progress.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_ms | number | – | Phase duration in milliseconds |
| jobId | string | yes | Job ID |
| level | string | – | Log level for this event |
| metadata | object | – | Additional event metadata |
| phase | string | yes | Pipeline phase name (e.g. intake, binding, execution, evidence, settlement) |
| source | string | – | Source module or component |
| status | string | yes | Phase status |
No output schema declared.
No examples provided.
execute_composition ~172
Commit a proposed composition: drives the DAG through the workflow engine, each step records a reputation outcome, the composition's reputation is finalized when the run ends. When `PCC_COMPOSE_EXECUTE_REAL=true` is set on the gateway, steps submit real jobs via JobFacade and the workflow run is durable (@pcc/workflow). When the flag is off, the NOOP runner returns synthetic success — useful in dev/test. Re-executing an already-run composition replays the stored result (idempotent — reputation deltas are applied exactly once).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Composition id from propose_composition. Must be in `proposed` status and not expired. |
| idempotencyKey | string | – | Optional caller-supplied key (≤120 chars) to dedupe execute calls. |
No output schema declared.
No examples provided.
file_escrow_dispute ~111
File a dispute against a milestone on-chain. Challenger must post a bond and provide evidence hash. Returns transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| challengerBond | string | yes | Bond amount in wei (as string) |
| challengerEvidenceHash | string | yes | Evidence hash as 0x-prefixed hex bytes32 |
| milestoneIndex | number | yes | Milestone index to dispute (0-based) |
| reason | string | yes | Human-readable dispute reason |
No output schema declared.
No examples provided.
fork_dashboard ~146
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 rather than build from scratch — e.g. fork a 'watch pizza' dashboard and raise the budget or add a receipt window via update_dashboard. Increments the source's fork counter. You can fork any public/unlisted artifact, or a private one you own.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id (ua_...) of the artifact to fork. |
| name | string | – | Optional name for the fork (defaults to '<original> (fork)'). |
| visibility | string | – | Visibility of the fork (default 'unlisted'). |
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | object | yes | – |
| name | string | – | – |
| slug | string | – | – |
No examples provided.
fork_protocol ~68
Fork a protocol template to create your own version with parameter overrides. Returns the new fork ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Protocol template ID to fork |
| name | string | – | Name for the forked protocol |
| parameterOverrides | object | – | Parameter values to override from the source template |
No output schema declared.
No examples provided.
fund_escrow ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
No output schema declared.
No examples provided.
get_active_telemetry ~24
List currently active jobs with their current pipeline phase and telemetry status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_agent_anomalies ~36
Get anomalies involving a specific agent, plus their trust impact score.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent or kernel ID |
No output schema declared.
No examples provided.
get_anomaly_stats ~25
Get aggregate anomaly statistics — total, unresolved, by severity, by category.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_automation_status ~49
Get automation status for a specific instrument-to-instrument transfer pair.
| Name | Type | Req | Description |
|---|---|---|---|
| fromNodeId | string | yes | Source instrument node ID |
| toNodeId | string | yes | Destination instrument node ID |
No output schema declared.
No examples provided.
get_bounty_leaderboard ~44
Get the bounty hunter leaderboard showing top operators by bounties claimed and verified.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of entries to return (default 10) |
No output schema declared.
No examples provided.
get_build_options ~82
Get configuration options for a capability type (materials, dimensions, tolerances, assurance tiers). Use before calling calculate_price.
| Name | Type | Req | Description |
|---|---|---|---|
| profileId | string | – | Optional capability profile ID |
| selections | object | – | Current selections to refine available options |
| type | string | yes | Capability type (e.g. fdm, cnc-3axis, hplc) |
No output schema declared.
No examples provided.
get_bundle_ipfs ~46
Get IPFS CIDs for a bundle — returns the primary CID, metadata CID, and Filecoin deal ID if available.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID |
No output schema declared.
No examples provided.
get_capability_ip ~40
Get the Story Protocol IP registration for a capability by its capability ID.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityId | string | yes | Capability ID to look up IP registration for |
No output schema declared.
No examples provided.
get_composition ~70
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 executing, or to recover a plan id after a restart.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Composition id (returned from propose_composition). |
No output schema declared.
No examples provided.
get_dashboard ~126
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 pizza dashboard') instead of regenerating it — a saved dashboard reloads with zero regeneration. Public for public/unlisted artifacts; owner-only for private ones. Increments the load counter (a popularity signal).
| Name | Type | Req | Description |
|---|---|---|---|
| idOrSlug | string | yes | The artifact id (ua_...) or its slug (e.g. 'watch-my-pizza-8k3f', the tail of the /a/<slug> URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | object | yes | – |
| name | string | – | – |
| slug | string | – | – |
No examples provided.
get_demand_supply ~25
Get network-wide demand vs supply timeline data for capacity planning and market analysis.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_depin_stats ~25
DePIN treasury, soulbound capability certificates, and current reward epoch stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_equipment_classes ~35
List equipment classes (FDM printers, CNC mills, etc.) with market snapshot data including utilization, demand, and pricing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_escrow ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| escrowId | string | yes | DB escrow ID or on-chain contract address (0x...) |
No output schema declared.
No examples provided.
get_escrow_chain_state ~53
Read full on-chain escrow state with all milestone details from the blockchain. More detailed than get_escrow for on-chain contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | On-chain escrow contract address (0x...) |
No output schema declared.
No examples provided.
How do I install the Physical Capability Cloud MCP server?
Physical Capability Cloud is a hosted endpoint at https://capability.network/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · capability.network
claude mcp add --transport http network-capability-physical-capability-cloud 'https://capability.network/mcp'
What is the Physical Capability Cloud MCP server?
Physical Capability Cloud is an MCP server listed in the public MCP registry as network.capability/physical-capability-cloud. Discover, hire, and verify real-world physical capability through MCP. This page covers its hosted endpoint (https://capability.network/mcp).
Is the Physical Capability Cloud MCP server safe to use?
Physical Capability Cloud scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Physical Capability Cloud MCP server expose?
Physical Capability Cloud exposes 256 tools: provision_api_key, list_api_keys, revoke_api_key, setup_detect, setup_generate_config, and 251 more. Their descriptions and schemas cost roughly 22,670 tokens of context every time the server is loaded.
Does the Physical Capability Cloud MCP server require authentication?
No. We connected to Physical Capability Cloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Physical Capability Cloud MCP server still maintained?
Physical Capability Cloud is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.