INDIVIDUAL MCP TOOL
get_record
The Family Office Record for one identifier: every field with value, source_url, read_by and state; optionally a named version.
LIVE ENDPOINT
https://mcp.familyofficeknowledgegraph.ai/mcp
Connect to this endpoint to inspect the live schema for get_record 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.family-office-knowledge-graph]
url = "https://mcp.familyofficeknowledgegraph.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"family-office-knowledge-graph": {
"type": "http",
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: family-office-knowledge-graph
Remote MCP URL: https://mcp.familyofficeknowledgegraph.ai/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": {
"family-office-knowledge-graph": {
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"family-office-knowledge-graph": {
"type": "http",
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "family-office-knowledge-graph",
"transport": "streamable-http",
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
resolve_family_office— Resolve an identifier (LEI, legal name, alias or register id) to the family-office records that carry it, with the node that serves each.list_events_since— Dated, URL'd events on one record (registrations, renewals, orders, acquisitions), oldest first, optionally since a date, paged by cursor.list_aliases— Every name the record carries for one identifier — legal name, register names, other names — each with its source.list_nodes— The graph's nodes — one per jurisdiction — with record counts read from each node's index, the node door and its as-of.