Analytics

whiteintel.dev

Provides entity resolution, search, and ownership tracing for companies and people to generate risk dossiers and beneficial ownership chains.

1 endpoint24 known toolsFirst detected July 6, 2026Last detected September 20, 2026

ENDPOINT 1

https://whiteintel.dev/api/mcp

No auth detected

MCP server metadata

Name: whiteintel-mcp-server
Version: 0.7.11

Capabilities

toolsresources

Server instructions

WhiteIntel corporate & offshore ownership intelligence over the public API. Resolve companies (by name, identifier, or meaning via semantic_search), trace ownership to the UBO, screen sanctions, pull cited dossiers + filed financials. Agents can transact: get_pricing → buy_dossier (guest Stripe Checkout) → claim_dossier mints a token → get_dossier with that token returns the unlocked report. Read the ontology resource (schema) to learn the field vocabulary.

Known tools 24

resolve

Batch-resolve a list of company names or scheme:value identifiers (lei/siren/br-cnpj/gb-coh/uen/sec/ofac/eu/un/uk/krs) to canonical WhiteIntel entity ids + confidence in ONE call.

Inferred read-only

search_entities

Search every node in the corpus — companies AND people — by name.

Inferred read-only

list_jurisdictions

The WhiteIntel coverage map — every jurisdiction we hold and HOW we hold it.

Inferred read-only

list_asset_coverage

The WhiteIntel ASSET-ownership coverage map — who owns the plane / yacht / property, and HOW we hold that link.

Inferred read-only

get_entity

Full record for one entity id + its direct relationships, with provenance.

Inferred read-only

get_dossier

Structured, fully-cited dossier for one entity: cross-source identity, ownership/UBO chain, risk signals, filed financials, provenance.

Inferred read-only

purchase_dossier

BUY the full dossier for one entity programmatically — no browser, no Stripe Checkout.

Inferred read-only

trace_ownership_path

Walk ownership upward from a root entity to the ultimate beneficial owner(s).

Inferred read-only

graph_neighbourhood

Every ownership/control edge within a bounded number of hops of one entity, in BOTH directions — who it controls, who controls it, and their neighbours.

Inferred read-only

graph_path

How two entities are connected: the ordered hops of a bounded breadth-first search over ownership and control edges in both directions.

Inferred read-only

lookup_by_identifier

Resolve a corpus entity by a strong identifier — lei | ofac | eu | un | uk | uen | sec | krs | gb-coh | siren | br-cnpj (Brazil RFB CNPJ, 8-digit root or full 14-digit).

Inferred read-only

get_sanctions

An entity's sanctions exposure (OFAC/EU/UN/UK) for it and its resolved cluster siblings, each cited.

Inferred read-only

check_offshore_exposure

Walk the ownership chain and flag sanctioned + secrecy-jurisdiction hops — the offshore-layering lead.

Inferred read-only

get_company_details

Registered profile for a company: address, status, SIC, incorporation, plus filing/compliance (overdue, charges, former names).

Inferred read-only

get_financials

Filed financials year-over-year: turnover, profit, net assets, cash, employees (Companies House iXBRL).

Inferred read-only

get_pulse

The corpus activity feed — recent ownership-change and filed-accounts events, cited.

Inferred read-only

lookup_company

UK company by Companies House number → record + ready-built ownership graph.

Inferred read-only

search_companies

Free-text UK Companies House company-name search → registration number.

Inferred read-only

semantic_search

Meaning-based entity search (BGE-M3 vector ANN over the resolved dossier cards).

Inferred read-only

find_similar

Entities most similar to a given one — the nearest corpus dossier cards ('more like this') for peer discovery.

Inferred read-only

get_pricing

WhiteIntel's price list + the exact machine flow for buying access: one verified dossier (€29, one price, everything), subscriptions (Pro €99/mo, Scale €499/mo) and the metered API.

Inferred read-only

buy_dossier

Start a one-off dossier purchase via guest Stripe Checkout — no WhiteIntel account needed (Stripe collects an email for delivery).

Potential side effects

get_payment_link

PERMANENT, shareable Stripe payment links for the one-off dossiers — use this instead of buy_dossier when you need something you can HAND TO A HUMAN.

Potential side effects

claim_dossier

Redeem a paid Stripe Checkout session for a dossier access token.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.whiteintel-mcp-server]
url = "https://whiteintel.dev/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "whiteintel-mcp-server": {
      "type": "http",
      "url": "https://whiteintel.dev/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: whiteintel-mcp-server
Remote MCP URL: https://whiteintel.dev/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "whiteintel-mcp-server": {
      "url": "https://whiteintel.dev/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "whiteintel-mcp-server": {
      "type": "http",
      "url": "https://whiteintel.dev/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "whiteintel-mcp-server",
  "transport": "streamable-http",
  "url": "https://whiteintel.dev/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for whiteintel.dev was fetched 2026-08-21T13:40:09.473Z and is being refreshed.

Trust status Neutral

whiteintel.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.