# OCOLO Project Requests

- Registry name: `io.ocolo.www/project-requests` · version 1.0.0
- Categories (automatic, keyword rules): Tasks & projects, Productivity, Email & messaging
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.ocolo.www%2Fproject-requests
- Server page: https://mcpstation.net/s/io.ocolo.www--project-requests.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

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

## Tools (as reported by the server, not verified)

- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html