Family Office Knowledge Graph

ai.familyofficeknowledgegraph/fo-kgVersion 0.21.0

Family Office Knowledge Graph: read-only MCP door over the public record. Agentic KG Holdings.

Status

Responds429 msNov 14, 2026, 13:29 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:29 UTC
Latency: 429 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.familyofficeknowledgegraph.ai/mcpResponds429 msNov 14, 2026, 13:29 UTC

No sign-in

Claude Code

claude mcp add --transport http fo-kg https://mcp.familyofficeknowledgegraph.ai/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: fo-kg
Remote MCP server URL: https://mcp.familyofficeknowledgegraph.ai/mcp

Cursor

{
  "mcpServers": {
    "fo-kg": {
      "url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"fo-kg","type":"http","url":"https://mcp.familyofficeknowledgegraph.ai/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

7 tools

Tools of Family Office Knowledge Graph
	Description		Read-only	Idempotent	Open world
`claim_seat`A family office's own agent claims the seat of its own record. Give card_url (the https URL of the office agent's card) and record_id (the record id as the graph serves it). The record must resolve to the name the card gives; the door then issues a domain challenge (DNS TXT _fo-kg-seat.<domain> or https://<domain>/.well-known/fo-kg-seat.txt). Call again with challenge_id: proven → the record moves listed → claimed and the seat key is answered once. With seat_key and rows, the seat sets its own fields on its own record only (website, aliases, sectors, structure, description, contact_url); the sourced fields are never touched and verified is set by a person, never by a tool. The seat settles on /seat (x402).	A family office's own agent claims the seat of its own record. Give card_url (the https URL of the office agent's card) and record_id (the record id as the graph serves it). The record must resolve to the name the card gives; the door then issues a domain challenge (DNS TXT _fo-kg-seat.<domain> or https://<domain>/.well-known/fo-kg-seat.txt). Call again with challenge_id: proven → the record moves listed → claimed and the seat key is answered once. With seat_key and rows, the seat sets its own fields on its own record only (website, aliases, sectors, structure, description, contact_url); the sourced fields are never touched and verified is set by a person, never by a tool. The seat settles on /seat (x402).	No	No	No	Yes
`get_record`The Family Office Record for one identifier: every field with value, source_url, read_by and state; optionally a named version.	The Family Office Record for one identifier: every field with value, source_url, read_by and state; optionally a named version.	No	Yes	Yes	No
`list_aliases`Every name the record carries for one identifier — legal name, register names, other names — each with its source.	Every name the record carries for one identifier — legal name, register names, other names — each with its source.	No	Yes	Yes	No
`list_events_since`Dated, URL'd events on one record (registrations, renewals, orders, acquisitions), oldest first, optionally since a date, paged by cursor.	Dated, URL'd events on one record (registrations, renewals, orders, acquisitions), oldest first, optionally since a date, paged by cursor.	No	Yes	Yes	No
`list_my_receipts`For a seat holder only: the RCO-10060 receipts whose subject is its own record — who read it (as the door saw the reader: user agent, network, country), when, and under which rule (the tool) — newest first, each with its verify URL. Needs record_id and the seat key of that record; nobody else can list them.	For a seat holder only: the RCO-10060 receipts whose subject is its own record — who read it (as the door saw the reader: user agent, network, country), when, and under which rule (the tool) — newest first, each with its verify URL. Needs record_id and the seat key of that record; nobody else can list them.	No	Yes	Yes	No
`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.	The graph's nodes — one per jurisdiction — with record counts read from each node's index, the node door and its as-of.	No	Yes	Yes	No
`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.	Resolve an identifier (LEI, legal name, alias or register id) to the family-office records that carry it, with the node that serves each.	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 5, 2026
Updated: Nov 5, 2026
Website: https://familyofficeknowledgegraph.ai/⁠ (opens in a new tab)
Repository: https://github.com/Agentic-Private-Office/fo-kg-door⁠ (opens in a new tab)
Categories (suggested): Databases Knowledge and notesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing