scrutica

endpoint

https://scrutica.com/api/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 scrutica live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is scrutica free to use?

Yes — the hub reached it with no key and no payment.

What tools does scrutica have?

10 tools: scrutica_get_company, scrutica_query_export_controls, scrutica_get_supply_chain, scrutica_get_scenario, scrutica_estimate_flops, scrutica_get_methodology, scrutica_search, scrutica_get_facility, ….

Is scrutica 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.

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.

• scrutica_entity_list_changes reads open 23h ago

  What CHANGED in the BIS Entity List, as bounded change-log summaries. Backed by the same derivation the public /export-controls/changes page and its RSS feed render. PREFER this over scrutica_query_export_controls for freshness questions ("what changed this month", "latest additions", "recent removals"): designation rows arrive already grouped into per-Federal-Register-notice change events, so you do not re-derive notice grouping from citation strings. Each event includes: canonical FR citation and link, notice title / publication date / document number where the citation resolved to one FR document, a derived event date labeled with the source column it came from, entry / entity / address / removal counts (entry_count counts entries as the Register does: an entity under two destinations is two entries), per-country counts, a bounded sample of entity names, and the entities cross-referenced to compute-infrastructure organizations. Removal actions are returned separately as date-keyed events — a screening list maintained from additions alone over-blocks forever. Also returns a last-N-ISO-week activity rollup counting BOTH additions and removals. Zero-count weeks are a real quiet-Federal-Register signal, not missing data. Results are bounded summaries, never row dumps: at most 24 events per call (default 6, newest first), with any truncation declared in metadata. Cite totals from the count field and per-event entry_count, never by summing a sampled list. Do NOT use this to look up one entity's designation rows — use scrutica_query_export_controls (substring match on the published name). Use company_id here only to scope the log to notices touching an organization you already resolved. Authority tier: Federal-Register-anchored designations are Tier 1 (primary source). Each entry is dated by the effective date of the Federal Register notice that added it, the notice the Entity List's own eCFR citations for the entry resolve to (a removed record: the notice its entry was dated by while the Register printed it, else its own citation's notice), except where no citation resolves to a notice; the event date is derived (modal designation_date, falling back to modal effective_date) and labeled with its source.

  mcp-tool

  123456789101112131415161718192021222324

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 6,
        "maximum": 24,
        "minimum": 1,
        "description": "Max change events to return (default 6, max 24), newest first. The count field always reports the full total in scope. At the Federal Register's Entity-List cadence the default already reaches back several months."
      },
      "weeks": {
        "type": "integer",
        "default": 8,
        "maximum": 52,
        "minimum": 1,
        "description": "ISO-week span of the activity rollup (default 8 — the change-log page's own window; max 52)."
      },
      "company_id": {
        "type": "string",
        "description": "Scope to change events touching one organization. Canonical Scrutica org ID ('org-<slug>'); the id space is the matched_org_id values in the BIS cross-reference, so designated entities without a compute-substrate cross-reference never appear under a scope. Kept events retain their full entity context."
      }
    }
  }

  arguments 24 lines copy
• scrutica_get_sovereign_program reads open 18h ago

  Fetch 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, NVIDIA/US dependency, source_count, and published_spending (a government's own spending figures, each in its currency against its budget, with the document). 'list_all' returns a summary table of all tracked programs. announced_usd can include private commitments; announced_govt_only_usd records the government-funded portion. Compare the programme sources for scope, dates and currency conversions. A government-only figure can still span a different budget period or initiative from another programme's figure. reality_ratio divides disbursed_usd by announced_govt_only_usd, using announced_usd when the government-only field is null. The ratio is null when disbursement or the denominator is missing, or the denominator is zero. Each row includes reality_ratio_denominator_usd and reality_ratio_denominator_field so the division is reproducible from the payload. Where disbursed_usd converts a government's published spending figure, reality_ratio_basis is native_currency and the ratio divides that figure by its own budget in the source currency (reality_ratio_numerator_native / reality_ratio_denominator_native, in reality_ratio_currency): the two dollar amounts were converted on different dates and do not reproduce it. disbursed_usd derives only from a government's published expenditure or payments; a transfer to an administering body is listed in published_spending as released and is not counted. Missing fields and differing reporting scopes limit comparisons; reality_ratio_unavailable_reason explains an absent ratio.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "country": {
        "type": "string",
        "maxLength": 2,
        "minLength": 2,
        "description": "ISO 3166-1 alpha-2"
      },
      "list_all": {
        "type": "boolean",
        "default": false,
        "description": "Return summary of all sovereign programs instead of a single record"
      },
      "program_id": {
        "type": "string",
        "description": "Scrutica sovereign-program ID in the form 'sovereign-<country_code>' (e.g. 'sovereign-ae'), as returned by scrutica_search and list_all. The bare country_code is also accepted. Regional programs use non-ISO codes ('sovereign-eurohpc', 'sovereign-nato-aukus', 'sovereign-africa-regional') and are reachable ONLY via program_id or list_all — the 2-letter country parameter cannot match them."
      }
    }
  }

  arguments 21 lines copy
