mcp-registry/com.familyofficeregistry/registry · v2
As of 2026-10-20 05:57 UTC, the Familyofficeregistry Registry MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Sourced, dated records of family offices in Switzerland, Liechtenstein, Austria, Germany and Dubai.
Claude Code
claude mcp add --transport http familyofficeregistry-registry-mcp-server https://familyofficeregistry.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"familyofficeregistry-registry-mcp-server": {
"type": "http",
"url": "https://familyofficeregistry.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,621 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.familyofficeregistry%2Fregistry/fixes
{
"name": "get_record",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Registry id, as returned by search_registry."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Read one registry record"
}{
"name": "search_registry",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "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."
},
"page": {
"type": "integer",
"default": 1,
"minimum": 1
},
"size": {
"type": "integer",
"default": 10,
"maximum": 25,
"minimum": 1,
"description": "Results per page, capped at 25 without a subscription key."
},
"type": {
"enum": [
"SFO",
"MFO",
"intermediary"
],
"type": "string"
},
"alloc": {
"enum": [
"fund-allocator",
"mixed",
"direct-only",
"no-external-investing"
],
"type": "string",
"description": "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": {
"type": "string",
"description": "Swiss canton code, e.g. ZH, ZG, GE."
},
"country": {
"enum": [
"CH",
"LI",
"AT",
"DE",
"AE"
],
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Search the family office registry"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.familyofficeregistry/registry"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.familyofficeregistry/registry"}) over MCP.
search_registry ~387 tokensget_record ~128 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.familyofficeregistry%2Fregistry?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.familyofficeregistry%2Fregistry?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.familyofficeregistry%2Fregistry.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.familyofficeregistry%2Fregistry.svg :target: https://glimind.com/server/mcp-registry%2Fcom.familyofficeregistry%2Fregistry?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e2cacf2dd990b152…, first seen 2026-10-17, included at leaf 13885 of 31,120. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 05:57 UTC, the Familyofficeregistry Registry MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Familyofficeregistry Registry MCP server advertises 2 tools, including get_record, search_registry.
Point your MCP client at this streamable-http endpoint: https://familyofficeregistry.com/api/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.