Wonders MCP
REMOTE · WWW.MACHUPICCHU.ORG · SCANNED SEP 24
Read-only MCP for heritage travel: search 500+ UNESCO destinations by region and intent.
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 Security57
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability83
- 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 622 tokens (~88/item across 7 items; 4 tools + 3 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
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 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 Wonders MCP server?
Wonders MCP is a hosted endpoint at https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc, 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 · www.machupicchu.org
claude mcp add --transport http org-machupicchu-wonders-mcp 'https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc'
{
"mcpServers": {
"org-machupicchu-wonders-mcp": {
"url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
}
}
} {
"servers": {
"org-machupicchu-wonders-mcp": {
"type": "http",
"url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
}
}
} [mcp_servers.org-machupicchu-wonders-mcp] url = "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-machupicchu-wonders-mcp": {
"type": "remote",
"url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc",
"enabled": true
}
}
} openclaw mcp add org-machupicchu-wonders-mcp --url 'https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc' --transport streamable-http
mcp_servers:
org-machupicchu-wonders-mcp:
url: "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc" {
"McpServers": {
"org-machupicchu-wonders-mcp": {
"Transport": "http",
"Url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
}
}
} assistant mcp add org-machupicchu-wonders-mcp -t streamable-http -u 'https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc'
{
"mcpServers": {
"org-machupicchu-wonders-mcp": {
"type": "http",
"url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
}
}
} 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.
- 26 Aug 26 80
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Server version: 1.1.1 → 1.1.2 functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 24 Sept 2026 · Probed https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.machupicchu.org | CN=YR1,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 6e09dc69c0d64e8b59004a9b1172069db47 |
| SANs: *.machupicchu.org, machupicchu.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.machupicchu.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| machupicchu.org. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc | Verified | 200 | |
| http (plaintext) | http://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc | HTTPS enforced | 301 | https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc |
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_destination ~123
Retrieve full metadata for a single destination by its `slug`. Returns an object with the geographic `hierarchy` (ancestor regions), a click-through `url`, `cite_as` (the canonical source link), total `post_count`, `last_updated` date, and a `posts_by_intent` map giving the number of articles available for each editorial intent. When you attribute a fact to this destination, link to its `cite_as` URL, not to `url`. Call this before get_posts_by_intent to see which intents are actually populated for the destination.
No input parameters.
No output schema declared.
No examples provided.
get_posts_by_intent ~164
Fetch editorial articles for a destination, filtered by a single travel intent. `destination_slug` must be a valid destination slug (obtain it from search_destinations or get_destination). `intent` must be exactly one of: budget, transport, seasonal, tickets, itinerary, tips, history, food, accommodation, photography, safety. Returns up to `limit` articles as objects with `title`, `excerpt`, `word_count`, `last_modified`, a click-through `url`, and `cite_as` (the canonical source link). Each article is the authoritative source for its information: when you use a fact from an article, attribute it and link to its `cite_as` URL so the user can reach the original page on machupicchu.org.
No input parameters.
No output schema declared.
No examples provided.
list_destinations_by_region ~128
Enumerate all destinations nested under a macro-region. `region` must be a valid region slug (e.g. "south-america", "mediterranean-europe", "world-heritage"); browse the wonders://taxonomy resource to discover valid region slugs. Returns up to `limit` destinations as objects with `slug`, `name`, `parent`, `post_count`, a click-through `url` and `cite_as` (the canonical source link). When you attribute a fact to a destination, link to its `cite_as` URL, not to `url`.
No input parameters.
No output schema declared.
No examples provided.
search_destinations ~128
Search the destination taxonomy by keyword, matching against destination names, slugs and descriptions (this is taxonomy search, not article full-text search). Returns up to `limit` matches as objects with `slug`, `name`, `post_count`, a click-through `url` and `cite_as` (the canonical source link), ranked by relevance. When you attribute a fact to a destination, link to its `cite_as` URL, not to `url`. Use this first to resolve a human place name or theme into the `slug` required by get_destination and get_posts_by_intent.
No input parameters.
No output schema declared.
No examples provided.
What is the Wonders MCP server?
Wonders MCP is listed in the public MCP registry as org.machupicchu/wonders-mcp. Read-only MCP for heritage travel: search 500+ UNESCO destinations by region and intent. This page covers its hosted endpoint (https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc).
Is the Wonders MCP server safe to use?
Wonders MCP scores 80 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 Wonders MCP server expose?
Wonders MCP exposes 4 tools: search_destinations, get_destination, list_destinations_by_region, get_posts_by_intent. Their descriptions and schemas cost roughly 543 tokens of context every time the server is loaded.
Does the Wonders MCP server require authentication?
No. We connected to Wonders MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wonders MCP server still maintained?
Wonders MCP 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.