Family Office Knowledge Graph

ai.familyofficeknowledgegraphPublished by familyofficeknowledgegraph.aiOfficial publisherv0.21.0Updated Nov 5, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Read-only MCP door to the Family Office Knowledge Graph, letting an assistant look up sourced public records on family offices, their aliases and events.

What you can do
  • Resolve an LEI, legal name, alias or register id to the family-office records that carry it
  • Read a full record field by field, with source URL, reader and state, or a named version
  • List dated, sourced events on a record since a given date, paged by cursor
  • List every name a record carries, each with its source
  • List the graph's jurisdiction nodes with record counts and as-of dates
  • Claim a seat for a family office's own agent and list that seat's read receipts
When to use it
Useful when an assistant needs verifiable, source-attributed information about family offices — identity resolution, record details, aliases or dated events — rather than answers from memory. Also relevant for a family office's own agent that wants to claim its record and see who read it.
Requirements
Remote Streamable HTTP endpoint; no authentication, environment variables or headers are declared for the read tools. The seat tools require a record id and the seat key of that record, plus a domain challenge (DNS TXT or similar) to claim a seat.
Before you install
The read tools are read-only, but claim_seat and list_my_receipts act on a record and require a seat key, which is a secret to protect. Read receipts expose reader details such as user agent, network and country, so seat holders should expect that visibility. Records are drawn from the public record and forwarded to jurisdiction nodes, so queries reach third-party endpoints.

Installation

In SourceWeft

  1. Open Family Office Knowledge Graph in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.familyofficeknowledgegraph%2Ffo-kg/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "family-office-knowledge-graph": {
      "type": "http",
      "url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
    }
  }
}

README

fo-kg-door — the Family Office Knowledge Graph door

The MCP door of the Family Office Knowledge Graph, operated by Agentic KG Holdings.

Five tools, the same names on every node door: resolve_family_office, get_record, list_events_since, list_aliases, list_nodes. One record per family office, drawn from the public record: every field carries where it came from, who read it, when, and its state. Errors are typed. Nothing is answered from memory.

What this repository holds

The door source only: the Cloudflare Worker (worker/), the served machine files and records (public/), the Worker config (wrangler.toml), the registry listing (server.json) and the deploy rails (rails/). It is a mirror of the deploy source, refreshed on every roll. It carries no orders, logs, harvest work, keys or private material.

Connect

  • Claude: Settings → Connectors → Add custom connector → https://mcp.familyofficeknowledgegraph.ai/mcp
  • Any MCP client with Streamable HTTP: point it at the same URL. Machine instructions: https://familyofficeknowledgegraph.ai/llms.txt

Licence

MIT — see LICENSE.

Source: README.md at commit aef101d

Tools

7

resolve_family_office

Resolve a 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.

Parametersidentifierrequired

get_record

Get a Family Office Record

The Family Office Record for one identifier: every field with value, source_url, read_by and state; optionally a named version.

Parametersversionidentifierrequired

list_events_since

List events on a record

Dated, URL'd events on one record (registrations, renewals, orders, acquisitions), oldest first, optionally since a date, paged by cursor.

Parameterslimitsincecursoridentifierrequired

list_aliases

List aliases

Every name the record carries for one identifier — legal name, register names, other names — each with its source.

Parametersidentifierrequired

list_nodes

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.

Takes no parameters.

claim_seat

Claim a 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).

Parametersrowscard_urlrequiredseat_keyrecord_idrequiredchallenge_id

list_my_receipts

List the receipts of my record

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.

Parameterslimitcursorseat_keyrequiredrecord_idrequired

Version history

2
  1. v0.21.0LatestNov 5, 2026
  2. v0.19.13Sep 17, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Familyofficeknowledgegraph integrations

RCO-A2A - Record of Cleared Orders

Published by GitHub account Agentic-Private-Office

Remote MCP server for the Record of Cleared Orders: writes signed, hash-chained receipts for cleared agentic orders and verifies them by decision id.

Streamable HTTPWeb executable
Security & Monitoring2 toolsOct 29, 2026