Scrutica

Free, no API key.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Scrutica Search: Search facilities, companies, or sovereign programs by free-text query. Returns ranked results with id, name, type, one-line summary, and Scrutica URL. Filter by entity_type to scope
  • Scrutica Get Facility: Fetch complete details for a single Scrutica facility by canonical ID. Returns: operator, owner, country, power capacity (MW), GPU inventory (where disclosed), location (lat/lng
  • Scrutica Get Company: Fetch complete details for a single organization (company, government entity, holding company) by canonical Scrutica ID. Returns: legal name, country of HQ, organization type, pa

What data it sees

Do you need an account

No: the server works without sign-in

Free, no API key. AI compute infrastructure for governance research: 4,573 compute facilities, ~19K supply-chain relationships, BIS Entity List and OFAC designations, 36 sovereign AI programmes (announced vs disbursed), scenario stress tests and FLOP estimation with bounds. Every record carries data_source, source_url and is_estimated.

10 read-only tools: search, facility and company records, supply-chain traversal, export-control lookup, Entity List change log, sovereign programmes, scenarios, FLOP estimation, methodology.

Docs: https://scrutica.com/agents · Agent guide: https://scrutica.com/api/mcp/llms.txt · Data licence: CC BY-SA 4.0 (see /agents for the licensed-corpora carve-out).

How to connect

How to connect Scrutica to Claude

The server address to paste into Claude settings:

https://scrutica--davidgringras.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Scrutica to ChatGPT

The server address to paste into ChatGPT settings:

https://scrutica--davidgringras.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Scrutica to Cursor

The server address to paste into Cursor settings:

https://scrutica--davidgringras.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (9)

Raw names from tools/list. Only developers need these.

scrutica_searchSearch facilities, companies, or sovereign programs by free-text query. Returns ranked results with id, name, type, one-line summary, and Scrutica URL. Filter by entity_type to scope to a single class. Filter by ISO 3166-1 alpha-2 country code. Do NOT use this for BIS Entity List / export-control lookups — use scrutica_query_export_controls. Do NOT use this for supply-chain traversal — resolve an entity ID first via this tool, then call scrutica_get_supply_chain.
scrutica_get_facilityFetch complete details for a single Scrutica facility by canonical ID. Returns: operator, owner, country, power capacity (MW), GPU inventory (where disclosed), location (lat/lng), facility type, status, data_source, source_url, is_estimated flags, data quality flags, BIS Entity List exposure via the ownership chain. Resolve facility IDs first via scrutica_search.
scrutica_get_companyFetch complete details for a single organization (company, government entity, holding company) by canonical Scrutica ID. Returns: legal name, country of HQ, organization type, parent / subsidiary references, supply-chain edge counts. Use scrutica_query_export_controls for BIS designation details. Use scrutica_get_supply_chain for full edge graphs.
scrutica_query_export_controlsLook up BIS Entity List, OFAC SDN, and Wassenaar Arrangement CCL designations for companies or countries. Fuzzy matches entity_name against organization_aliases. Returns designation_date, jurisdiction, control_reason, source_url (Federal Register anchor). Authority tier: Federal-Register-anchored designations are Tier 1 (primary source).
scrutica_get_supply_chainReturn supply-chain relationships for one or more organizations. direction = 'upstream' traces suppliers (who feeds this entity); 'downstream' traces customers (who depends on this entity); 'both' returns both. Each edge: source_org_id, target_org_id, relationship_type, supply_share (where disclosed), factset_price_correlation (3-month rolling, where available), data_source. Dataset: ~18,600 edges from FactSet Revere + WRDS + SEC Exhibit 21.
scrutica_get_sovereign_programFetch detailed data on a national sovereign AI compute program. Returns: announced_usd, announced_govt_only_usd, committed_usd, disbursed_usd, reality_ratio, status, key_partners, governance_reach, NVIDIA/US dependency, source_count. 'list_all' returns a summary table of all tracked programs for cross-country comparison.
scrutica_get_scenarioFetch geopolitical compute risk scenarios. Available: 'taiwan-strait' (4 TSMC disruption scenarios), 'iran-threat' (IRGC missile range vs Gulf compute), 'tokyo-earthquake' (Japan memory-fab exposure), 'south-china-sea' (submarine cable severing), 'abqaiq-2' (Saudi grid). Returns scenario summary with key assumptions, affected facilities, recovery timeline, and source citations.
scrutica_estimate_flopsCompute peak BF16 FLOP estimates for a hardware configuration. Returns point estimate + bounds. Methodology matches the Interactive Methodology Explorer at /methodology#flop-estimation. Do NOT present outputs as exact measurements — always relay the bounds and the is_estimated flag.
scrutica_get_methodologyReturn methodology documentation for a Scrutica metric or index. Topics: 'flop-estimation', 'cost-index', 'compute-visibility-index', 'supply-chain-weighting', 'chokepoint-cascade', 'sovereign-execution-classification'. Returns the canonical URL + section anchor + summary. Use this when a user asks "how did you calculate X".