• scrutica_get_company reads unknown 23h ago

  Fetch 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. US government listings that are not export controls: us_restrictive_listings holds the rows that name the organization, each with its list (dod_1260h: the Defense Department's Section 1260H list of "Chinese military companies"; ofac_ns_cmic: OFAC's Non-SDN Chinese Military-Industrial Complex Companies List; dhs_fascsa_exclusion: a Homeland Security FASCSA exclusion order), whether it is on the current list, the name as printed, its source (Federal Register notice or OFAC list file) and how it was matched (resolution 'name' or 'alias'; 'ambiguous' when the printed name matches several organizations, which are listed). on_1260h and on_ns_cmic are true when a current row resolves to the organization, false when no current row names it, and null when a current row names it among several organizations (unless the stored flag already reads true) or the rows cannot be read: names that match no record are not resolved, so false is not proof of absence. on_ofac_sdn is always null: OFAC's SDN list is not ingested. Use scrutica_query_export_controls for BIS designation details. Use scrutica_get_supply_chain for full edge graphs.

  mcp-tool

  1234567891011121314151617181920212223242526

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "id": {
        "type": "string",
        "description": "Alias for company_id."
      },
      "org_id": {
        "type": "string",
        "description": "Alias for company_id."
      },
      "entity_id": {
        "type": "string",
        "description": "Alias for company_id."
      },
      "company_id": {
        "type": "string",
        "description": "REQUIRED. Canonical Scrutica organization ID. Format: 'org-<slug>' (e.g. 'org-nvidia', 'org-tsmc', 'org-huawei'). Resolve via scrutica_search first — do NOT guess slugs. Optional in the schema only so the aliases below can stand in; supply exactly one of these."
      },
      "organization_id": {
        "type": "string",
        "description": "Alias for company_id."
      }
    }
  }

  arguments 26 lines copy
• scrutica_query_export_controls reads unknown never probed

  Look up BIS Entity List designations for companies or countries. The queried dataset is the US Commerce Department Entity List, Federal-Register-anchored; it does NOT cover OFAC SDN or Wassenaar CCL (for an organization's Section 1260H, NS-CMIC or FASCSA listing, use scrutica_get_company — its us_restrictive_listings rows and the on_1260h / on_ns_cmic flags derived from them; OFAC's SDN list is not ingested, and on_ofac_sdn is null). entity_name is a case-insensitive substring match against the designated entity's published name (no alias expansion). Returns entity_name, entity_type, country, list_type, designation_date, removal_date, grounds, federal_register_citation, source_url (Federal Register notice URL), data_quality_flags. Provide entity_name or country. entity_id filtering is not implemented: an entity_id-only call is rejected; alongside a supported filter, entity_id is ignored and the response sets entity_id_ignored: true. VEU authorization removals are returned separately in regulatory_events (maximum 50, with count and truncation); they do not contribute to designation membership or counts. Event effective_date and publication_date are distinct. Authority tier: Federal-Register-anchored designations are Tier 1 (primary source). bis_coverage_class discriminates how a row is covered: explicitly_named (FR notice cites the entity by name) vs affiliate_50pct_rule (inferred via BIS's 50% Affiliates Rule). coverage_note is populated only on affiliate_50pct_rule rows and states whether that rule is currently suspended. data_quality_flags is an array of provenance/caveat notes, empty for most rows; where present (derived-country provenance, removal-date sourcing, or the affiliate rows' suspension and substrate-reproducibility caveats) treat it as load-bearing context for the row.

  mcp-tool

  1234567891011121314151617181920212223242526

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 50,
        "minimum": 1
      },
      "country": {
        "type": "string",
        "maxLength": 2,
        "minLength": 2,
        "description": "ISO 3166-1 alpha-2"
      },
      "entity_id": {
        "type": "string",
        "description": "Retained for compatibility; filtering by this ID is not implemented. An ID-only call is rejected; with entity_name or country, the ID is ignored and entity_id_ignored is true."
      },
      "entity_name": {
        "type": "string",
        "description": "Case-insensitive substring of the designated entity's published name; no alias expansion. Supply entity_name or country."
      }
    }
  }

  arguments 26 lines copy
