AI Buildout Permits

● Active

io.github.2016judea/ai-buildout-permits

US AI data-center projects from public records: tenants, air permits, turbines, resolved to tickers

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "ai-buildout-permits": {
      "url": "https://aibuildoutpermits.vercel.app/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http ai-buildout-permits https://aibuildoutpermits.vercel.app/mcp
VS Code
code --add-mcp '{"name":"ai-buildout-permits","type":"http","url":"https://aibuildoutpermits.vercel.app/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Legal & Government
Version
0.1.0
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: AI Buildout Permits is maintained, hosted endpoint answering without a key.

Maintained
Active
Last commit today (Nov 21, 2026), 0 open issues.
Official registry
Active
Published as io.github.2016judea/ai-buildout-permits in the official MCP registry, version 0.1.0.
Source
No licence found
Public repository, but GitHub reports no recognised licence (0 stars). Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to aibuildoutpermits.vercel.app: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 07:08 UTCStatus history & uptime →
● Working213 msprotocol 2025-06-18v0.1.0tools

The endpoint answered the MCP handshake as "AI Buildout Permits" and listed 7 tools. Answering since Nov 21, 2026.

Context cost ≈ 2.3k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 7 tools.

Tools (7)

  • whats_new5 params

    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?"

    Show parameters
    • sincestringISO date (YYYY-MM-DD). Default: 30 days ago.
    • statestringTwo-letter US state code, e.g. TX, VA, OH.
    • event_typestringcertified, air_permit, rezoning, moratorium, abatement, land_use (any agenda item), generator, changes, withdrawn.
    • limitintegerRows per page with a subscription (max 200).
    • offsetinteger
  • find_projects14 params

    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"

    Show parameters
    • statestringTwo-letter US state code, e.g. TX, VA, OH.
    • countystring
    • citystring
    • tenantstringOccupant named on a certification (Texas), e.g. 'Anthropic', 'Amazon'.
    • operatorstringOperator, owner or permittee name, e.g. 'Microsoft', 'Vantage'.
    • partystringAny named party in any role.
    • tickerstringA resolved ticker, e.g. AMZN, ORCL, CRWV.
    • statusstring
    • onsite_gasbooleanTrue: only projects whose records show on-site generation.
    • sourcestring
    • querystringWords in the project name.
    • include_jurisdictionsbooleanAlso return city/county agenda records (Legistar).
    • limitinteger
    • offsetinteger
  • project_detail1 param

    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"

    Show parameters
    • projectstringrequiredProject id (e.g. tx-dc046706) or a name.
  • company_exposure3 params

    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?"

    Show parameters
    • ticker_or_companystringrequiredA ticker (AMZN, CRWV, 9432.T) or a company name (Anthropic, Vantage).
    • limitinteger
    • offsetinteger
  • equipment_tracker4 params

    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"

    Show parameters
    • makerstringe.g. GE Vernova, Siemens Energy, Mitsubishi, Caterpillar, Bloom.
    • modelstringe.g. 7HA.02, SGT-800, FT8.
    • technologystringe.g. gas turbine, reciprocating engine, fuel cell, combined cycle.
    • statestringTwo-letter US state code, e.g. TX, VA, OH.
  • pipeline_series7 params

    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"

    Show parameters
    • group_bystring
    • measurestring
    • event_typestring
    • statestringTwo-letter US state code, e.g. TX, VA, OH.
    • fromstringISO date to start from.
    • intervalstring
    • date_basisstring
  • export6 params

    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"

    Show parameters
    • formatstring
    • statestringTwo-letter US state code, e.g. TX, VA, OH.
    • tickerstring
    • event_typestring
    • sincestring
    • projectstring

Checked by Serverdex with a plain initialize + tools/list call to aibuildoutpermits.vercel.app/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 21, 2026
License
—

From the README

AI Buildout Permits Live: https://aibuildoutpermits.vercel.app Every US AI data-center project as a public-record row: who the tenant is, how much power, which turbines, how far along, and which stocks are exposed. Built from state tax certifications, air permits and city and county agendas. Every row links to its source record. Connect • Claude: add the connector from Claude's connector directory, or as a custom connector at https://aibuildoutpermits.vercel.app/mcp • Claude Code: claude mcp add --transport http ai-buildout-permits https://aibuildoutpermits.vercel.app/mcp • Codex, Cursor, VS Code, Python: https://aibuildoutpermits.vercel.app/connect Free: the last 30 days of events, 10 rows per answer, full project detail. Paid ($99/month or $990/year): history with first-seen dates, ticker exposure, the turbine tracker, time series and exports. Pricing: https://aibuildoutpermits.vercel.app/pricing Sample data data/texas-certified-data-centers-tickers.csv: the Texas Comptroller's certified data-center list with each occupant resolved to a ticker where one exists. CC BY 4.0, credit "AI Buildout Permits". The underlying list is public domain (Texas Comptroller of Public Accounts). Support Open an issue in this repository. Privacy: https://aibuildoutpermits.vercel.app/privacy AI Buildout Permits is made by Brick and Mortar AI LLC. Not affiliated with any agency or company named in the data.

Read the full README on GitHub →

Remotes

  • streamable-httphttps://aibuildoutpermits.vercel.app/mcp

The most-starred Legal & Government servers in the index, with their live-check result.

ServerStarsLast pushLive check
Korean Law MCP2,891Nov 2026Working
EdgarTools2,859Nov 2026Local / not checked
Global law2,167Nov 2026Working
MCP Fiscal Brasil433Nov 2026Local / not checked
Legal Data Hunter422Nov 2026Needs sign-in

AI Buildout Permits: questions people ask

Is AI Buildout Permits a remote or a local MCP server?
According to its entry in the official MCP registry, AI Buildout Permits ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does AI Buildout Permits need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is AI Buildout Permits safe to use?
Mostly fine: AI Buildout Permits is maintained, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is AI Buildout Permits still maintained?
Active: the repository's last commit today. Last push Nov 21, 2026, 0 GitHub stars. Read from GitHub on Nov 21, 2026.
What tools does AI Buildout Permits expose?
7 tools as listed by the server itself during the live check, including whats_new, find_projects, project_detail, company_exposure, equipment_tracker. The full list with parameters is in the Live check section above.
How do I add AI Buildout Permits to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Appeal Draft – Twin Cities property tax appealIs my Twin Cities property tax assessment too high? County value vs. recorded sales, when to appeal
  2. Tip & Overtime DeductionsWorks out the no-tax-on-tips and no-tax-on-overtime deductions and W-2 boxes, with the math shown
  3. Breach to Claim: data breach settlementsAm I owed money from a data breach? Open settlements, deadlines, payouts and official claim sites
  4. heistclips – GTA 6 clippingFind clip-worthy moments in Twitch streams from chat spikes; rank clipping campaigns by pay per clip
Browse all Legal & Government →

Add the badge to your site

Show visitors that AI Buildout Permits is listed here — it’s also the link we check for a free listing.

AI Buildout Permits — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-2016judea-ai-buildout-permits?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="AI Buildout Permits — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![AI Buildout Permits — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-2016judea-ai-buildout-permits?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-2016judea-ai-buildout-permits) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-2016judea-ai-buildout-permits) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-2016judea-ai-buildout-permits)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-2016judea-ai-buildout-permits"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-2016judea-ai-buildout-permits"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-2016judea-ai-buildout-permits"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).