Scrutica MCP Server

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

Tools

Last Updated

Jun 14, 2026

What is the Scrutica MCP Server?

The Scrutica MCP server gives AI agents structured, permission-aware access to Scrutica through the Model Context Protocol. With 9 pre-built actions, agents can read, create, and update Scrutica data on behalf of authorized users.

Willow ships the Scrutica MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Scrutica is being used by every AI agent in your stack.

Tools

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 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_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), 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_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, 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_controls

Look 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_chain

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: source_org_id, target_org_id, relationship_type, supply_share (where disclosed), price_correlation_3m (3-month rolling, where available), data_source. Dataset: 20,534 edges from a licensed supply-chain database (held under subscription, not redistributed) plus SEC Exhibit 21 (substrate snapshot 2026-05-19).

scrutica_get_sovereign_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, governance_reach, NVIDIA/US dependency, source_count. 'list_all' returns a summary table of all tracked programs for cross-country comparison.

scrutica_get_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 scenario summary with key assumptions, affected facilities, recovery timeline, and source citations.

scrutica_estimate_flops

Compute 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_methodology

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

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

Set Up Your Scrutica MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json

{
  "mcpServers": {
    "willow-scrutica": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/scrutica"
    }
  }
}

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "willow-scrutica": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/scrutica"
    }
  }
}

Claude Code

CLI

claude mcp add willow-scrutica --transport http https://<org>.mcp-s.com/mcp/mcp/scrutica

n8n

HTTP Request Node

{
  "url": "https://<org>.mcp-s.com/mcp/mcp/scrutica",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Scrutica

Willow adds the layer Scrutica and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Scrutica MCP Server FAQ

What is the Scrutica MCP server?

The Scrutica MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Scrutica data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Scrutica MCP server different from the official one?

The official Scrutica MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Scrutica MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Scrutica MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Scrutica, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Scrutica actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Scrutica MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Scrutica MCP locally, you'll see it.

What does the Scrutica MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Scrutica MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.