• scrutica_get_supply_chain reads unknown 18h ago

  Return 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 carries supplier_org_id, customer_org_id and data_source; product_service, category, sole-source status, share and criticality appear only where the edge's cited source states them for that pair, and attribute_withholding gives the reason for every withheld value. Collection size: 20,687 supply-chain records across all sources (snapshot 2026-11-03). Of these records, 1,924 come from a licensed layer limited to relationships between organizations already in Scrutica's records.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 25,
        "maximum": 100,
        "minimum": 1
      },
      "org_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        ],
        "description": "Alias for org_ids; a single id may be passed as a bare string."
      },
      "org_ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 5,
        "minItems": 1,
        "description": "REQUIRED. Scrutica org IDs in 'org-<slug>' format (e.g. ['org-nvidia', 'org-tsmc']), 1-5 of them. Optional in the schema only so the single-id aliases below can stand in."
      },
      "direction": {
        "enum": [
          "upstream",
          "downstream",
          "both"
        ],
        "type": "string",
        "default": "both"
      },
      "company_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          }
        ],
        "description": "Alias for org_ids."
      }
    }
  }

  arguments 58 lines copy
• scrutica_get_scenario reads unknown 9h ago

  Fetch 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), 'abqaiq-2' (Saudi grid). Returns the scenario's summary plus its substrate serialized from the interactive page's own data modules — assumption scenarios / threat systems / affected assets with per-item sources and authority tiers, capped lists shipping their true totals. The propagation SIMULATION itself remains interactive-only at the returned URL.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "scenario_id"
    ],
    "properties": {
      "scenario_id": {
        "enum": [
          "taiwan-strait",
          "iran-threat",
          "tokyo-earthquake",
          "abqaiq-2"
        ],
        "type": "string"
      }
    }
  }

  arguments 18 lines copy
• scrutica_estimate_flops reads unknown 18h ago

  Estimate hypothetical peak and sustained throughput for a user-specified hardware configuration and precision. Sustained throughput equals dense peak throughput multiplied by accelerator count and utilization. The reported bounds are fixed at 0.7 and 1.15 times that result; they are model assumptions. Retain the bounds and is_estimated flag when quoting the estimate. This tool does not verify a named facility's inventory, availability or regulatory compliance. Named-facility estimates have separate evidence requirements documented at /methodology#flop-estimation.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "hardware_type",
      "unit_count"
    ],
    "properties": {
      "sparsity": {
        "enum": [
          "dense",
          "2:4"
        ],
        "type": "string",
        "default": "dense",
        "description": "Structured-sparsity mode, accepted and echoed in the response. Both values currently apply a 1.0 multiplier."
      },
      "precision": {
        "enum": [
          "fp16",
          "bf16",
          "fp8",
          "int8"
        ],
        "type": "string",
        "default": "bf16"
      },
      "unit_count": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 1,
        "description": "Number of accelerators"
      },
      "utilization": {
        "type": "number",
        "default": 0.4,
        "maximum": 1,
        "minimum": 0,
        "description": "Fraction of dense peak throughput sustained (0–1; default 0.40)."
      },
      "hardware_type": {
        "enum": [
          "H100-SXM5",
          "H200",
          "B100",
          "B200",
          "A100-80GB",
          "MI300X",
          "TPU-v5p"
        ],
        "type": "string",
        "description": "GPU / accelerator model"
      }
    }
  }

  arguments 55 lines copy
