mcpbeat Sign in

Wonders MCP Server

by machupicchu Your server? Claim it
answering

Wonders MCP is answering right now. Last checked moments ago. It exposes 4 tools.

Read-only MCP for heritage travel: search 500+ UNESCO destinations by region and intent.

Uptime history 91 days of history · worst day 97%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
797 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

25 Sep a tool changed version
8 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check Wonders MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add wonders-mcp --transport http https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc
Settings → Connectors → Add custom connector, then paste this address
https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc
~/.codex/config.toml
[mcp_servers.wonders-mcp]
url = "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
.cursor/mcp.json
{
  "mcpServers": {
    "wonders-mcp": {
      "url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "wonders-mcp": {
      "type": "http",
      "url": "https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

destinations
list_destinations_by_region
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`.
search_destinations
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.
destination
get_destination
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.
posts
get_posts_by_intent
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.

Endpoints

URLTransportStateLatencyChecked
https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc streamable-http answering 762 ms 0 min ago

Alternatives to Wonders MCP

same job, measured the same way
P
PopUp Organizer
by usepopup

Read-only MCP server for PopUp — search vendors, manage events, and track applications.

48 installs/wk local only
rdrop for Raindrop.io
by kingpsychopath

Search Raindrop.io bookmarks and review tag and collection plans. Read-only MCP by default.

66 installs/wk local only
Burs-IA Tools
by soyeladice-svg

Free read-only tools for agents: agent-readiness audit, TLS/DNS/header checks, MCP search, utils.

47 tools answering
llmsmap.me International Directory
by arseniigruzdev

Read-only search and discovery for the international llms.txt directory maintained by llmsmap.me.

2 tools answering
NetTree Public
by tsingniao666

Read-only link-destination catalog for agents: search, get, and suggest public fit.

answering
Transcripted
by r3dbars

Read-only search over the meetings, dictations and writing saved by the Transcripted Mac app.

local only
Ivisa
by ivisa-www

Check visa requirements and travel documents for international travel destinations.

1 tools answering
unesco-heritage-mcp-server
by cyanheads

Search UNESCO World Heritage sites, intangible heritage, biosphere reserves, and Global Geoparks.

276 installs/wk 9 tools answering

Wonders MCP — questions

Answers built from our own checks of this server.

What can Wonders MCP do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_destination, get_posts_by_intent, list_destinations_by_region, search_destinations. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Wonders MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 797 ms. The bar chart above shows every period we have measured.
How do I connect Wonders MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Wonders MCP need an API key?
No. Wonders MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Wonders MCP?
It answers our handshake in 797 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.