Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Agentic-Private-Office/fo-kg-door
GitHub Stars
0
Server Listing
ai.familyofficeknowledgegraph/fo-kg
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct operation: resolve_family_office does identifier→record lookup, get_record fetches one record by id, and list_events_since/list_my_receipts are separate dated/receipt feeds. The main overlap is list_aliases versus get_record, since get_record already returns 'every field' including names, so an agent may wonder which to call for names; claim_seat also mixes challenge/proof handling with field writes in one tool, adding some internal complexity.

Naming Consistency5/5

All seven tools follow a consistent snake_case verb_noun pattern (claim_seat, get_record, list_aliases, list_events_since, list_my_receipts, list_nodes, resolve_family_office). Verbs are used predictably: list_* for collections, get_* for single fetch, resolve_* for lookup translation, claim_* for the one mutation.

Tool Count5/5

Seven tools is well-scoped for a read-oriented registry API: five read/discovery tools plus one write tool and one receipt/audit tool. Nothing appears redundant or padded for the stated purpose.

Completeness4/5

The read surface is strong (record, aliases, events, nodes, resolution, receipts) and the write surface is intentionally limited to a seat setting its own fields, with verification reserved for humans. Minor gaps remain: no way to enumerate all records on a node, no cross-record search or search-by-sector, and no dedicated tool to check or renew a challenge/seat key state outside of calling claim_seat again.

Available Tools

7 tools
claim_seatAInspect

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. or https:///.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).

Inputs: card_url (required), record_id (required), rows, seat_key, +1 more. Returns: reason, result, seat_id, seat_key, +3 more

get_recordA
Read-onlyIdempotent
Inspect

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

Inputs: identifier (required), version. Returns: record, served_by

list_aliasesA
Read-onlyIdempotent
Inspect

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

Inputs: identifier (required). Returns: lei, aliases, served_by, legal_name

list_events_sinceA
Read-onlyIdempotent
Inspect

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

Inputs: identifier (required), limit, since, cursor. Returns: lei, events, served_by, next_cursor

list_my_receiptsA
Read-onlyIdempotent
Inspect

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.

Inputs: seat_key (required), record_id (required), limit, cursor. Returns: result, receipts, record_id

list_nodesA
Read-onlyIdempotent
Inspect

The graph's nodes — one per jurisdiction — with record counts read from each node's index, the node door and its as-of.

Inputs: no named parameters. Returns: apex, nodes

resolve_family_officeA
Read-onlyIdempotent
Inspect

Resolve an identifier (LEI, legal name, alias or register id) to the family-office records that carry it, with the node that serves each.

Inputs: identifier (required). Returns: matches, served_by, identifier

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An embedded knowledge graph in one SQLite file, exposing a MCP server for agents to read and write entities and relationships with full audit trail and time travel.
      73 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Hosted MCP server providing corporate ownership intelligence, enabling AI agents to look up parent companies, PE backing, corporate families, and portfolio siblings via natural language queries.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server serving a normalized graph of fund holdings and service providers built from SEC Form N-PORT and N-CEN data joined to the GLEIF LEI register. Currently only the ingest layer is implemented, with the MCP server not yet built.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.