mcp-registry/ai.datacenterindex/datacenterindex · v1.0.0
As of 2026-10-26 17:27 UTC, the Datacenterindex MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 26.1 hours.
AI infrastructure tracker: data center campuses, power projects, MW and the companies behind them
Point your MCP client at this streamable-http endpoint: https://datacenterindex.ai/mcp
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
7 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.datacenterindex%2Fdatacenterindex/fixes
{
"name": "get_company",
"description": "One public company by ticker: description, data-center exposure, market cap, and the tracked projects it is linked to.",
"inputSchema": {
"type": "object",
"required": [
"ticker"
],
"properties": {
"ticker": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_market",
"description": "One US state market: summary description, counts, the tracked projects, and the public companies exposed to it.",
"inputSchema": {
"type": "object",
"required": [
"state"
],
"properties": {
"state": {
"type": "string",
"description": "State name or two-letter code, e.g. \"Ohio\" or \"OH\""
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_movers",
"description": "Biggest day and week stock moves across the tracked universe (latest close).",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.datacenterindex/datacenterindex"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.datacenterindex/datacenterindex"}) over MCP.
search_projects ~219 tokensrecent_changes ~96 tokensget_market ~88 tokenslist_companies ~87 tokensget_project ~72 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fai.datacenterindex%2Fdatacenterindex?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.datacenterindex%2Fdatacenterindex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.datacenterindex%2Fdatacenterindex.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.datacenterindex%2Fdatacenterindex.svg :target: https://glimind.com/server/mcp-registry%2Fai.datacenterindex%2Fdatacenterindex?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4aca365fb9240fb0…, first seen 2026-10-17, included at leaf 10529 of 74,418. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:27 UTC, the Datacenterindex MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 26.1 hours.
Datacenterindex MCP server advertises 8 tools, including get_company, get_market, get_movers, get_project, list_companies.
Point your MCP client at this streamable-http endpoint: https://datacenterindex.ai/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.