Agentic KG Holdings MCP server

• Registry nameai.familyofficeknowledgegraph/fo-kgverified in the MCP registry

The registry name sits under familyofficeknowledgegraph.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-23
• Tools5
• Server calls itselfFamily Office Knowledge Graph
• Server version0.20.1
• Protocol version2025-06-18

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 232 ms.

• Its tools do every use case we checked: look up a family office by LEI or legal name; list dated events for a family office.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer283 ms
• Space in an agent's context≈ 570 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsA · 97 of 100
• Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 5

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.

• get_record

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

• 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.