Scrutica

io.github.davidgringras由 GitHub 账号 davidgringras 发布v0.2.0更新于 Oct 24, 2026

AI compute infrastructure intelligence: facilities, supply chains, sovereign AI, export controls.

已验证Streamable HTTP可网页运行网页搜索与抓取

概览

AI 生成的概览

Scrutica 让助手获取 AI 算力基础设施情报:设施、供应链、主权 AI 与出口管制。

可以做什么
Scrutica 是一个远程 MCP 服务器,聚焦 AI 算力基础设施情报。根据其注册表描述,它涵盖设施、供应链、主权 AI 计划以及出口管制。清单中未公布工具列表,因此它具体提供哪些查询或数据集在此无法说明。
适用场景
当助手需要了解 AI 算力建设、芯片与硬件供应链、各国 AI 计划或出口管制相关背景与研究时,可以考虑使用。对于该领域之外的通用任务,相关性较低。
运行要求
它以远程 streamable HTTP 端点形式运行在 scrutica.com,无需本地运行时或安装软件包。清单声明无需身份验证、环境变量或请求头,但需要能访问该端点的网络。
安装前请注意
清单未声明任何凭据,也未公布工具列表,因此该服务器能读取或修改什么并不明确。对于出口管制或供应链方面的回答,应视为第三方数据,使用前先核实。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Scrutica,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.davidgringras%2Fscrutica/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "scrutica": {
      "type": "http",
      "url": "https://scrutica.com/api/mcp"
    }
  }
}

工具

10

scrutica_get_facility

Facility record

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, 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 dense FP16 rate or held with a reason; one held partition withholds the facility figure. 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. 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.

输入参数identity_idfacility_id

scrutica_get_company

Company record

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.

输入参数idorg_identity_idcompany_idorganization_id

scrutica_query_export_controls

Export-control designations

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

输入参数limitcountryentity_identity_name

scrutica_entity_list_changes

Entity List change log

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, entity / addition / removal counts, 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 entity_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 designation_date is the effective date of the Federal Register notice that added the entry, except where the citation resolves to no notice; the event date is derived (modal designation_date, falling back to modal effective_date) and labeled with its source.

输入参数limitweekscompany_id

scrutica_get_supply_chain

Supply-chain edges

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,798 supply-chain records across all sources (snapshot 2026-10-22). Of these records, 1,924 come from a licensed layer limited to relationships between organizations already in Scrutica's records.

输入参数limitorg_idorg_idsdirectioncompany_id

scrutica_get_sovereign_program

Sovereign AI program

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. '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. Disbursements can include transfers to an administering body before expenditure on equipment or services. Missing fields and differing reporting scopes limit comparisons; reality_ratio_unavailable_reason explains an absent ratio.

输入参数countrylist_allprogram_id

scrutica_get_scenario

Risk scenario

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), 'south-china-sea' (submarine cable severing), '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.

输入参数scenario_id必填

scrutica_estimate_flops

FLOP estimator

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.

输入参数sparsityprecisionunit_count必填utilizationhardware_type必填

scrutica_get_methodology

Methodology reference

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

输入参数topic必填

版本历史

1
  1. v0.2.0最新Sep 16, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。