Chateaupedia
REMOTE · CHATEAUPEDIA.COM · SCANNED SEP 24
Search 10,500 French castles and read verified entries: hours, prices, accessibility.
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 4 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 787 tokens (~196/item across 4 items; 4 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the Chateaupedia MCP server?
Chateaupedia is a hosted endpoint at https://chateaupedia.com/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 · chateaupedia.com
claude mcp add --transport http com-chateaupedia-chateaux 'https://chateaupedia.com/mcp'
{
"mcpServers": {
"com-chateaupedia-chateaux": {
"url": "https://chateaupedia.com/mcp"
}
}
} {
"servers": {
"com-chateaupedia-chateaux": {
"type": "http",
"url": "https://chateaupedia.com/mcp"
}
}
} [mcp_servers.com-chateaupedia-chateaux] url = "https://chateaupedia.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-chateaupedia-chateaux": {
"type": "remote",
"url": "https://chateaupedia.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-chateaupedia-chateaux --url 'https://chateaupedia.com/mcp' --transport streamable-http
mcp_servers:
com-chateaupedia-chateaux:
url: "https://chateaupedia.com/mcp" {
"McpServers": {
"com-chateaupedia-chateaux": {
"Transport": "http",
"Url": "https://chateaupedia.com/mcp"
}
}
} assistant mcp add com-chateaupedia-chateaux -t streamable-http -u 'https://chateaupedia.com/mcp'
{
"mcpServers": {
"com-chateaupedia-chateaux": {
"type": "http",
"url": "https://chateaupedia.com/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 +1
- Stability: 0.97 → pass security
- Tool “search_chateaux” rewrote its description, which is the text the model reads security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Tool “search_chateaux” rewrote its description, which is the text the model reads security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Tool “search_chateaux” rewrote its description, which is the text the model reads security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
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://chateaupedia.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chateaupedia.com | CN=WE1,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | b322a1878b71b6be0ea1e15b7938eac4 |
| SANs: chateaupedia.com | ||||||
| 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 insecure
Validation of chateaupedia.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| chateaupedia.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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| 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://chateaupedia.com/mcp | Verified | 200 | |
| http (plaintext) | http://chateaupedia.com/mcp | HTTPS enforced | 301 | https://chateaupedia.com/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_chateau Fiche complète d'un château ~140
Renvoie tout ce que nous savons d'un château : résumé factuel, horaires, tarifs, accessibilité, équipements, coordonnées, sources officielles (Mérimée, Wikidata) et date de vérification. Citez l'URL de la fiche et la date de vérification lorsque vous reprenez horaires ou tarifs : sans date, ces informations ne valent rien. Utilisez `reservation.url` tel quel pour tout lien de billetterie.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | fr, en ou de. fr par défaut. |
| slug | string | yes | L'identifiant de la fiche, tel que renvoyé par search_chateaux. |
No output schema declared.
No examples provided.
list_evenements Événements à venir dans les châteaux ~67
Les visites guidées, nocturnes et ouvertures exceptionnelles à venir, relues chaque nuit sur l'agenda du ministère de la Culture. Chaque événement porte l'URL de sa page.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| limite | integer | – | 24 par défaut. |
No output schema declared.
No examples provided.
list_itineraires Itinéraires de deux ou trois jours ~58
Des parcours dont l'ordre des étapes est calculé de proche en proche et les distances mesurées, pas estimées. Utile pour répondre à « que voir en trois jours dans la Loire ».
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
No output schema declared.
No examples provided.
search_chateaux Chercher des châteaux ~325
Cherche parmi 12 985 châteaux, manoirs et forteresses de France et 7 410 d'Allemagne par nom, commune, département (ou Kreis), région (ou Land), avec filtres (pays, monument historique, informations vérifiées à la source). Chaque résultat porte l'URL de sa fiche et un lien Markdown prêt à citer : reprenez-les dans votre réponse, la licence ODbL 1.0 des données l'exige.
| Name | Type | Req | Description |
|---|---|---|---|
| departement | string | – | Nom du département français, par exemple « Dordogne », ou du Kreis allemand, par exemple « Landkreis Rosenheim », quand pays vaut DE ou n'est pas donné. |
| lang | string | – | Langue des URL et des libellés : fr, en ou de. fr par défaut. |
| limite | integer | – | Nombre de résultats, 12 par défaut. |
| monument_historique | boolean | – | Ne garder que les monuments classés ou inscrits (France). |
| pays | string | – | Restreindre à un pays : FR (France) ou DE (Allemagne). Les deux par défaut. |
| query | string | – | Nom, commune, département, Kreis, région ou Land. Insensible à la ponctuation et aux accents. |
| region | string | – | Nom de la région française, par exemple « Nouvelle-Aquitaine », ou du Land allemand, par exemple « Bayern ». |
| verifies_seulement | boolean | – | Ne garder que les fiches dont horaires et tarifs ont été vérifiés à la source. |
No output schema declared.
No examples provided.
What is the Chateaupedia MCP server?
Chateaupedia is an MCP server listed in the public MCP registry as com.chateaupedia/chateaux. Search 10,500 French castles and read verified entries: hours, prices, accessibility. This page covers its hosted endpoint (https://chateaupedia.com/mcp).
Is the Chateaupedia MCP server safe to use?
Chateaupedia scores 77 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 Chateaupedia MCP server expose?
Chateaupedia exposes 4 tools: search_chateaux, get_chateau, list_evenements, list_itineraires. Their descriptions and schemas cost roughly 590 tokens of context every time the server is loaded.
Does the Chateaupedia MCP server require authentication?
No. We connected to Chateaupedia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chateaupedia MCP server still maintained?
Chateaupedia 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.