Physical Capability Cloud
REMOTE · CAPABILITY.NETWORK
Discover, hire, and verify real-world physical capability through MCP.
Available components
Last scanned (6 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 →
get_escrow_dispute ~51
Read dispute state for a specific milestone from the blockchain.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Escrow contract address (0x...) |
| milestoneIndex | number | yes | Milestone index (0-based) |
No output schema declared.
No examples provided.
get_escrow_events ~60
Get on-chain event history for an escrow contract. Returns funding, release, dispute, and bond events.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | On-chain escrow contract address (0x...) |
| fromBlock | string | – | Starting block number (optional) |
No output schema declared.
No examples provided.
get_evidence_bundle ~39
Get an encrypted evidence bundle by its bundle ID. Returns the encrypted payload and key capsules.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID |
No output schema declared.
No examples provided.
get_installations ~39
List equipment installation orders with step progress and status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by installation status (draft, scheduled, in_progress, completed) |
No output schema declared.
No examples provided.
get_ip_lineage ~39
Get the full IP lineage chain for an asset — parent capabilities and all derivative job registrations.
| Name | Type | Req | Description |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
No output schema declared.
No examples provided.
get_ip_revenue ~40
Get a revenue snapshot for an IP asset — total earned, pending claims, and recent payments.
| Name | Type | Req | Description |
|---|---|---|---|
| ipId | string | yes | IP asset ID |
No output schema declared.
No examples provided.
get_job ~30
Get job details including progress, evidence bundles, and milestones.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job ID |
No output schema declared.
No examples provided.
get_job_telemetry ~44
Get full event timeline for a specific job — all pipeline phase transitions with timings and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job ID to get pipeline timeline for |
No output schema declared.
No examples provided.
get_kernel ~31
Get kernel details including full capability objects, devices, and queue.
| Name | Type | Req | Description |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
No output schema declared.
No examples provided.
get_kernel_devices ~35
List all devices registered under a specific kernel, including adapter configs and device types.
| Name | Type | Req | Description |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
No output schema declared.
No examples provided.
get_kernel_jobs ~34
List all jobs submitted to a specific kernel, including job status and progress.
| Name | Type | Req | Description |
|---|---|---|---|
| kernelId | string | yes | Kernel ID |
No output schema declared.
No examples provided.
get_kernel_sensors ~37
Get sensor channels for a specific kernel. Returns live channel descriptors.
| Name | Type | Req | Description |
|---|---|---|---|
| kernelId | string | yes | Kernel ID to get sensors for |
No output schema declared.
No examples provided.
get_lit_conditions ~48
Get Lit Protocol access conditions for a Lit-encrypted evidence bundle. Returns the conditions that gate decryption.
| Name | Type | Req | Description |
|---|---|---|---|
| bundleId | string | yes | Evidence bundle ID (must be Lit-encrypted) |
No output schema declared.
No examples provided.
get_logistics_overview ~25
Logistics hub overview: active shipments, pending installations, and upcoming bookings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_marketplace_overview ~24
Equipment marketplace overview with demand/supply metrics across all capability types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_operator_certs ~46
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_operator_dashboard ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_operator_earnings ~55
Answers 501 not_available: operator earnings history is not recorded on this gateway. Per-job payment state is at GET /api/jobs/:jobId/execution.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Time period for earnings data |
No output schema declared.
No examples provided.
get_operator_machines ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_operator_status ~150
Four-slot substrate view for an operator: kernels, capabilities (with sla + availability), notification channels, and the per-kernel A2A agent-card URLs. Returns totals and a `missing` list naming any of the four onboarding slots that are still empty. Use this from an onboarding agent's wrap-up step to confirm 'are all four slots wired before I go live?' status is `ready` | `partial` | `unconfigured`. Public — operator slug is non-secret and the response carries no credentials (channel `credentialRef` values are vault references, not secrets).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Operator slug — typically the operator's wallet address used as `operatorAddress` on their kernels. |
No output schema declared.
No examples provided.
get_pool ~36
Get details of a specific investment pool including stakes, status, and revenue share terms.
| Name | Type | Req | Description |
|---|---|---|---|
| poolId | string | yes | Investment pool ID |
No output schema declared.
No examples provided.
get_pool_earnings ~38
Check earnings from capability investment pools for a staker address.
| Name | Type | Req | Description |
|---|---|---|---|
| staker | string | yes | Address or DID of the staker |
No output schema declared.
No examples provided.
get_popular_csd_templates ~89
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 entry includes the CSD record plus usage attribution: count, recent adopters (deduped, capped at 50), and lastUsedAt.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (1..50, default 10). |
No output schema declared.
No examples provided.
get_protocol ~35
Get protocol template details by ID. Returns steps, transfers, parameters, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Protocol template ID |
No output schema declared.
No examples provided.
get_protocol_forks ~39
List all forks of a protocol template. Shows who forked it and what parameters they changed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Protocol template ID |
No output schema declared.
No examples provided.
get_protocol_run ~38
Get protocol run status including step progress, transfer status, current phase, and evidence hashes.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | Protocol run ID |
No output schema declared.
No examples provided.
get_registration ~40
Get details of a specific machine registration by ID, including capabilities, pricing, operator info, and current status.
| Name | Type | Req | Description |
|---|---|---|---|
| registrationId | string | yes | Registration ID |
No output schema declared.
No examples provided.
get_sensor_channels ~25
List all registered sensor channels across kernels. Returns channel descriptors with units and ranges.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_settlement_epochs ~24
Get settlement epoch history showing past batch settlements with timing and operation counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_settlement_status ~28
Get settlement pipeline status including pending operations count, total value queued, and smart account address.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_shipment_quote ~71
Get shipping quotes from logistics providers based on origin, destination, weight, and priority.
| Name | Type | Req | Description |
|---|---|---|---|
| destinationZip | string | – | Destination ZIP code |
| originZip | string | – | Origin ZIP code |
| priority | string | – | Shipping priority level |
| weightKg | number | – | Package weight in kg |
No output schema declared.
No examples provided.
get_shipments ~45
List equipment shipments with tracking status. Optionally filter by status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by shipment status (in_transit, delivered, pickup_scheduled, etc.) |
No output schema declared.
No examples provided.
get_space ~35
Get detailed information about a hosting space including power, amenities, safety features, and pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Space ID |
No output schema declared.
No examples provided.
get_space_bookings ~48
List space bookings for hosting equipment. Optionally filter by status or space.
| Name | Type | Req | Description |
|---|---|---|---|
| spaceId | string | – | Filter by space ID |
| status | string | – | Filter by booking status |
No output schema declared.
No examples provided.
get_subnet_miners ~32
List verification subnet miners on the Bittensor network. Returns miner addresses, scores, and leaderboard positions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_subnet_status ~26
Get Bittensor verification subnet health, agent bridge status, and network connectivity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_telemetry_logs ~133
Query structured logs with filters for level, source, jobId, kernelId, time range, and full-text search.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Return logs after this ISO timestamp |
| before | string | – | Return logs before this ISO timestamp |
| jobId | string | – | Filter by job ID |
| kernelId | string | – | Filter by kernel ID |
| level | string | – | Filter by log level |
| limit | number | – | Max entries to return (default 200) |
| search | string | – | Full-text search query |
| source | string | – | Filter by source module |
No output schema declared.
No examples provided.
get_telemetry_stats ~30
Get aggregate pipeline telemetry statistics including phase timings, success rates, and throughput metrics across all jobs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_allowance ~71
Read the ERC-20 token allowance granted by an owner to a spender from the blockchain.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Token owner address (0x...) |
| spender | string | yes | Spender address (0x...) |
| tokenAddress | string | yes | ERC-20 token contract address (0x...) |
No output schema declared.
No examples provided.
get_token_balance ~57
Read an ERC-20 token balance for an account address from the blockchain.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account address to check balance for (0x...) |
| tokenAddress | string | yes | ERC-20 token contract address (0x...) |
No output schema declared.
No examples provided.
get_top_demand ~47
Get top demand signals aggregated by capability type. Shows which capabilities are most wanted on the network.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of top demand entries to return (default 10) |
No output schema declared.
No examples provided.
get_transfer_graphs ~27
Get resource transfer graphs showing instrument topology, transfer edges, and mechanisms for all kernels.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_unresolved_anomalies ~70
List all unresolved anomalies on the network. Filter by severity, category, or target agent.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| severity | string | – | Filter by severity: info, warning, critical |
| targetId | string | – | Filter by target agent/kernel ID |
No output schema declared.
No examples provided.
get_verification_assignments ~45
Get pending verification assignments for a verifier node. Returns requests this verifier has been assigned but not yet responded to.
| Name | Type | Req | Description |
|---|---|---|---|
| verifierId | string | yes | Verifier node ID |
No output schema declared.
No examples provided.
get_verification_status ~47
Get verification status for a request. Returns vote tally, consensus state, dispute list, and pending response count.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | Verification request ID (hvreq_...) |
No output schema declared.
No examples provided.
get_workflow ~32
Get detailed workflow information including steps, node assignments, and progress.
| Name | Type | Req | Description |
|---|---|---|---|
| workflowId | string | yes | Workflow ID |
No output schema declared.
No examples provided.
get_workflows ~42
List active instrument workflows in the orchestrator. Optionally filter by status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by workflow status (e.g. running, completed) |
No output schema declared.
No examples provided.
get_write_status ~35
Check if on-chain write operations are enabled (requires PCC_GATEWAY_PRIVATE_KEY to be configured). Returns write status and signer address.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
grant_evidence_access ~75
Grant a new recipient access to an encrypted evidence bundle. Creates a re-encrypted key capsule for the recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| accessLevel | string | – | Level of access to grant (default: full) |
| bundleId | string | yes | Evidence bundle ID |
| recipientAddress | string | yes | Recipient EVM address (0x...) |
No output schema declared.
No examples provided.
kernel_announce_capabilities ~106
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 publish a capability, use create_capability (POST /api/capabilities).
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | Capability objects to announce |
| devices | array | – | Device IDs that back these capabilities |
| kernelId | string | yes | Kernel ID |
| signature | string | – | Ed25519 signature of the announcement |
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.