MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
Nothing to run from here
Osint is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
66
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
US ISO interconnection queues and cited energy data. 25 free queries, then $49/mo or $490/yr.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http api-exascale-build-osint-mcp https://api.exascale.build/mcp
# 2 — ask your agent for something these tools do
# list_capabilities_v1, get_source_evidence_v1, describe_capability_v1 and 63 more
Osint costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AEAll 1 server
api.exascale.build1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http api-exascale-build-osint-mcp https://api.exascale.build/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
66 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List available exascale.build data capabilities for agent discovery before querying. Also call this BEFORE stating that a capability is not available — client tool lists are cached and this surface grows; anything listed here is reachable via query_capability_v1 even if your tool list predates it.
No parameter schema on file.
Fetch and hash-verify the raw source row behind a returned citation. Pass a citation object inside params. Two ready-to-pass shapes come straight from the query tools: each aggregate row's citations[ref].verify object, or a detail record's citation (from include_records). Either proves the number with no re-query. The tool verifies the raw workbook SHA-256 before returning source-header row
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe any served capability by name — the generic twin of the named describe tools. Pass capability as either a capability id from list_capabilities_v1 (e.g. "power.capacity") or a query primitive name (e.g. "query_power_capacity_v1"). Returns the same schema payload as the named describe tool: valid filters, groupings, metrics, detail fields, and citation fields. Use the generic pair (this
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability | string | yes | — |
Query any served capability by name — the generic twin of the named query tools, reaching every capability including ones newer than your client's cached tool list. Pass capability as either a capability id from list_capabilities_v1 (e.g. "power.price_ercot") or a query primitive name (e.g. "query_power_price_ercot_v1"), and params as the same flat JSON object the named query tool accepts — c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability | string | yes | — |
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.capacity.
No parameter schema on file.
Query verified U.S. generator-level operating, planned, retired, or canceled power capacity from EIA-860M. Use this for capacity questions by state/jurisdiction, county FIPS, source-reported balancing authority code, fuel, prime mover, technology, lifecycle, or year. Pass filters inside the params object. The operating/planned/retired/canceled selector is lifecycle (e.g. `lifecycle: "operatin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, atoms, metrics, detail fields, and citation fields for power.generation.
No parameter schema on file.
Query verified U.S. monthly net electricity generation (MWh) from EIA-923. Use this for "how much was generated" questions by state, source-reported balancing authority code, fuel, prime mover, sector, plant, or generator, for a given month. For a fuel total or a fuel mix (e.g. "coal generation", "top fuels"), filter or group by fuel_group — it sums the several energy_source_code values a fuel
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe annual EIA-860 ownership filters, convention, metrics, and exact-cell citations.
No parameter schema on file.
Query verified annual EIA-860 generator ownership. Returns the Owner schedule's raw owner names and ownership shares for each eia_plant_id + generator_id. percent_owned is the workbook's raw fraction of one (0.6 = 60%), not a whole-number percent. Filter by plant, generator, exact raw owner name, state, owner state, annual vintage, or source-reported balancing authority code; `{"state":"TX"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe EIA-923 receipt/cost filters, raw units, missing semantics, and exact-cell citations.
No parameter schema on file.
Query verified raw EIA-923 fuel receipts and delivered fuel costs. Returns one Page 5 Fuel Receipts and Costs row per published receipt: plant/month, fuel, supplier, purchase type, source physical quantity, and delivered cost in EIA's stated cents/MMBtu. Filter by plant, month/range, exact source strings, state, fuel, cost status, or source-reported balancing authority code; `{"state":"TX","balan
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe native-XBRL Form 1 plant-cost facts, units, coverage, and exact-fact citations.
No parameter schema on file.
Query accepted native-XBRL FERC Form 1 large-steam plant facts. Returns one separately cited XBRL fact per respondent, report year, raw plant name, and source concept: installed capacity, net generation, plant-cost balance items, fuel expense, and individual operation and maintenance lines. Values and units are as filed; nominal dollars are not adjusted, allocated, divided by generation, or combi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe the EIA Henry Hub and state electric-power gas-price atoms, units, aggregate grain, missingness, vintages, and citations.
No parameter schema on file.
Query verified EIA natural-gas price records from two public series. atom="henry_hub_daily_spot" returns one trading-day Henry Hub spot price in EIA's published $/MMBtu unit (series RNGWHHD). atom="state_electric_power_monthly" returns one state-month average price paid by electric-power consumers in EIA's published $/Mcf unit; {"atom":"state_electric_power_monthly","state":"TX"} is the Tex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.demand.
No parameter schema on file.
Query verified U.S. hourly electricity demand (MW) by balancing authority from EIA-930. Use this for "how much load" questions at the hourly balancing-authority grain: filter or group by balancing_authority_code, region, data_date (or the data_date_from/data_date_to range), hour_number, datetime_utc, or is_imputed. Pass filters inside the params object. Returns JSON aggregates w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.demand_rollup.
No parameter schema on file.
Query verified U.S. hourly electricity demand (MW) as EIA's own published national and regional totals from the EIA Grid Monitor (region-data). Use this for "how much load for the whole country, or a region" questions. Filter by respondent (US48 = the Lower-48 national total, or one of the 13 EIA regions — CAL, CAR, CENT, FLA, MIDA, MIDW, NE, NW, NY, SE, SW, TEN, TEX), data_date (one day) or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.retail_sales.
No parameter schema on file.
Query verified U.S. annual retail electricity sales — billed MWh, revenue, and customer counts — by utility, state, and customer sector from EIA-861. Use this for "who sold how much power to whom" questions at the annual utility×state×sector grain: filter or group by data_year, state, sector (residential / commercial / industrial / transportation), part, service_type, ownership, `ba_c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue.
No parameter schema on file.
Query the MISO generator interconnection queue — the public waiting line of projects that have REQUESTED to connect to the MISO grid (the 15-state Midwest/South footprint). Returns cited, project-level records: requested megawatts (net summer / net winter), location (state, county, derived county_fips), fuel and technology as MISO reports them, three independent status dimensions (`applicat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_pjm.
No parameter schema on file.
Query the PJM New Services (interconnection) queue — the public waiting line of projects that have REQUESTED to connect to the PJM grid (the mid-Atlantic RTO incl. Northern Virginia, PA, NJ, MD, OH, VA, WV and more). Returns cited, project-level records with PJM's full published structure: requested megawatts (requested_max_output_mw = MFO, requested_summer_mw = MW Capacity / summer net, `req
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_pjm_cycle.
No parameter schema on file.
Query PJM's cluster/cycle service-request grid — the cluster view of PJM's interconnection process: the TC1/TC2 transition cycles (re-processing the pre-Order-2023 serial backlog) and the reopened steady-state cycles (C01+, the new intake). A SEPARATE PJM publication from the full New Services queue (query_power_interconnection_queue_pjm_v1) — richer per-project cluster detail; the two share rows
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_caiso.
No parameter schema on file.
Query the CAISO generator interconnection queue — California ISO's public Public Queue Report, the waiting line of projects that have REQUESTED to connect to the CAISO grid (California, plus the out-of-state edges it studies: NV, AZ). Returns cited, project-level records with CAISO's full published structure: the net megawatts to grid (net_mw_to_grid, CAISO's own headline figure) and the per-co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_nyiso.
No parameter schema on file.
Query the NYISO generator + load interconnection queue — New York ISO's public waiting line of projects that have REQUESTED to connect to the New York grid. Uniquely among ISOs, NYISO publishes a Load Projects tab — load interconnection requests (large-load demand), served as-reported — and since its 2026-07 edition tags each load request with its own End-Use class (end_use, e.g. DAT / DAT-AI
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_isone.
No parameter schema on file.
Query the ISO-NE generator interconnection queue — ISO New England's public IRTT "public queue" report, the waiting line of projects that have REQUESTED to connect to the New England grid (CT, MA, ME, NH, RI, VT). Returns cited, project-level records with ISO-NE's full published structure (all 31 columns of the rendered report): the three megawatt readings kept SEPARATE (net_mw, summer_mw = m
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_ercot.
No parameter schema on file.
Query the ERCOT generator interconnection queue — ERCOT's public GIS Report (EMIL PG7-200-ER), the waiting line of generation projects that have REQUESTED to connect to the ERCOT (Texas) grid. Returns cited, project-level records with ERCOT's full published structure across four lifecycle sheets (Large Gen + Small Gen = active; Inactive Projects; Cancellation Update): the requested capacity_mw
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.interconnection_queue_spp.
No parameter schema on file.
Query the SPP generator interconnection queue — Southwest Power Pool's public GI Summary report, the waiting line of generation projects that have REQUESTED to connect to the SPP grid (the ~14-state central-US RTO: OK, KS, TX panhandle, NE, NM, MO, CO, ND, SD, AR, LA and more). Returns cited, project-level records with SPP's full published structure: the requested capacity_mw (SPP's headline `C
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for power.price_ercot.
No parameter schema on file.
Query verified ERCOT wholesale electricity prices — ERCOT's Day-Ahead Market Settlement Point Prices ($/MWh, EMIL NP4-190-CD), the price cleared the day before each operating day at every ERCOT (Texas) settlement point, served hourly. Returns cited prices for each (settlement_point, delivery_date, hour_ending): the per-hour price_usd_per_mwh in detail records, plus avg_price_usd_per_mwh
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe PJM ELCC document identities, class dimensions, metrics, and citations.
No parameter schema on file.
Query cited PJM marginal ELCC class ratings by document kind, auction, delivery year, and resource class. Preliminary, final, and incremental-auction documents remain separate; no value is preferred or reconciled. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe PJM RPM delivery-year/LDA filters, UCAP metrics, and citations.
No parameter schema on file.
Query cited PJM Base Residual Auction UCAP clearing prices, RTO cleared MW, reliability requirement, and published administrative price collar by delivery year and LDA. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe MISO accreditation document kinds, resource classes, ratios, suppressions, and citations.
No parameter schema on file.
Query cited MISO Schedule 53 class-average and indicative-DLOL seasonal accreditation ratios, including published unit counts, storage variants, and explicit suppression atoms. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe MISO PRA planning-year, season, zone, parameter, and citation fields.
No parameter schema on file.
Query cited MISO Planning Resource Auction seasonal zonal ACP, verbatim ERZ values, published CONE parameters, and IMM conduct thresholds. Requires an API key ($49/mo or $490/yr, 7-day full refund, at https://exascale.build/pro) while the source's redistribution terms are under review. This data point is not included in the 25 free queries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.construction.
No parameter schema on file.
Query verified U.S. private construction spending ($ millions) for data centers and semiconductor/computer-electronics manufacturing plants, from the U.S. Census Bureau's Value of Construction Put in Place (C30). Use this for "how much is being spent BUILDING data centers (or chip fabs) in the US" questions — the construction buildout in dollars, not capacity or investment. Filter by category (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.trade.
No parameter schema on file.
Query verified U.S. monthly IMPORTS of integrated circuits (HS-8542) — customs value (USD) by country of origin — from the U.S. Census Bureau's International Trade data. Use this for "how much $ of chips did the US import (from Taiwan / South Korea / in total) and how is it trending" questions. HS-8542 is ALL integrated circuits (processors, memory, amplifiers, parts) — NOT AI-accelerator / GPU-s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.equipment_trade.
No parameter schema on file.
Query verified U.S. monthly IMPORTS of semiconductor-manufacturing EQUIPMENT (HS-8486) — customs value (USD) by country of origin — from the U.S. Census Bureau's International Trade data. Use this for "is the fab buildout actually tooling up, and who supplies the machines" questions — the equipment leg of the fab lifecycle: construction spending (ai_infrastructure.construction) measures the shell
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for ai_infrastructure.production.
No parameter schema on file.
Query verified U.S. semiconductor & electronic-component PRODUCTION and CAPACITY UTILIZATION — the Federal Reserve's monthly G.17 industrial-production index (2017=100) and capacity-utilization rate (percent) for NAICS 3344 — from the Board's own release, history to 1972. Use this for "are the domestic fabs actually producing / how hot are they running" questions — the OUTPUT leg of the fab lifec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.trade.
No parameter schema on file.
Query verified U.S. monthly IMPORTS of INDUSTRIAL ROBOTS — customs value (USD) AND unit counts (number of robots) — by country of origin, from the U.S. Census Bureau's International Trade data. Use this for "how many robots is the US importing, from whom, and what are they worth" questions — the only high-frequency official U.S. robotics series. Covers the nomenclature's two robot-specific HS-10
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for robotics.adoption.
No parameter schema on file.
Query the verified share of US manufacturing plants USING industrial robots — plus workers exposed and robotics capex — from the Census Industrial Robotic Equipment product (the first official federal robotics-adoption statistics). Use this for "are factories actually adopting robots" questions — the INSTALLED-BASE reading the import data cannot see. Serves the percent of plants with robots and t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for space.satellite_filings.
No parameter schema on file.
Query the verified FCC satellite licensing docket — every space-station (SAT) filing in the FCC's own daily IBFS database dump, back to the 1960s — by applicant, application type, status, and filing date. Use this for "who is authorized to operate what in orbit, what has been filed, and where does each filing stand" questions — the satellite-buildout licensing pipeline. Each filing carries the FC
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe valid filters, groupings, metrics, detail fields, and citation fields for space.satellite_notices.
No parameter schema on file.
Query the FCC Space Bureau's weekly satellite public notices since the ICFS cutover (2025-06-18) — every satellite application the FCC accepted for filing and every action it took (grants, partial grants, dismissals, surrenders), as printed. Use this for "what satellite filings has the FCC received or acted on since mid-2025" questions — the current licensing pipeline, which the pre-cutover docke
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Describe capacity factor: net generation / (operating nameplate × hours), joined across EIA-860M and EIA-923.
No parameter schema on file.
Query verified U.S. capacity factor — how hard a fleet actually runs — by joining EIA-860M capacity and EIA-923 generation. Requires data_month: one ISO month start, e.g. "2026-01-01". If the user names no month, ask which one (or state the month you chose); if a month is not covered, the error lists the months that are — do not retry blindly. capacity_factor = net generation (MWh) / (operatin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| params | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Osint or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.7.
1.1.7
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Osint can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.