Family Office Knowledge Graph
https://familyofficeknowledgegraph.ai
Registry code: 51f34fb212fd1270
Read-only door over the Family Office Knowledge Graph (public record, one record per family office, every field with source_url, read_by, state). This is the apex door; it holds the index and forwards to the node that serves the record. Tools: resolve_family_office, get_record, list_events_since, list_aliases, list_nodes (reads; each cleared read is evidenced by an RCO-10060 receipt on chain fo-kg); claim_seat and list_my_receipts (a family office's own agent, its own record only). Errors are typed. Nothing is answered from memory.
- endpoint
- https://familyofficeknowledgegraph.ai/mcp
- door code
- 15f0afd68eb9e3e2
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Family Office Knowledge Graph live?
- Yes — it answered the hub's last check (checked 10h ago). It answered 100% of checks over the last 30 days.
- Is Family Office Knowledge Graph free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Family Office Knowledge Graph have?
- 7 tools: get_record, claim_seat, list_events_since, resolve_family_office, list_aliases, list_my_receipts, list_nodes.
- Is Family Office Knowledge Graph safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.7%· all time 98.6%
last good check
of 7 tools
- used for
- resolve a family office by lei or name
- get a family office's public record
- list dated events for a family office
- list name aliases of a family office
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 21 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-09
shared-payto
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_nodes reads open 10h ago
The graph's nodes — one per jurisdiction — with record counts read from each node's index, the node door and its as-of.
{ "type": "object", "properties": {} }arguments 4 linesget_record reads unknown 37h ago
The Family Office Record for one identifier: every field with value, source_url, read_by and state; optionally a named version.
{ "type": "object", "required": [ "identifier" ], "properties": { "version": { "type": "string", "description": "record version as listed by list_nodes (e.g. 2026-09-13.1); omit for current" }, "identifier": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive)" } } }arguments 18 linesclaim_seat unknown never probed
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).
{ "type": "object", "required": [ "card_url", "record_id" ], "properties": { "rows": { "type": "object", "properties": { "aliases": { "type": "array", "items": { "type": "string" } }, "sectors": { "type": "array", "items": { "type": "string" } }, "website": { "type": "string" }, "structure": { "type": "string" }, "contact_url": { "type": "string" }, "description": { "type": "string" } }, "description": "the seat's own fields" }, "card_url": { "type": "string", "description": "https URL of the office agent's card (A2A agent card JSON)" }, "seat_key": { "type": "string", "description": "the seat key answered when the claim was proven (for rows)" }, "record_id": { "type": "string", "maxLength": 120, "minLength": 2, "description": "the office's record id as the graph serves it (resolve_family_office lists it)" }, "challenge_id": { "type": "string", "description": "the challenge_id from the accepted claim, once the token is published" } } }arguments 57 lineslist_events_since reads unknown 10h ago
Dated, URL'd events on one record (registrations, renewals, orders, acquisitions), oldest first, optionally since a date, paged by cursor.
{ "type": "object", "required": [ "identifier" ], "properties": { "limit": { "type": "integer", "default": 50, "maximum": 200, "minimum": 1 }, "since": { "type": "string", "description": "ISO date YYYY-MM-DD; events on or after it" }, "cursor": { "type": "string", "description": "next_cursor from a previous page" }, "identifier": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive)" } } }arguments 28 linesresolve_family_office reads unknown never probed
Resolve an identifier (LEI, legal name, alias or register id) to the family-office records that carry it, with the node that serves each.
{ "type": "object", "required": [ "identifier" ], "properties": { "identifier": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive)" } } }arguments 14 lineslist_aliases reads unknown 37h ago
Every name the record carries for one identifier — legal name, register names, other names — each with its source.
{ "type": "object", "required": [ "identifier" ], "properties": { "identifier": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive)" } } }arguments 14 lineslist_my_receipts unknown 10h ago
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.
{ "type": "object", "required": [ "record_id", "seat_key" ], "properties": { "limit": { "type": "integer", "default": 100, "maximum": 500, "minimum": 1 }, "cursor": { "type": "string" }, "seat_key": { "type": "string" }, "record_id": { "type": "string", "maxLength": 120, "minLength": 2 } } }arguments 26 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id51f34fb212fd1270.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/51f34fb212fd1270/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/51f34fb212fd1270?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 344ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.