INDIVIDUAL MCP TOOL
graph_path
How two entities are connected: the ordered hops of a bounded breadth-first search over ownership and control edges in both directions.
LIVE ENDPOINT
https://whiteintel.dev/api/mcp
Connect to this endpoint to inspect the live schema for graph_path and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
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.
Related tools
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.search_entities— Search every node in the corpus — companies AND people — by name.list_jurisdictions— The WhiteIntel coverage map — every jurisdiction we hold and HOW we hold it.list_asset_coverage— The WhiteIntel ASSET-ownership coverage map — who owns the plane / yacht / property, and HOW we hold that link.get_entity— Full record for one entity id + its direct relationships, with provenance.get_dossier— Structured, fully-cited dossier for one entity: cross-source identity, ownership/UBO chain, risk signals, filed financials, provenance.trace_ownership_path— Walk ownership upward from a root entity to the ultimate beneficial owner(s).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.