OCOLO Project Requests

Name: OCOLO Project Requests
Author: io.ocolo.www

MCP serverMCP

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

by io.ocolo.wwwrepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ocolo-project-requests","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability47/47 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	204 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
10 h ago	mcp initialize	ok	200	260 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
17 h ago	mcp initialize	ok	200	211 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
25 h ago	mcp initialize	ok	200	273 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
31 h ago	mcp initialize	ok	200	206 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	249 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	482 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	212 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	199 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	206 ms	server ocolo 1.0.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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 pr
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
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 n

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.ocolo.www/project-requests

first seen 13 d ago · fetched 33 h agoopen ↗

Field history (7 recent events)

13 d ago · declared · summary → "Submit a data center colocation requirement to OCOLO; reaches 270+ providers. Email-verified."
13 d ago · declared · description → "Submit a data center colocation requirement to OCOLO; reaches 270+ providers. Email-verified."
13 d ago · declared · publisherName → "io.ocolo.www"
13 d ago · declared · homepageUrl → "https://www.ocolo.io/for-agents/"
13 d ago · declared · repoUrl → "https://github.com/Ocolo-io/ocolo-agent-api"
13 d ago · declared · version → "1.0.0"
13 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from