# DC Blueprint data-centre intelligence (remote · dcblueprint.com)

Dated European data-centre markets, grid connection restrictions, country rules and the live grid.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `dcblueprint.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint.md), [page](https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint)

## Channel facts

- Endpoint: `https://dcblueprint.com/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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1132 tokens (~188/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DC Blueprint data-centre intelligence MCP server?

DC Blueprint data-centre intelligence is a hosted endpoint at https://dcblueprint.com/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 com-dcblueprint-data-centres 'https://dcblueprint.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dcblueprint-data-centres": {
      "url": "https://dcblueprint.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dcblueprint-data-centres": {
      "type": "http",
      "url": "https://dcblueprint.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dcblueprint-data-centres]
url = "https://dcblueprint.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dcblueprint-data-centres": {
      "type": "remote",
      "url": "https://dcblueprint.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dcblueprint-data-centres --url 'https://dcblueprint.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dcblueprint-data-centres:
    url: "https://dcblueprint.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dcblueprint-data-centres": {
      "Transport": "http",
      "Url": "https://dcblueprint.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dcblueprint-data-centres -t streamable-http -u 'https://dcblueprint.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dcblueprint-data-centres": {
      "type": "http",
      "url": "https://dcblueprint.com/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-11-04 (score 74, 0)

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

### 2026-11-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 73, +1)

- [security] Tool “data_centre_market_overview” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 72)

First indexed and scored.

## MCP tools (6)

### `data_centre_market_overview` (~241 tokens)

Data-centre market overview (Europe)

Dated overview of a European data-centre market: how many data-centre projects of 500 kW or more our pipeline tracker lists and how many are permitted or being built, the stated MW by stage on each capacity basis, who develops the most of them, whether new grid connections are paused, rationed or conditional in that country, the grid carbon intensity and power price this hour, and how many data-centre rules apply. Use for questions like "data centres in Germany", "Frankfurt data centre market", "who is building data centres in Spain". Metros: London, Frankfurt, Paris, Amsterdam, Dublin, Milan, Madrid, Helsinki, Athens, Berlin, Lyon, Warsaw, Zurich, Lisbon, Stockholm, Copenhagen, Oslo. Countries: United Kingdom, Germany, Italy, Spain, France, Finland, Netherlands, Ireland, Norway, Poland, Sweden, Greece, Denmark, Portugal, Switzerland, Belgium, Czechia, Croatia, Estonia, Romania, Austria, Lithuania, Hungary, Latvia.

Input parameters:

- `market` (string, required): A country or metro name, e.g. "Frankfurt", "Ireland", "the Netherlands".

### `grid_connection_status` (~107 tokens)

Grid connection status for data centres (Europe)

Where in Europe new grid connections for data centres are paused, rationed, conditional or congested, by country, with the measure's name, what it applies to and when it started. Without a country: the whole ranking. Use for questions like "where can I still connect a data centre to the grid in Europe", "is Ireland's grid moratorium still in force".

Input parameters:

- `country` (string): Optional European country, e.g. "Germany". Leave out for every country.

### `data_centre_rules` (~136 tokens)

Data-centre rules and deadlines by country

The national and EU rules for building and running a data centre in one European country (energy efficiency reporting, waste heat, permitting, grid), each with its status, who it applies to and the next date that matters, plus upcoming deadlines. Countries: Germany, France, Ireland, Netherlands, Italy, Spain, Sweden, Finland, Denmark, Poland, United Kingdom, Belgium, Czechia, Portugal, Switzerland, Norway, Greece, Austria, Hungary, Croatia, Lithuania, Latvia, Estonia, Romania, Bulgaria, Slovakia, Slovenia, Cyprus, Malta.

Input parameters:

- `country` (string, required): A European country, e.g. "Germany".

### `grid_carbon_and_price_now` (~130 tokens)

Grid carbon intensity and power price now

This hour's grid carbon intensity (gCO2/kWh), renewable share and day-ahead power price for a European market, the cleanest window in the next hours and its rank among 15 markets. Without a market: all markets ranked cleanest first. Markets: Germany, United Kingdom, France, Netherlands, Ireland, Italy (North), Spain, Poland, Belgium, Austria, Switzerland, Norway (NO2), Sweden (SE3), Denmark (DK1), Finland.

Input parameters:

- `market` (string): Optional market, e.g. "France". Leave out for the ranking.

### `search_dcblueprint` (~105 tokens)

Search DC Blueprint

Search DC Blueprint's pages: the four steps, the European market pages, the trackers (data-centre pipeline, grid connections, tenders, substation headroom), the Insights articles, the glossary, the operator pages and the facility pages. Returns up to 5 pages, best match first, with title, date, link and summary.

Input parameters:

- `query` (string, required): What to look for, e.g. "PUE benchmarks", "fibre latency London Frankfurt".

### `business_case_figures` (~299 tokens)

Data-centre business-case figures for one market

The inputs of a colocation data-centre business case for one European market: construction cost per MW, colocation prices per kW-month, electricity price, staff cost, guarding, property tax, exit yield, grid wait, permitting and grid charges, with low and high. Needs a personal DC Blueprint key (Authorization: Bearer) from an account with a DC Blueprint licence or trial. Ask for one market for the project at hand: every figure costs 5 credits, one figure (the "figure" argument) 1; the same answer again in the calendar month costs nothing. It is not a way to copy the catalogue market by market. Markets: Amsterdam, Athens, Berlin, Copenhagen, Dublin, Frankfurt, Helsinki, Lisbon, London, Madrid, Milan, Oslo, Paris, Stockholm, Vienna, Warsaw, Zurich. Figures: Construction cost, Colocation price, retail, Colocation price, wholesale, Colocation price, large deals, Electricity price, Cost of a site employee, Guarding and monitoring, Property tax, Exit yield, Wait for a grid connection, Permitting, Grid connection charge, Customer substation.

Input parameters:

- `figure` (string): Optional: one figure only, e.g. "Construction cost" or "Exit yield" (1 credit). Leave it out for every figure of the market.
- `market` (string, required): A business-case market, e.g. "Frankfurt", "Milan".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72

## Common questions

### What is the DC Blueprint data-centre intelligence MCP server?

DC Blueprint data-centre intelligence is an MCP server listed in the public MCP registry as com.dcblueprint/data-centres. Dated European data-centre markets, grid connection restrictions, country rules and the live grid. This page covers its hosted endpoint (https://dcblueprint.com/mcp).

### Is the DC Blueprint data-centre intelligence MCP server safe to use?

DC Blueprint data-centre intelligence scores 74 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 DC Blueprint data-centre intelligence MCP server expose?

DC Blueprint data-centre intelligence exposes 6 tools: data_centre_market_overview, grid_connection_status, data_centre_rules, grid_carbon_and_price_now, search_dcblueprint, business_case_figures. Their descriptions and schemas cost roughly 1,018 tokens of context every time the server is loaded.

### Does the DC Blueprint data-centre intelligence MCP server require authentication?

No. We connected to DC Blueprint data-centre intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DC Blueprint data-centre intelligence MCP server still maintained?

DC Blueprint data-centre intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DC Blueprint data-centre intelligence MCP server?

VerifyMCP ran 13 checks on DC Blueprint data-centre intelligence, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://dcblueprint.com/mcp
- Website: https://dcblueprint.com/connector
- Changelog RSS feed: https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint.json
- HTML version of this page: https://verifymcp.io/servers/com-dcblueprint-data-centres/dcblueprint