MCP servers observed by Lowdown
network.capability/physical-capability-cloud MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 182 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:network.capability/physical-capability-cloud
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:network.capability/physical-capability-cloud?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
182 tools on 2026-11-17:
activate_registrationanalyze_machine_docsapprove_registrationarchive_encrypted_bundlearchive_evidenceattach_operator_channelbuild_contractcalculate_pricecheck_invitecheck_support_repliesclaim_bountyclaim_ip_revenueclaim_poolclose_poolcommit_evidenceconvert_bounty_to_poolcreate_capabilitycreate_investment_poolcreate_kerneldelete_operator_channeldispute_verificationdistribute_royaltiesemit_telemetryexecute_compositionfork_dashboardget_active_telemetryget_agent_anomaliesget_anomaly_statsget_bounty_leaderboardget_build_optionsget_bundle_ipfsget_capability_ipget_compositionget_dashboardget_escrowget_escrow_chain_stateget_escrow_disputeget_escrow_eventsget_evidence_bundleget_ip_lineageget_ip_revenueget_jobget_job_telemetryget_kernelget_kernel_devicesget_kernel_jobsget_kernel_sensorsget_lit_conditionsget_operator_certsget_operator_dashboardget_operator_earningsget_operator_machinesget_operator_statusget_poolget_pool_earningsget_popular_csd_templatesget_registrationget_sensor_channelsget_settlement_epochsget_settlement_statusget_subnet_minersget_subnet_statusget_telemetry_logsget_telemetry_statsget_token_allowanceget_token_balanceget_top_demandget_unresolved_anomaliesget_verification_assignmentsget_verification_statusget_write_statusgrant_evidence_accesskernel_announce_capabilitieskernel_heartbeatlist_api_keyslist_batcheslist_bountieslist_capability_typeslist_escrowslist_evidencelist_evidence_grantslist_jobslist_kernelslist_operator_channelslist_poolslist_registrationslit_decryptnear_intentnear_intent_statusnear_quotenear_statusonboard_machineoperator_heartbeatoperator_poll_jobsoperator_push_evidenceoperator_update_job_statuspay_ip_royaltypcc.op.capability.request_quotepcc_assign_node_operatorpcc_cancel_requestpcc_capture_anchorpcc_capture_challengepcc_capture_class_registrypcc_capture_statuspcc_capture_uploadpcc_contributor_listpcc_contributor_registerpcc_decompose_requestpcc_dht_metricspcc_dht_peerspcc_dht_querypcc_get_requestpcc_get_request_critical_pathpcc_get_request_dagpcc_job_completepcc_job_settlementpcc_list_requestspcc_list_verdictspcc_onboard_session_build_agentpcc_onboard_session_ingest_docspcc_onboard_session_live_datapcc_onboard_session_scrapepcc_onboard_session_startpcc_onboard_session_statuspcc_oracle_statuspcc_oracle_verifypcc_orchestrator_list_templatespcc_orchestrator_match_capabilitiespcc_publish_requestpcc_reportpcc_report_attemptpcc_schedule_evaluatepcc_schedule_getpcc_schedule_publishpcc_submit_paid_jobpcc_submit_requestpcc_training_manifest_getpcc_training_manifest_setpcc_update_node_statuspcc_update_requestpcc_verifier_healthpropose_compositionprotocol_stateprove_registrationprovision_api_keyraise_ip_disputeredeem_inviteregister_capability_ipregister_job_evidence_ipreject_registrationrender_pcc_dashboardrender_pcc_dashboard_irreply_to_support_threadreport_anomalyreport_protocol_failureresolve_anomalyrespond_to_verificationretrieve_ipfsrevoke_api_keysave_dashboardsearch_capabilitiessearch_dashboardssend_diagnosticssend_support_messagesetup_detectsetup_generate_configsetup_register_devicesetup_statussetup_test_jobsetup_validatestake_in_poolsubmit_demandsubmit_feedbacksubmit_for_human_verificationsuggest_csd_templatessystem_telemetrytest_operator_channelsupdate_dashboardupdate_job_statusupdate_operator_channelverify_bountyverify_evidence_zk
MCP Registry declaration
- Registry name:
network.capability/physical-capability-cloud - Declared version: 2.19.0
- Status: active
- Declared hosts:
capability.network
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:network.capability/physical-capability-cloud", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:network.capability/physical-capability-cloud?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).