OpenHeritage Public Search
REMOTE · OPENHERITAGE.ONLINE · SCANNED SEP 24
Read-only OpenHeritage search for genealogy and cultural heritage records.
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 Security60
- 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 12 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 614 tokens (~43/item across 14 items; 12 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 5 additions. See how to fix → Fail
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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 OpenHeritage Public Search MCP server?
OpenHeritage Public Search is a hosted endpoint at https://openheritage.online/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 · openheritage.online
claude mcp add --transport http openheritageonline-public-search 'https://openheritage.online/mcp'
{
"mcpServers": {
"openheritageonline-public-search": {
"url": "https://openheritage.online/mcp"
}
}
} {
"servers": {
"openheritageonline-public-search": {
"type": "http",
"url": "https://openheritage.online/mcp"
}
}
} [mcp_servers.openheritageonline-public-search] url = "https://openheritage.online/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"openheritageonline-public-search": {
"type": "remote",
"url": "https://openheritage.online/mcp",
"enabled": true
}
}
} openclaw mcp add openheritageonline-public-search --url 'https://openheritage.online/mcp' --transport streamable-http
mcp_servers:
openheritageonline-public-search:
url: "https://openheritage.online/mcp" {
"McpServers": {
"openheritageonline-public-search": {
"Transport": "http",
"Url": "https://openheritage.online/mcp"
}
}
} assistant mcp add openheritageonline-public-search -t streamable-http -u 'https://openheritage.online/mcp'
{
"mcpServers": {
"openheritageonline-public-search": {
"type": "http",
"url": "https://openheritage.online/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.
- 24 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 2.14.0 → 2.14.1 functional
- 23 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 22 Sept 26 0
- Server version: 2.13.4 → 2.14.0 functional
- 21 Sept 26 −1
- HSTS header: unverified → fail ▼ security
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 2.12.3 → 2.13.4 functional
- 20 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 19 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Sept 26 +24
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Server version: 2.11.6 → 2.12.3 functional
- 17 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
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 24 Sept 2026 · Probed https://openheritage.online/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openheritage.online | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7433338fbd720d2213633aa7d459b95e |
| SANs: openheritage.online, *.openheritage.online | ||||||
| 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 openheritage.online. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| online. | present | 30961 | 13 | Verified |
| openheritage.online. | present | 2371 | 13 | Verified |
| openheritage.online. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openheritage.online/mcp | Verified | 400 | |
| http (plaintext) | http://openheritage.online/mcp | HTTPS enforced | 301 | https://openheritage.online/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 →
autocomplete_places ~56
Autocomplete active canonical places by prefix, optionally resolving historical context for a date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | yes | – |
| query | string | yes | – |
| take | integer|null | yes | – |
| typeCode | string|null | yes | – |
No output schema declared.
No examples provided.
find_places_nearby ~74
Find active canonical places near coordinates, optionally resolving historical context for a date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | yes | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| radiusKm | number|null | yes | – |
| take | integer|null | yes | – |
| typeCode | string|null | yes | – |
No output schema declared.
No examples provided.
get_place ~41
Read a canonical place by stable ID, optionally resolving its historical context for a date.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | yes | – |
| placeId | string | yes | – |
No output schema declared.
No examples provided.
search_authors ~32
Search public person and organization author authority records by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_cemeteries ~31
Search public cemeteries by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_collections ~30
Search public OpenHeritage collections by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_documents ~27
Search public source documents by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_memorials ~29
Search public memorial records by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_places ~144
Search active canonical places by text and optional geographic or type filters.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | yes | Optional historical date in yyyy-MM-dd format. |
| hasCoordinates | boolean|null | yes | Optionally require places to have or not have coordinates. |
| latitude | number|null | yes | Optional latitude in decimal degrees; longitude is required when supplied. |
| longitude | number|null | yes | Optional longitude in decimal degrees; latitude is required when supplied. |
| query | string | yes | Required place name or text to search for. |
| radiusKm | number|null | yes | Optional positive search radius in kilometres; coordinates are required when supplied. |
| typeCode | string|null | yes | Optional canonical place type code. |
No output schema declared.
No examples provided.
search_records ~45
Search public OpenHeritage records across supported entity types.
| Name | Type | Req | Description |
|---|---|---|---|
| entityTypes | array|null | yes | Optional public entity type filters. |
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_repositories ~28
Search public source repositories by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
search_sources ~26
Search public sources by text.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Required text to search for. |
No output schema declared.
No examples provided.
What is the OpenHeritage Public Search MCP server?
OpenHeritage Public Search is an MCP server listed in the public MCP registry as io.github.OpenHeritageOnline/public-search. Read-only OpenHeritage search for genealogy and cultural heritage records. This page covers its hosted endpoint (https://openheritage.online/mcp).
Is the OpenHeritage Public Search MCP server safe to use?
OpenHeritage Public Search scores 78 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 OpenHeritage Public Search MCP server expose?
OpenHeritage Public Search exposes 12 tools: search_collections, search_memorials, find_places_nearby, search_sources, search_records, and 7 more. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.
Does the OpenHeritage Public Search MCP server require authentication?
No. We connected to OpenHeritage Public Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OpenHeritage Public Search MCP server still maintained?
OpenHeritage Public Search is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.