_ registry / mcp http-sse · checked 8h ago

ai-buildout-permits

https://aibuildoutpermits.vercel.app

Registry code: 4f496a2ad8dfc0c2

api record

AI Buildout Permits is a ledger of US data-center projects built only from public records: Texas Comptroller data-center

certifications (owner, occupant = tenant, operator), Virginia DEQ and EPA ICIS-Air air-permit records, Minnesota

endpoint
https://aibuildoutpermits.vercel.app/mcp
protocol
http-sse ·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 ai-buildout-permits live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is ai-buildout-permits free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does ai-buildout-permits have?
7 tools: company_exposure, whats_new, project_detail, export, find_projects, equipment_tracker, pipeline_series.
Is ai-buildout-permits 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
100%

90 days 100%· all time 100%

latency
204ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 7 tools
1 open2 auth-required 4 never probed 3 of 7 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.

  • find_projects open 8h ago

    Searches US data-center projects in the public record by state, county, city, tenant (Texas occupant), operator or permittee, any named party, ticker, status, on-site gas generation, source or name. Each row gives status, tenant, operator, resolved tickers, private parents, stated on-site MW, the record link and a page link, plus the true total of matches. Example questions: - "Which Texas data centers list Amazon as the tenant?" - "Planned data centers in Loudoun County with air permits" - "Data-center campuses with on-site gas turbines"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1
        },
        "party": {
          "type": "string",
          "description": "Any named party in any role."
        },
        "query": {
          "type": "string",
          "description": "Words in the project name."
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter US state code, e.g. TX, VA, OH."
        },
        "county": {
          "type": "string"
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0
        },
        "source": {
          "enum": [
            "tx_comptroller",
            "va_deq",
            "epa_echo",
            "mn_deed",
            "eia860m",
            "permit_docs",
            "legistar"
          ],
          "type": "string"
        },
        "status": {
          "enum": [
            "certified",
            "proposed",
            "permitted",
            "under_construction",
            "operating",
            "closed"
          ],
          "type": "string"
        },
        "tenant": {
          "type": "string",
          "description": "Occupant named on a certification (Texas), e.g. 'Anthropic', 'Amazon'."
        },
        "ticker": {
          "type": "string",
          "description": "A resolved ticker, e.g. AMZN, ORCL, CRWV."
        },
        "operator": {
          "type": "string",
          "description": "Operator, owner or permittee name, e.g. 'Microsoft', 'Vantage'."
        },
        "onsite_gas": {
          "type": "boolean",
          "description": "True: only projects whose records show on-site generation."
        },
        "include_jurisdictions": {
          "type": "boolean",
          "description": "Also return city/county agenda records (Legistar)."
        }
      }
    }
    arguments 79 lines
  • equipment_tracker auth-required 8h ago

    On-site generation at data-center campuses as the records state it: turbine or engine maker, model, unit count, unit and total MW, status and planned online date, each with its quoted source line; summarized by maker and model. Rows whose record names no maker say so. Requires a subscription. Example questions: - "Which turbine makers appear in data-center air permits?" - "How many Siemens SGT-800s are permitted?" - "Planned gas generation at data-center campuses in Texas"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "maker": {
          "type": "string",
          "description": "e.g. GE Vernova, Siemens Energy, Mitsubishi, Caterpillar, Bloom."
        },
        "model": {
          "type": "string",
          "description": "e.g. 7HA.02, SGT-800, FT8."
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter US state code, e.g. TX, VA, OH."
        },
        "technology": {
          "type": "string",
          "description": "e.g. gas turbine, reciprocating engine, fuel cell, combined cycle."
        }
      }
    }
    arguments 24 lines
  • pipeline_series auth-required 8h ago

    Counts of data-center events or projects over time (by month, quarter or year), grouped by state, ticker, event type or source, dated by the record's own date or by first-seen date. Requires a subscription. Example questions: - "Texas data-center certifications per quarter since 2023" - "Monthly moratorium and rezoning items by state this year" - "Certifications by tenant ticker per year"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "from": {
          "type": "string",
          "description": "ISO date to start from."
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter US state code, e.g. TX, VA, OH."
        },
        "measure": {
          "enum": [
            "events",
            "projects"
          ],
          "type": "string"
        },
        "group_by": {
          "enum": [
            "state",
            "ticker",
            "event_type",
            "source"
          ],
          "type": "string"
        },
        "interval": {
          "enum": [
            "month",
            "quarter",
            "year"
          ],
          "type": "string"
        },
        "date_basis": {
          "enum": [
            "record",
            "first_seen"
          ],
          "type": "string"
        },
        "event_type": {
          "enum": [
            "certified",
            "air_permit",
            "rezoning",
            "moratorium",
            "abatement",
            "land_use",
            "generator",
            "changes",
            "withdrawn"
          ],
          "type": "string"
        }
      }
    }
    arguments 61 lines
  • company_exposure unknown never probed

    Every data-center project in the ledger that resolves to one ticker or company, in any role (tenant, operator, owner, permittee, equipment maker): status, place, first record date, first-seen date, stated on-site MW, plus counts by role, state and first-record year, and the link methods used. Requires a subscription. Example questions: - "Which data-center projects resolve to ORCL, and since when?" - "How many Texas certifications name Amazon by year?" - "Where does Anthropic show up as a tenant?"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "ticker_or_company"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 300,
          "minimum": 1
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0
        },
        "ticker_or_company": {
          "type": "string",
          "minLength": 1,
          "description": "A ticker (AMZN, CRWV, 9432.T) or a company name (Anthropic, Vantage)."
        }
      }
    }
    arguments 24 lines
  • whats_new unknown never probed

    Dated events on US data-center projects, newest first: Texas certifications, air-permit filings and listings, planned on-site generators, rezonings, moratoria, abatements and other city/county agenda items, and changes this ledger detected (status, tenant, delisting). Each event has its project, place, tenant or operator, tickers, the record link and a project page link. Returns the true total. Example questions: - "What data centers got certified in Texas this month?" - "Which counties voted on data-center moratoria lately?" - "Any new data-center air permits in Virginia?"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Rows per page with a subscription (max 200)."
        },
        "since": {
          "type": "string",
          "description": "ISO date (YYYY-MM-DD). Default: 30 days ago."
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter US state code, e.g. TX, VA, OH."
        },
        "offset": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 0
        },
        "event_type": {
          "enum": [
            "certified",
            "air_permit",
            "rezoning",
            "moratorium",
            "abatement",
            "land_use",
            "generator",
            "changes",
            "withdrawn"
          ],
          "type": "string",
          "description": "certified, air_permit, rezoning, moratorium, abatement, land_use (any agenda item), generator, changes, withdrawn."
        }
      }
    }
    arguments 42 lines
  • project_detail unknown never probed

    One data-center project in full: every named party and role with its ticker link (parent, method, confidence, evidence), on-site power (technology, maker, model, unit count, MW, with the quoted source line), the dated timeline of records, coordinates where stated, and each source's publisher, URL, retrieval time and file hash. Takes a project id from another tool, or a name. Example questions: - "Who is behind Cipher's Barber Lake site?" - "What turbines are permitted at Project Matador?" - "Show the record for TX4"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "project"
      ],
      "properties": {
        "project": {
          "type": "string",
          "minLength": 2,
          "description": "Project id (e.g. tx-dc046706) or a name."
        }
      }
    }
    arguments 14 lines
  • export unknown never probed

    A download link (valid 24 hours) for ledger rows with record dates, first-seen dates and source hashes: a CSV of events filtered by state, ticker, event type, start date or project, or the full ledger as Parquet files (events, projects, and every value each field has held with the days it was first and last seen). Requires a subscription. Example questions: - "Export every Texas certification with first-seen dates as CSV" - "Give me the full ledger as Parquet for a backtest"

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "since": {
          "type": "string"
        },
        "state": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "Two-letter US state code, e.g. TX, VA, OH."
        },
        "format": {
          "enum": [
            "csv",
            "parquet"
          ],
          "type": "string"
        },
        "ticker": {
          "type": "string"
        },
        "project": {
          "type": "string"
        },
        "event_type": {
          "enum": [
            "certified",
            "air_permit",
            "rezoning",
            "moratorium",
            "abatement",
            "land_use",
            "generator",
            "changes",
            "withdrawn"
          ],
          "type": "string"
        }
      }
    }
    arguments 42 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 4f496a2ad8dfc0c2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4f496a2ad8dfc0c2/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/4f496a2ad8dfc0c2/badge.svg)](https://brick.blue/agent/4f496a2ad8dfc0c2?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.