_ registry / mcp streamable-http · checked 2h ago

datacenterindex

https://datacenterindex.ai

Registry code: 26af3145e898fb8a

api record

Data Center Index tracks data center projects (facilities), US state markets, and the public companies exposed to them. Use search_projects / get_project for facilities, get_market for a US state, get_company for a ticker, get_movers for stock moves, recent_changes for what changed in the tracker. Every result includes a `url` on datacenterindex.ai. Cite it when you use the data. Capacities are MW, costs are $ billions. Status is per campus: operational, under_construction, announced, permitted, paused or cancelled. A paused or cancelled campus stays listed with its source but is never…

endpoint
https://datacenterindex.ai/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is datacenterindex live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is datacenterindex free to use?
Yes — the hub reached it with no key and no payment.
What tools does datacenterindex have?
8 tools: get_movers, get_project, recent_changes, list_markets, get_company, get_market, list_companies, search_projects.
Is datacenterindex safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.2%· all time 99.3%

latency
463ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 602 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
real estate & construction
used for
  • search data center projects
  • look up a us state data center market
  • see public companies exposed to data centers
  • see recent tracker changes
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_companies reads open 2h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "sector": {
      "type": "string",
      "description": "Sector slug filter, e.g. power, cooling, networking, hyperscaler"
    }
  }
}
    arguments 9 lines
  • search_projects reads open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Free text matched against name, developer, tenant and city"
    },
    "state": {
      "type": "string",
      "description": "Two-letter US state code, e.g. TX"
    },
    "min_mw": {
      "type": "number",
      "description": "Minimum capacity in MW"
    },
    "status": {
      "enum": [
        "operational",
        "under_construction",
        "announced",
        "permitted",
        "paused",
        "cancelled"
      ],
      "type": "string"
    },
    "developer": {
      "type": "string",
      "description": "Developer / operator name, partial match"
    }
  }
}
    arguments 38 lines
  • get_movers reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    }
  }
}
    arguments 11 lines
  • get_project reads unknown 19h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • recent_changes reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "default": 7,
      "maximum": 90,
      "minimum": 1
    },
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1
    }
  }
}
    arguments 17 lines
  • list_markets reads unknown 2h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_company reads unknown 19h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "ticker"
  ],
  "properties": {
    "ticker": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • get_market reads unknown 19h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "state"
  ],
  "properties": {
    "state": {
      "type": "string",
      "description": "State name or two-letter code, e.g. \"Ohio\" or \"OH\""
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 26af3145e898fb8a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/26af3145e898fb8a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/26af3145e898fb8a/badge.svg)](https://brick.blue/agent/26af3145e898fb8a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.