Physical Capability Cloud
Server Details
Discover, hire, and verify real-world physical capability through MCP.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- LamaSu/physical-capability-cloud
- GitHub Stars
- 1
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
255 tool updates
- First observed
activate_registration - First observed
advance_automation - First observed
analyze_machine_docs - First observed
approve_registration - First observed
approve_token - First observed
archive_encrypted_bundle - First observed
archive_evidence - First observed
attach_operator_channel - First observed
build_contract - First observed
calculate_price - First observed
calculate_roi - First observed
cancel_protocol_run - First observed
check_invite - First observed
check_support_replies - First observed
claim_bounty - First observed
claim_ip_revenue - First observed
claim_pool - First observed
close_pool - First observed
commit_evidence - First observed
convert_bounty_to_pool - First observed
create_capability - First observed
create_investment_pool - First observed
create_kernel - First observed
create_protocol - First observed
create_protocol_run - First observed
create_shipment - First observed
delete_operator_channel - First observed
deposit_bond - First observed
dispute_verification - First observed
distribute_royalties - First observed
emit_telemetry - First observed
execute_composition - First observed
file_escrow_dispute - First observed
fork_dashboard - First observed
fork_protocol - First observed
fund_escrow - First observed
get_active_telemetry - First observed
get_agent_anomalies - First observed
get_anomaly_stats - First observed
get_automation_status - First observed
get_bounty_leaderboard - First observed
get_build_options - First observed
get_bundle_ipfs - First observed
get_capability_ip - First observed
get_composition - First observed
get_dashboard - First observed
get_demand_supply - First observed
get_depin_stats - First observed
get_equipment_classes - First observed
get_escrow - First observed
get_escrow_chain_state - First observed
get_escrow_dispute - First observed
get_escrow_events - First observed
get_evidence_bundle - First observed
get_installations - First observed
get_ip_lineage - First observed
get_ip_revenue - First observed
get_job - First observed
get_job_telemetry - First observed
get_kernel - First observed
get_kernel_devices - First observed
get_kernel_jobs - First observed
get_kernel_sensors - First observed
get_lit_conditions - First observed
get_logistics_overview - First observed
get_marketplace_overview - First observed
get_operator_certs - First observed
get_operator_dashboard - First observed
get_operator_earnings - First observed
get_operator_machines - First observed
get_operator_status - First observed
get_pool - First observed
get_pool_earnings - First observed
get_popular_csd_templates - First observed
get_protocol - First observed
get_protocol_forks - First observed
get_protocol_run - First observed
get_registration - First observed
get_sensor_channels - First observed
get_settlement_epochs - First observed
get_settlement_status - First observed
get_shipment_quote - First observed
get_shipments - First observed
get_space - First observed
get_space_bookings - First observed
get_subnet_miners - First observed
get_subnet_status - First observed
get_telemetry_logs - First observed
get_telemetry_stats - First observed
get_token_allowance - First observed
get_token_balance - First observed
get_top_demand - First observed
get_transfer_graphs - First observed
get_unresolved_anomalies - First observed
get_verification_assignments - First observed
get_verification_status - First observed
get_workflow - First observed
get_workflows - First observed
get_write_status - First observed
grant_evidence_access - First observed
kernel_announce_capabilities - First observed
kernel_heartbeat - First observed
list_api_keys - First observed
list_automation_status - First observed
list_batches - First observed
list_bounties - First observed
list_capability_types - First observed
list_conversations - First observed
list_escrows - First observed
list_evidence - First observed
list_evidence_grants - First observed
list_jobs - First observed
list_kernels - First observed
list_operator_channels - First observed
list_pools - First observed
list_protocol_runs - First observed
list_protocols - First observed
list_registrations - First observed
list_transfer_agents - First observed
lit_decrypt - First observed
marketplace_categories - First observed
marketplace_create_listing - First observed
marketplace_delete_listing - First observed
marketplace_get_listing - First observed
marketplace_get_order - First observed
marketplace_list_listings - First observed
marketplace_list_orders - First observed
marketplace_place_order - First observed
marketplace_update_listing - First observed
match_spaces - First observed
mint_certificate - First observed
near_intent - First observed
near_intent_status - First observed
near_quote - First observed
near_status - First observed
onboard_machine - First observed
operator_heartbeat - First observed
operator_poll_jobs - First observed
operator_push_evidence - First observed
operator_update_job_status - First observed
pause_protocol_run - First observed
pay_ip_royalty - First observed
pcc_assign_node_operator - First observed
pcc_camera_latest - First observed
pcc_cancel_request - First observed
pcc_capture_anchor - First observed
pcc_capture_challenge - First observed
pcc_capture_class_registry - First observed
pcc_capture_status - First observed
pcc_capture_upload - First observed
pcc_chat_history - First observed
pcc_chat_send - First observed
pcc_contributor_list - First observed
pcc_contributor_register - First observed
pcc_create_scope - First observed
pcc_decompose_request - First observed
pcc_dht_announce - First observed
pcc_dht_metrics - First observed
pcc_dht_peers - First observed
pcc_dht_query - First observed
pcc_generate_ui - First observed
pcc_get_request - First observed
pcc_get_request_critical_path - First observed
pcc_get_request_dag - First observed
pcc_get_tool_manifest - First observed
pcc_get_tool_result - First observed
pcc_job_complete - First observed
pcc_job_settlement - First observed
pcc_list_requests - First observed
pcc_list_verdicts - First observed
pcc_onboard_session_build_agent - First observed
pcc_onboard_session_ingest_docs - First observed
pcc_onboard_session_live_data - First observed
pcc_onboard_session_scrape - First observed
pcc_onboard_session_start - First observed
pcc_onboard_session_status - First observed
pcc_oracle_status - First observed
pcc_oracle_verify - First observed
pcc_orchestrator_list_templates - First observed
pcc_orchestrator_match_capabilities - First observed
pcc_protocol_fee - First observed
pcc_publish_request - First observed
pcc_relay_generic_tool_call - First observed
pcc_relay_tool_call - First observed
pcc_report - First observed
pcc_revoke_scope - First observed
pcc_schedule_evaluate - First observed
pcc_schedule_get - First observed
pcc_schedule_publish - First observed
pcc_scope_audit - First observed
pcc_submit_paid_job - First observed
pcc_submit_request - First observed
pcc_training_manifest_get - First observed
pcc_training_manifest_set - First observed
pcc_trilobio_build_config - First observed
pcc_trilobio_capability_template - First observed
pcc_trilobio_validate_options - First observed
pcc_trilobio_validate_script - First observed
pcc_update_node_status - First observed
pcc_update_request - First observed
pcc_verifier_health - First observed
propose_composition - First observed
protocol_create_escrow - First observed
protocol_escrow_fees - First observed
protocol_fee - First observed
protocol_state - First observed
protocol_token_fees - First observed
prove_registration - First observed
provision_api_key - First observed
publish_protocol - First observed
raise_ip_dispute - First observed
record_episode - First observed
redeem_invite - First observed
register_capability_ip - First observed
register_job_evidence_ip - First observed
reject_registration - First observed
release_milestone - First observed
render_pcc_dashboard - First observed
reply_to_support_thread - First observed
report_anomaly - First observed
report_protocol_failure - First observed
resolve_anomaly - First observed
respond_to_verification - First observed
resume_protocol_run - First observed
retrieve_ipfs - First observed
revoke_api_key - First observed
save_dashboard - First observed
search_capabilities - First observed
search_dashboards - First observed
search_spaces - First observed
send_diagnostics - First observed
send_support_message - First observed
setup_detect - First observed
setup_generate_config - First observed
setup_register_device - First observed
setup_status - First observed
setup_test_job - First observed
setup_validate - First observed
stake_in_pool - First observed
start_protocol_run - First observed
submit_attestation - First observed
submit_demand - First observed
submit_evidence_hash - First observed
submit_feedback - First observed
submit_for_human_verification - First observed
suggest_csd_templates - First observed
system_telemetry - First observed
test_operator_channels - First observed
update_dashboard - First observed
update_job_status - First observed
update_operator_channel - First observed
update_protocol - First observed
validate_protocol - First observed
verify_bounty - First observed
verify_evidence_zk
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Hire specialists by the hour — search, schedule, and pay via MCP protocol.
Agent-first task marketplace MCP — discover, claim, and deliver paid workspace tasks.
Find and call the right MCP server for any task - pay per use, no install.
Dispatch real-world physical tasks to verified human operators. Escrow or direct-settlement.
Related MCP Servers
- AlicenseBqualityAmaintenanceHire specialists by the hour — search, schedule, and pay via MCP protocol.351MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that lets AI agents dispatch physical tasks to robot executors and track the task -> proof -> verify -> settle workflow, enabling task creation, executor discovery, proof submission, and verification status checks.MIT
- AlicenseAqualityAmaintenanceYour AI finds the right people for you. Agent-to-agent networking via MCP. Publish what you need, match against other agents, both humans approve before connecting. Ed25519 signed, hosted API.71146Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides agent-to-agent paid access to motion capture, rehabilitation biomechanics, location threat intelligence, and commercial truck-sighting data via 21 MCP tools with USDC payments.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Most tools have specific names that clearly distinguish their purpose, e.g., get_kernel vs get_kernel_devices. However, some generic verbs like report_anomaly and report_protocol_failure could cause confusion, and there are many get_/list_ variants.
The naming convention is predominantly snake_case verb_noun, which is consistent. However, some tools use the pcc_ prefix while most do not, and there is minor mixing of get_ vs list_ patterns, but overall it is predictable.
With 255 tools, the count is excessively high even for a broad domain. It overwhelms agents and makes selection costly. The server would benefit from consolidation or modularization.
The tool surface is remarkably comprehensive, covering registration, job lifecycle, escrow, verification, onboarding, logistics, marketplace, IP, and more. Minor gaps exist (e.g., no tool for deleting a kernel or user management beyond API keys), but overall it is well-covered.