All servers · Tasks & projects · Email & messaging

OCOLO Project Requests

io.ocolo.www/project-requests · v1.0.0

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Can write (some tools are not declared read-only)
Capabilities declared	tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

Submit a data center colocation requirement to OCOLO; reaches 270+ providers. Email-verified.

streamable-http · https://www.ocolo.io/api/v1/mcp/

claude mcp add --transport http project-requests https://www.ocolo.io/api/v1/mcp/

{
  "mcpServers": {
    "project-requests": {
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}

submit_project_request
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
get_project_request_status
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`.
get_broker_guidance
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.

Repository · Website · JSON · Text for agents · Registry updated 2026-09-26