Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Data Center Index

REMOTE · DATACENTERINDEX.AI

AI infrastructure tracker: data center campuses, power projects, MW and the companies behind them

+8 this week 84 Trust /100

Last scanned (20 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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 Security74
  • 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. 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 987 tokens (~123/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +61
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: 46% → 100% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: good → excellent functional
    • “get_company” reworded the description of “ticker” cosmetic
    • “get_movers” reworded the description of “limit” cosmetic
    • “get_project” reworded the description of “slug” cosmetic
    • “list_companies” reworded the description of “sector” cosmetic
    • “recent_changes” reworded the description of “days” cosmetic
    • “recent_changes” reworded the description of “limit” cosmetic
    • “search_projects” reworded the description of “developer” cosmetic
    • “search_projects” reworded the description of “limit” cosmetic
    • “search_projects” reworded the description of “min_mw” cosmetic
    • “search_projects” reworded the description of “query” cosmetic
    • “search_projects” reworded the description of “status” cosmetic
    • Tool “get_company” changed its title: Get one public company cosmetic
    • Tool “get_market” changed its title: Get one US state market cosmetic
    • Tool “get_movers” changed its title: Get biggest stock moves cosmetic
    • Tool “get_project” changed its title: Get one data center project cosmetic
    • Tool “list_companies” changed its title: List tracked public companies cosmetic
    • Tool “list_markets” changed its title: List US state markets cosmetic
    • Tool “recent_changes” changed its title: Get recent directory changes cosmetic
    • Tool “search_projects” changed its title: Search data center projects cosmetic
  • 20 Nov 26 −53
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Probed https://datacenterindex.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=datacenterindex.ai CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA256 a1d5f9380eca30ff0e2d3e3782bdaf8c
SANs: datacenterindex.ai, *.datacenterindex.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of datacenterindex.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
datacenterindex.ai. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://datacenterindex.ai/mcp Verified 200
http (plaintext) http://datacenterindex.ai/mcp HTTPS enforced 301 https://datacenterindex.ai/mcp
MCP tools · 8 exposed · ~615 tokens

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 →

Tool Tokens
get_company ~56

One public company by ticker: description, data-center exposure, market cap, and the tracked projects it is linked to.

NameTypeReqDescription
tickerstringyesStock ticker, any case, e.g. "VRT" or "nvda"

No output schema declared.

No examples provided.

get_market ~53

One US state market: summary description, counts, the tracked projects, and the public companies exposed to it.

NameTypeReqDescription
statestringyesState name or two-letter code, e.g. "Ohio" or "OH"

No output schema declared.

No examples provided.

get_movers ~54

Biggest day and week stock moves across the tracked universe (latest close).

NameTypeReqDescription
limitinteger–How many companies to return, ranked by the size of the day move, 1 to 50 (default 10)

No output schema declared.

No examples provided.

get_project ~65

One tracked project by slug (the last path segment of a datacenterindex.ai/projects/... URL), with its linked public companies.

NameTypeReqDescription
slugstringyesProject slug from search_projects or a datacenterindex.ai/projects/<slug> URL, e.g. "meta-aiken"

No output schema declared.

No examples provided.

list_companies ~84

Public companies in the tracked supply-chain universe with sector, data-center revenue exposure and project count.

NameTypeReqDescription
sectorstring–Exact sector slug: power_equipment, cooling, networking, energy, construction, dc_operator, hyperscaler, ai_lab, gpu_cloud, semiconductor, chip_fab, fab_equipment, it_hardware or space. Omit for ever…

No output schema declared.

No examples provided.

list_markets ~30

Every US state market with tracked projects: counts by status, pipeline MW, grid operator, page URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recent_changes ~77

What changed in the tracker recently: new projects, status changes, capacity revisions. The single source for "what is new".

NameTypeReqDescription
daysinteger–Look-back window in days, 1 to 90 (default 7)
limitinteger–How many changes to return, 1 to 100 (default 25)

No output schema declared.

No examples provided.

search_projects ~196

Search tracked data center projects. Filter by free-text query (name, developer, tenant, city), US state code, status, developer, or minimum MW. Returns up to 50 rows sorted by capacity.

NameTypeReqDescription
developerstring–Developer or operator name, partial match, e.g. "Meta" or "QTS"
limitinteger–How many projects to return, 1 to 50 (default 20)
min_mwnumber–Minimum capacity in MW, e.g. 500
querystring–Free text matched against name, developer, tenant and city, e.g. "Stargate" or "Abilene"
statestring–Two-letter US state code, e.g. TX
statusstring–Campus status. Use under_construction for what is being built (operational campuses with expanding: true are also adding buildings)

No output schema declared.

No examples provided.

Install

How do I install the Data Center Index MCP server?

Data Center Index is a hosted endpoint at https://datacenterindex.ai/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 · datacenterindex.ai

# add to Claude Code
claude mcp add --transport http ai-datacenterindex-datacenterindex 'https://datacenterindex.ai/mcp'
Common questions

What is the Data Center Index MCP server?

Data Center Index is an MCP server listed in the public MCP registry as ai.datacenterindex/datacenterindex. AI infrastructure tracker: data center campuses, power projects, MW and the companies behind them. This page covers its hosted endpoint (https://datacenterindex.ai/mcp).

Is the Data Center Index MCP server safe to use?

Data Center Index scores 84 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 Data Center Index MCP server expose?

Data Center Index exposes 8 tools: search_projects, get_project, list_markets, get_market, list_companies, and 3 more. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

Does the Data Center Index MCP server require authentication?

No. We connected to Data Center Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Data Center Index MCP server still maintained?

Data Center Index is still listed as active in the MCP registry. We last reached this channel on 21 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 Data Center Index MCP server?

VerifyMCP ran 13 checks on Data Center Index, 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.