mcp-registry/network.capability/physical-capability-cloud · v2.19.3+sha256.a93b6fab5a8a325daafb456917b722efa1823dfe6585acecd7d65029a67d4ec9
As of 2026-10-20 17:16 UTC, the Capability Physical Capability Cloud MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Discover, hire, and verify real-world physical capability through MCP.
Claude Code
claude mcp add --transport http capability-physical-capability-cloud-mcp https://capability.network/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"capability-physical-capability-cloud-mcp": {
"type": "http",
"url": "https://capability.network/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 tool definition(s) exceed ~1,200 tokens each (largest: render_pcc_dashboard_ir, ~2,303).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~4,469 tokens every session. How to fix →
256 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
50 parameter(s) across 10 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).
Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →
Loading this server's tool list costs an agent ~43,308 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~1,822 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 2 tool(s) removed and 4 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fnetwork.capability%2Fphysical-capability-cloud/fixes
{
"name": "pcc_op_capability_request_quote",
"description": "Price a configured PCC capability (typed operation). Returns the itemized quote for the given capability type + selections. Pure calculation — no funds move and nothing is created. Maps to POST /api/build/price.",
"inputSchema": {
"type": "object",
"required": [
"type",
"selections"
],
"properties": {
"type": {
"type": "string",
"description": "Capability type, e.g. 'fdm'."
},
"profileId": {
"type": "string"
},
"selections": {
"type": "object",
"description": "Parameter selections."
},
"capabilityId": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/network.capability/physical-capability-cloud"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/network.capability/physical-capability-cloud"}) over MCP.
render_pcc_dashboard_ir ~2,303 tokensrender_pcc_dashboard ~2,298 tokenspcc_report_attempt ~1,668 tokenspcc_report ~787 tokenspcc_trilobio_build_config ~646 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fnetwork.capability%2Fphysical-capability-cloud?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fnetwork.capability%2Fphysical-capability-cloud?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fnetwork.capability%2Fphysical-capability-cloud.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fnetwork.capability%2Fphysical-capability-cloud.svg :target: https://glimind.com/server/mcp-registry%2Fnetwork.capability%2Fphysical-capability-cloud?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f987bbd8bbf5cd26…, first seen 2026-10-17, included at leaf 16364 of 34,069. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable ml servers · most reliable other servers · most reliable storage servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 17:16 UTC, the Capability Physical Capability Cloud MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Capability Physical Capability Cloud MCP server advertises 256 tools, including activate_registration, advance_automation, analyze_machine_docs, approve_registration, archive_encrypted_bundle.
Point your MCP client at this streamable-http endpoint: https://capability.network/mcp
Glimind scanned all 256 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.