DC Blueprint data-centre intelligence
REMOTE · DCBLUEPRINT.COM
Dated European data-centre markets, grid connection restrictions, country rules and the live grid.
Available components
Last scanned (5 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- 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 security
- 3 Nov 26 +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.
- 1 Nov 26 +1
- Tool “data_centre_market_overview” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://dcblueprint.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dcblueprint.com | CN=YE2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 643f2db26ac6dd336d90117697858679404 |
| SANs: *.dcblueprint.com, dcblueprint.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dcblueprint.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dcblueprint.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dcblueprint.com/mcp | Verified | 200 | |
| http (plaintext) | http://dcblueprint.com/mcp | HTTPS enforced | 308 | https://dcblueprint.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
business_case_figures Data-centre business-case figures for one market ~299
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A business-case market, e.g. "Frankfurt", "Milan". |
No output schema declared.
No examples provided.
data_centre_market_overview Data-centre market overview (Europe) ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | A country or metro name, e.g. "Frankfurt", "Ireland", "the Netherlands". |
No output schema declared.
No examples provided.
data_centre_rules Data-centre rules and deadlines by country ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | A European country, e.g. "Germany". |
No output schema declared.
No examples provided.
grid_carbon_and_price_now Grid carbon intensity and power price now ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Optional market, e.g. "France". Leave out for the ranking. |
No output schema declared.
No examples provided.
grid_connection_status Grid connection status for data centres (Europe) ~107
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".
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional European country, e.g. "Germany". Leave out for every country. |
No output schema declared.
No examples provided.
search_dcblueprint Search DC Blueprint ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "PUE benchmarks", "fibre latency London Frankfurt". |
No output schema declared.
No examples provided.
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.
remote · dcblueprint.com
claude mcp add --transport http com-dcblueprint-data-centres 'https://dcblueprint.com/mcp'
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.