Family Office Knowledge Graph
REMOTE · MCP.FAMILYOFFICEKNOWLEDGEGRAPH.AI · SCANNED SEP 26
Family Office Knowledge Graph: read-only MCP door over the public record. Agentic KG Holdings.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 465 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Family Office Knowledge Graph MCP server?
Family Office Knowledge Graph is a hosted endpoint at https://mcp.familyofficeknowledgegraph.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.familyofficeknowledgegraph.ai
claude mcp add --transport http ai-familyofficeknowledgegraph-fo-kg 'https://mcp.familyofficeknowledgegraph.ai/mcp'
{
"mcpServers": {
"ai-familyofficeknowledgegraph-fo-kg": {
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
} {
"servers": {
"ai-familyofficeknowledgegraph-fo-kg": {
"type": "http",
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
} [mcp_servers.ai-familyofficeknowledgegraph-fo-kg] url = "https://mcp.familyofficeknowledgegraph.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-familyofficeknowledgegraph-fo-kg": {
"type": "remote",
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-familyofficeknowledgegraph-fo-kg --url 'https://mcp.familyofficeknowledgegraph.ai/mcp' --transport streamable-http
mcp_servers:
ai-familyofficeknowledgegraph-fo-kg:
url: "https://mcp.familyofficeknowledgegraph.ai/mcp" {
"McpServers": {
"ai-familyofficeknowledgegraph-fo-kg": {
"Transport": "http",
"Url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
} assistant mcp add ai-familyofficeknowledgegraph-fo-kg -t streamable-http -u 'https://mcp.familyofficeknowledgegraph.ai/mcp'
{
"mcpServers": {
"ai-familyofficeknowledgegraph-fo-kg": {
"type": "http",
"url": "https://mcp.familyofficeknowledgegraph.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Probed https://mcp.familyofficeknowledgegraph.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=familyofficeknowledgegraph.ai | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a3c8d3ac9fdc716d0e7dbd6aedf0f7e7 |
| SANs: familyofficeknowledgegraph.ai, mcp.familyofficeknowledgegraph.ai, *.mcp.familyofficeknowledgegraph.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.familyofficeknowledgegraph.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| familyofficeknowledgegraph.ai. | present | 2371 | 13 | Verified |
| mcp.familyofficeknowledgegraph.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; img-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self'; connect-src 'self' https://formspree.io; form-action https://formspree.io; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.familyofficeknowledgegraph.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.familyofficeknowledgegraph.ai/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_record ~97
The Family Office Record for one identifier: every field with value, source_url, read_by and state; optionally a named version.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive) |
| version | string | – | record version as listed by list_nodes (e.g. 2026-09-13.1); omit for current |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
| served_by | object | – | – |
No examples provided.
list_aliases ~64
Every name the record carries for one identifier — legal name, register names, other names — each with its source.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive) |
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | yes | – |
| legal_name | object | – | – |
| lei | string | yes | – |
| served_by | object | – | – |
No examples provided.
list_events_since ~112
Dated, URL'd events on one record (registrations, renewals, orders, acquisitions), oldest first, optionally since a date, paged by cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from a previous page |
| identifier | string | yes | Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive) |
| limit | integer | – | – |
| since | string | – | ISO date YYYY-MM-DD; events on or after it |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | – |
| lei | string | yes | – |
| next_cursor | string|null | – | – |
| served_by | object | – | – |
No examples provided.
list_nodes ~35
The graph's nodes — one per jurisdiction — with record counts read from each node's index, the node door and its as-of.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| apex | object | – | – |
| nodes | array | yes | – |
No examples provided.
resolve_family_office ~73
Resolve an identifier (LEI, legal name, alias or register id) to the family-office records that carry it, with the node that serves each.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Record id, LEI, legal name, alias, or a register identifier as it appears on the record (case-insensitive) |
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| matches | array | yes | – |
| served_by | object | – | – |
No examples provided.
What is the Family Office Knowledge Graph MCP server?
Family Office Knowledge Graph is an MCP server listed in the public MCP registry as ai.familyofficeknowledgegraph/fo-kg. Family Office Knowledge Graph: read-only MCP door over the public record. Agentic KG Holdings. This page covers its hosted endpoint (https://mcp.familyofficeknowledgegraph.ai/mcp).
Is the Family Office Knowledge Graph MCP server safe to use?
Family Office Knowledge Graph scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Family Office Knowledge Graph MCP server expose?
Family Office Knowledge Graph exposes 5 tools: resolve_family_office, get_record, list_events_since, list_aliases, list_nodes. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.
Does the Family Office Knowledge Graph MCP server require authentication?
No. We connected to Family Office Knowledge Graph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Family Office Knowledge Graph MCP server still maintained?
Family Office Knowledge Graph is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.