• scrutica_get_methodology reads unknown 9h ago

  Return 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".

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "topic"
    ],
    "properties": {
      "topic": {
        "enum": [
          "flop-estimation",
          "cost-index",
          "compute-visibility-index",
          "supply-chain-weighting",
          "chokepoint-cascade",
          "sovereign-execution-classification"
        ],
        "type": "string"
      }
    }
  }

  arguments 20 lines copy
• scrutica_search reads unknown 9h ago

  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 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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "default": 10,
        "maximum": 20,
        "minimum": 1
      },
      "query": {
        "type": "string",
        "minLength": 1,
        "description": "Free-text search query"
      },
      "country": {
        "type": "string",
        "maxLength": 2,
        "minLength": 2,
        "description": "ISO 3166-1 alpha-2 country code (e.g. US, CN, TW)"
      },
      "entity_type": {
        "enum": [
          "facility",
          "company",
          "sovereign_program",
          "all"
        ],
        "type": "string",
        "default": "all",
        "description": "Limit results to this entity class"
      }
    }
  }

  arguments 37 lines copy
• scrutica_get_facility reads unknown 23h ago

  Fetch complete details for a single Scrutica facility by canonical ID. Returns: roles[] — each organisation the record names, under the relationship its own source ESTABLISHES (site owner, site operator, AI hardware owner, or another relationship such as PeeringDB listing holder, lessee, developer), with the reason, source URL, quote and authority tier; withheld_roles[] — recorded attributions the cited source does not establish, with the reason; then country, place (the city, town or census-designated place containing the site, else its county; then state and country) with place_basis saying how it was derived, the source's own location cells verbatim (source_location_cells), power capacity (MW), GPU inventory (where disclosed), location (lat/lng), facility type, status, data_source, source_url, is_estimated flags, and any logged data-quality flags (cross-source divergence investigations). present_inventory is Scrutica's partition-by-partition compute evidence (the verdict the facility page, threshold table and query tools use): each accelerator partition admitted at its cited 16-bit rate (rate_format names FP16 or BF16, as the vendor prints it; rate_sparsity says dense, or unstated where the vendor labels the rate neither way) or held with a reason; one held partition withholds the facility figure. Read facility_peak_pflops_16bit, dense_16bit_tflops_per_accelerator and peak_pflops_16bit. The deprecated facility_peak_pflops_fp16, dense_fp16_tflops_per_accelerator and peak_pflops_fp16 keep their earlier meaning, a figure at an FP16 rate: they are null for a BF16 partition, and the facility figure is null unless every partition is admitted at FP16. facility.peak_pflops_fp16 and h100_equivalent_gpus are the record's catalogue scalars, a different basis. Describe an organisation as the site's owner ONLY where roles[] names it "Site owner"; a recorded organisation is not by itself evidence of title or operation. Where a role's evidence covers only part of the record, that role's scope_extent is "part", scope names the part, and the role reads "…, for <the part>"; state the role of that part only, never of the whole site. For BIS Entity List designations tied to an organisation recorded at the facility, look it up via scrutica_query_export_controls — this tool does not compute ownership-chain BIS exposure. Resolve facility IDs first via scrutica_search.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "id": {
        "type": "string",
        "description": "Alias for facility_id."
      },
      "entity_id": {
        "type": "string",
        "description": "Alias for facility_id."
      },
      "facility_id": {
        "type": "string",
        "description": "REQUIRED. Canonical Scrutica facility ID. Format: 'fac-<slug>' (e.g. 'fac-tsmc-arizona-fab21-p2', 'fac-tsmc-fab-18'). Resolve via scrutica_search first — do NOT guess slugs. Optional in the schema only so the aliases below can stand in; supply exactly one of these."
      }
    }
  }

  arguments 18 lines copy

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

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.