Family Office Registry
REMOTE · FAMILYOFFICEREGISTRY.COM · SCANNED SEP 29
Sourced, dated records of family offices in Switzerland, Liechtenstein, Austria, Germany and Dubai.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 511 tokens (~127/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Family Office Registry MCP server?
Family Office Registry is a hosted endpoint at https://familyofficeregistry.com/api/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 · familyofficeregistry.com
claude mcp add --transport http com-familyofficeregistry-registry 'https://familyofficeregistry.com/api/mcp'
{
"mcpServers": {
"com-familyofficeregistry-registry": {
"url": "https://familyofficeregistry.com/api/mcp"
}
}
} {
"servers": {
"com-familyofficeregistry-registry": {
"type": "http",
"url": "https://familyofficeregistry.com/api/mcp"
}
}
} [mcp_servers.com-familyofficeregistry-registry] url = "https://familyofficeregistry.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-familyofficeregistry-registry": {
"type": "remote",
"url": "https://familyofficeregistry.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-familyofficeregistry-registry --url 'https://familyofficeregistry.com/api/mcp' --transport streamable-http
mcp_servers:
com-familyofficeregistry-registry:
url: "https://familyofficeregistry.com/api/mcp" {
"McpServers": {
"com-familyofficeregistry-registry": {
"Transport": "http",
"Url": "https://familyofficeregistry.com/api/mcp"
}
}
} assistant mcp add com-familyofficeregistry-registry -t streamable-http -u 'https://familyofficeregistry.com/api/mcp'
{
"mcpServers": {
"com-familyofficeregistry-registry": {
"type": "http",
"url": "https://familyofficeregistry.com/api/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.
- 29 Sept 26 66
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 29 Sept 2026 · Probed https://familyofficeregistry.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lasvegasrestaurantspecials.com | CN=WR3,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | RSA 2048 | SHA256-RSA | 19182b3ab42c6bb50aed6b16a15e754f |
| SANs: lasvegasrestaurantspecials.com, auth.writepair.app, www.pangestuaprian.com, marcus-nash-portfolio.com, www.jemsactive.com, www.hashitosystem.com, www.desora-beauty.co.uk, www.stravity.in, bootea2.cl, www.sandboxdc.space, soulfulsonnets.life, paulafelices.com and 88 more | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of familyofficeregistry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| familyofficeregistry.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=31556926 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://familyofficeregistry.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://familyofficeregistry.com/api/mcp | HTTPS enforced | 301 | https://familyofficeregistry.com/api/mcp |
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 Read one registry record ~71
One firm by its registry id. Without a subscription key this returns the open fields and says how many named roles the full record holds; with one it returns the named roles, the contact channels, the full source list and the verification note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Registry id, as returned by search_registry. |
No output schema declared.
No examples provided.
search_registry Search the family office registry ~229
Search verified family offices and related firms in Switzerland, Liechtenstein, Austria and Germany, and single-family offices in Dubai (free, with no named people). Returns one page of open records — the same fields the public site publishes. Named people, contact channels, source lists and verification notes need a subscription. Read the skill resource before answering from these results.
| Name | Type | Req | Description |
|---|---|---|---|
| alloc | string | – | Subscription only: list firms by how they invest. Without a key the search refuses this filter; get_record gives any one firm's call free. |
| canton | string | – | Swiss canton code, e.g. ZH, ZG, GE. |
| country | string | – | – |
| page | integer | – | – |
| q | string | – | Free text. Without a key it looks in the open fields (name, city, register id, legal form, focus tags); with one, in the people and the purpose clauses too. For a place, filter by canton or country. |
| size | integer | – | Results per page, capped at 25 without a subscription key. |
| type | string | – | – |
No output schema declared.
No examples provided.
What is the Family Office Registry MCP server?
Family Office Registry is an MCP server listed in the public MCP registry as com.familyofficeregistry/registry. Sourced, dated records of family offices in Switzerland, Liechtenstein, Austria, Germany and Dubai. This page covers its hosted endpoint (https://familyofficeregistry.com/api/mcp).
Is the Family Office Registry MCP server safe to use?
Family Office Registry scores 66 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 Registry MCP server expose?
Family Office Registry exposes 2 tools: search_registry, get_record. Their descriptions and schemas cost roughly 300 tokens of context every time the server is loaded.
Does the Family Office Registry MCP server require authentication?
No. We connected to Family Office Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Family Office Registry MCP server still maintained?
Family Office Registry is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.