# OCOLO Project Requests (remote · www.ocolo.io)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `www.ocolo.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-ocolo-www-project-requests/api-v1-mcp.md), [page](https://verifymcp.io/servers/io-ocolo-www-project-requests/api-v1-mcp)

## Channel facts

- Endpoint: `https://www.ocolo.io/api/v1/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "io-ocolo-www-project-requests": {
      "type": "http",
      "url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-ocolo-www-project-requests]
url = "https://www.ocolo.io/api/v1/mcp/"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add io-ocolo-www-project-requests --url 'https://www.ocolo.io/api/v1/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-ocolo-www-project-requests:
    url: "https://www.ocolo.io/api/v1/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "io-ocolo-www-project-requests": {
      "Transport": "http",
      "Url": "https://www.ocolo.io/api/v1/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-ocolo-www-project-requests -t streamable-http -u 'https://www.ocolo.io/api/v1/mcp/'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 64, +1)

- [security] Tool “submit_project_request” rewrote its description, which is the text the model reads

### 2026-09-28 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-26 (score 62)

First indexed and scored.

## MCP tools (3)

### `submit_project_request` (~635 tokens)

Submit a colocation project request to OCOLO

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.

Input parameters:

- `additional_services`: Remote hands, managed services, migration help, etc.
- `agent` (object, required)
- `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, required)
- `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, required): 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.

### `get_project_request_status` (~73 tokens)

Check the status of a submitted request

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

Input parameters:

- `request_id` (string, required)
- `status_token` (string, required)

### `get_broker_guidance` (~65 tokens)

How OCOLO works and broker etiquette

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-ocolo-www-project-requests/api-v1-mcp#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 63
- 2026-09-27: 63
- 2026-09-26: 62

## Common questions

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

## Links

- Remote endpoint: https://www.ocolo.io/api/v1/mcp/
- Repository: https://github.com/Ocolo-io/ocolo-agent-api
- Website: https://www.ocolo.io/for-agents/
- Changelog RSS feed: https://verifymcp.io/servers/io-ocolo-www-project-requests/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-ocolo-www-project-requests/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-ocolo-www-project-requests/api-v1-mcp