OCOLO Project Requests MCP server

online · 100% uptime

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

No reviews yet

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

B81/100grade B

Write a review Run it

What users say

No reviews yet

Be the first

Safety scan

B81/100

full report

Adoption

Growing

0 stars

Reviews

Write one

Nobody has reviewed OCOLO Project Requests yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

OCOLO Project Requests tools (3, 1 write)

write = sends, deletes, buys or posts

get_broker_guidanceFree
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.
get_project_request_statusFree
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`.
submit_project_requestwrite actionFree
Submit a data center colocation / space requirement to OCOLO on behalf of the user. OCOLO is a colocation broker with a network of 272 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.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 high

–Code scanremote-only server, no package to scann/a
Live reliabilityremote reachable in 410ms20/20
Tool poisoning3 tool descriptions checked15/15
Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
Maintenancelast push 0 days ago15/15
Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10

Findings (1)

highWrite-action tools reachable without authenticationauth.open-write

Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How OCOLO Project Requests compares

Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 81/100; higher than 68% of 916 Email servers
Tools: 3; the typical Email server has 7
Tools that change things: 33%; typical: 25%. Fewer write tools means less an agent can break
Uptime: 100%; of our recent checks; the typical remote Email server answers 100%
Response time: 327 ms; faster than 49% of 609 Email servers

What its tools let an agent do: 2 read · 1 change

Install OCOLO Project Requests in Claude Code, Cursor or VS Code

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

Add to Cursor

What the publisher says

From the OCOLO Project Requests repository's README, as published. We do not edit it. Read it on GitHub

OCOLO Project Request API (for AI agents)

Submit a data center colocation requirement to OCOLO on behalf of a human, from any AI agent. OCOLO is a colocation broker with a network of 270+ data center providers; one submission puts the requirement in front of all of them, and OCOLO returns the best options to the contact within 2-3 business days. No API key, no account: the contact confirms by email.

Human guide: https://www.ocolo.io/for-agents/
OpenAPI 3.1: https://www.ocolo.io/api/v1/openapi.json (copy in this repo: openapi.json, refreshed with ./sync-spec.sh; the live document is canonical)
MCP server (Streamable HTTP): https://www.ocolo.io/api/v1/mcp/
Discovery: https://www.ocolo.io/.well-known/ocolo-agent.json, https://www.ocolo.io/llms.txt

Quick start (REST)

curl -X POST https://www.ocolo.io/api/v1/project-requests/ \
  -H 'Content-Type: application/json' \
  -d @examples/request.json

Response (201): requestid, status: pendingconfirmation, statusurl, a statustoken to keep, machine-readable next_steps, and a guidance object. Poll status with Authorization: Bearer .

import requests
r = requests.post("https://www.ocolo.io/api/v1/project-requests/", json={
    "location": "Northern Virginia, USA",
    "power_mw": 2,
    "cabinets": 60,
    "requested_delivery_date": "2027-03-01",
    "requirements_text": "Liquid cooling preferred, N+1 or better, SOC 2 required.",
    "contact": {"name": "Jane Doe", "email": "jane@acme.com", "company": "Acme"},
    "agent": {"name": "my-agent", "on_behalf_of_confirmed": True},
    "idempotency_key": "acme-nova-2027-q1",
}).json()
print(r["status"], r["status_url"])
for step in r["next_steps"]:
    print(step["action"], step.get("detail", ""))

MCP

Add https://www.ocolo.io/api/v1/mcp/ as a remote MCP server (no auth). Tools:

server.json in this repo is the MCP Registry manifest.

What happens after you submit

also edit the request on OCOLO's form first; the requestid stays the same and the status body then carries editedby_contact: true and the final values under current).

The contact receives a confirmation email. Nothing is active until they confirm (they can

outreach.

OCOLO takes the project to its provider network, finds suitable sites and coordinates the

OCOLO replies to the contact within 2-3 business days.

Broker etiquette (please follow)

approach; ten people asking about the same requirement reads as rumor, not a strategic partnership.

Do not sign an exclusive broker agreement; keep the user's options open.
Engage no more than 1-3 brokers in total for a single project. Providers see every inbound

requirement to other brokers or marketplaces.

While OCOLO is coordinating a request, do not contact providers directly or submit the same

Every API response repeats this in its guidance field.

Limits

Rate limited per IP and per contact email; honour Retry-After and use idempotency_key for safe retries. Bodies over 64 KB are rejected. Questions: info@ocolo.io.

Nothing above is checked by us. What we check is on the safety report.

OCOLO Project Requests: common questions

Is OCOLO Project Requests MCP server safe?: Mostly: it is graded B (81/100). Read the OCOLO Project Requests safety report
How do I install OCOLO Project Requests?: It runs remotely at www.ocolo.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does OCOLO Project Requests need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is OCOLO Project Requests maintained?: The last commit was 39 days ago (2026-09-26). The latest release is v1.0.0.
Is OCOLO Project Requests up?: 100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of OCOLO Project Requests?: Servers from other publishers that do the same job: e2a — email for AI agents MCP server, e2a — email for AI agents MCP server and Notifykit MCP server.
How does OCOLO Project Requests compare with other Email MCP servers?: safety score 81/100 (higher than 68% of 916 Email servers); tools 3 (the typical Email server has 7); tools that change things 33% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to OCOLO Project Requests

Same job from other publishers: the closest match first, then the best rated.

e2a — email for AI agents
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
not reviewed
Established
A
e2a — email for AI agents
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
not reviewed
Established
A
Notifykit
Unified notifications for Next.js. Multi-provider SMS, email, and push.
not reviewed
Growing
A
Mailoo - Email MCP Server
Email MCP server for AI agents: IMAP/SMTP, Gmail, Outlook, calendar, ManageSieve, AI triage, OAuth2.
5.0(1)
Growing
A
emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
not reviewed
Established
A

Run it through the gateway

With the gateway added, ask your agent for it by name:

agent prompt

call io.ocolo.www/project-requests → get_broker_guidance

Free per call. Metered, capped by your key, logged for reliability.

Add the gateway (gw.mcp.market)

Rating: —
Safety grade: B · 81/100
Stars: 0
Downloads/wk: –
Price: Free
Licence: NOASSERTION
Transport: Remote
Uptime: 100% · 28/28 checks
Version: 1.0.0
Category: Email
Last release: 2026-09-26

Endpoint

https://www.ocolo.io/api/v1/mcp/

streamable-http

Own this server?

Claim it to keep the listing current and reply to reviews. Claiming never changes the grade or hides a review.

Claim listing

Badge for your README

Shows the safety grade and links back to this page. It updates itself after every scan and review.

[![mcp.market](https://mcp.market/badge/ocolo-project-requests.svg)](https://mcp.market/server/ocolo-project-requests)

How the badge works