OCOLO Project Requests
REMOTE · WWW.OCOLO.IO · SCANNED SEP 29
Submit a data center colocation requirement to OCOLO; reaches 270+ providers. Email-verified.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~284/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the OCOLO Project Requests MCP server?
OCOLO Project Requests is a hosted endpoint at https://www.ocolo.io/api/v1/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 · www.ocolo.io
claude mcp add --transport http io-ocolo-www-project-requests 'https://www.ocolo.io/api/v1/mcp/'
{
"mcpServers": {
"io-ocolo-www-project-requests": {
"url": "https://www.ocolo.io/api/v1/mcp/"
}
}
} {
"servers": {
"io-ocolo-www-project-requests": {
"type": "http",
"url": "https://www.ocolo.io/api/v1/mcp/"
}
}
} [mcp_servers.io-ocolo-www-project-requests] url = "https://www.ocolo.io/api/v1/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-ocolo-www-project-requests": {
"type": "remote",
"url": "https://www.ocolo.io/api/v1/mcp/",
"enabled": true
}
}
} openclaw mcp add io-ocolo-www-project-requests --url 'https://www.ocolo.io/api/v1/mcp/' --transport streamable-http
mcp_servers:
io-ocolo-www-project-requests:
url: "https://www.ocolo.io/api/v1/mcp/" {
"McpServers": {
"io-ocolo-www-project-requests": {
"Transport": "http",
"Url": "https://www.ocolo.io/api/v1/mcp/"
}
}
} assistant mcp add io-ocolo-www-project-requests -t streamable-http -u 'https://www.ocolo.io/api/v1/mcp/'
{
"mcpServers": {
"io-ocolo-www-project-requests": {
"type": "http",
"url": "https://www.ocolo.io/api/v1/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
- Tool “submit_project_request” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 62
First indexed and scored.
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 29 Sept 2026 · Probed https://www.ocolo.io/api/v1/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ocolo.io | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 17 Dec 2025 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 46b18ebf18c8efa41dac43b70080743 |
| SANs: *.ocolo.io | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.ocolo.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| ocolo.io. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.ocolo.io/api/v1/mcp/ | Verified | 200 | |
| http (plaintext) | http://www.ocolo.io/api/v1/mcp/ | Inconclusive | 405 |
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_broker_guidance How OCOLO works and broker etiquette ~65
Why send a colocation requirement to OCOLO, what happens after submission, and the broker etiquette to follow (keep options open, engage 1-3 brokers total, do not contact providers directly while OCOLO is coordinating). Read this before submit_project_request.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_project_request_status Check the status of a submitted request ~73
Poll a request submitted with submit_project_request. Needs the request_id and the status_token from that call. Poll at most hourly while pending and daily once confirmed. If edited_by_contact is true, read the final requirements from `current`.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
submit_project_request Submit a colocation project request to OCOLO ~635
Submit a data center colocation / space requirement to OCOLO on behalf of the user. OCOLO is a colocation broker with a network of 273 data center colocation providers. Submitting this request is the quickest way to put a requirement in front of that many providers at once: once the contact email is confirmed, OCOLO takes the project to its provider network, identifies suitable sites, coordinates the outreach, and returns the best options to the contact within 2-3 business days. Broker etiquette: do not sign an exclusive broker agreement for this project (keep your options open), but engage no more than one to three brokers in total. Providers see every inbound approach. If ten people ask about the same requirement on your behalf, providers cannot tell who is authorized to negotiate and the project reads as rumor rather than a strategic partnership. Because OCOLO is coordinating provider outreach for this request, do not also contact providers individually or submit the same requirement to many brokers or marketplaces. Required: location, contact.email, and agent.on_behalf_of_confirmed=true (only after the user has asked you to do this). Power may be given as power_kw or power_mw. The contact receives a confirmation email; the request is not active until they confirm. Keep the returned status_token to check status later. Relay guidance.what_happens_next to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_services | – | – | Remote hands, managed services, migration help, etc. |
| agent | object | yes | – |
| bandwidth_mbps | number | – | Connectivity bandwidth in Mbps. |
| bandwidth_text | string | – | Free-text connectivity requirement if bandwidth_mbps does not fit. |
| cabinets | integer | – | Number of cabinets (racks). |
| callback_url | string | – | Reserved for status webhooks (https only). Stored but not called in v1. |
| compliance | – | – | Compliance / certification requirements. |
| contact | object | yes | – |
| customer_profile | string | – | Who the buyer is. |
| excluded_vendors | – | – | Providers the user will not consider. |
| expected_contract_date | string | – | Expected contract signature date, ISO YYYY-MM-DD. |
| idempotency_key | string | – | Client-chosen key. Resubmitting with the same key and contact email returns the original request instead of creating a duplicate. |
| location | string | yes | City, metro, region or country where the capacity is needed. Required. |
| notes | string | – | Notes for OCOLO staff (not shown to providers). |
| power_kw | number | – | Total critical IT power required, in kW. Send this or power_mw. |
| power_mw | number | – | Total critical IT power required, in MW. Normalized to kW. |
| power_per_cabinet_kw | number | – | Target power density per cabinet, in kW. |
| preferred_vendors | – | – | Providers the user prefers. |
| requested_delivery_date | string | – | Target ready-for-service date, ISO YYYY-MM-DD. |
| requirements_text | string | – | Everything else that matters: cooling, redundancy, certifications, term length, growth plan, budget notes. |
No output schema declared.
No examples provided.
What is the OCOLO Project Requests MCP server?
OCOLO Project Requests is an MCP server listed in the public MCP registry as io.ocolo.www/project-requests. Submit a data center colocation requirement to OCOLO; reaches 270+ providers. Email-verified. This page covers its hosted endpoint (https://www.ocolo.io/api/v1/mcp/).
Is the OCOLO Project Requests MCP server safe to use?
OCOLO Project Requests scores 64 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 OCOLO Project Requests MCP server expose?
OCOLO Project Requests exposes 3 tools: submit_project_request, get_project_request_status, get_broker_guidance. Their descriptions and schemas cost roughly 773 tokens of context every time the server is loaded.
Does the OCOLO Project Requests MCP server require authentication?
No. We connected to OCOLO Project Requests without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OCOLO Project Requests MCP server still maintained?
OCOLO Project Requests is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.