Home / MCP registry index / network.capability/physical-capability-cloud
Physical Capability Cloud
network.capability/physical-capability-cloud in the official MCP registry.
Endpoint https://capability.network/mcp. Source: github.com/LamaSu/physical-capability-cloud.
The registry describes it as: Discover, hire, and verify real-world physical capability through MCP.
We read its 200 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
provision_api_key list_api_keys revoke_api_key setup_detect setup_generate_config setup_validate setup_register_device setup_test_job setup_status list_capability_types search_capabilities get_build_options calculate_price build_contract list_kernels get_kernel get_kernel_devices get_kernel_jobs create_kernel list_jobs get_job update_job_status list_escrows get_escrow get_escrow_chain_state get_escrow_events get_token_balance get_token_allowance get_escrow_dispute get_write_status fund_escrow release_milestone file_escrow_dispute deposit_bond submit_evidence_hash submit_attestation archive_evidence get_evidence_bundle grant_evidence_access list_evidence_grants archive_encrypted_bundle get_bundle_ipfs retrieve_ipfs get_lit_conditions lit_decrypt verify_evidence_zk commit_evidence get_telemetry_stats get_active_telemetry get_job_telemetry get_telemetry_logs emit_telemetry submit_for_human_verification get_verification_assignments get_verification_status respond_to_verification dispute_verification register_capability_ip register_job_evidence_ip distribute_royalties and 140 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/network-capability-physical-capability-cloud)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.