Robin Saige we check the tools AI agents call

Wonders MCP

org.machupicchu/wonders-mcp

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

— the operator's own registry description reported

Publisher org.machupicchu · first seen 2026-08-12 · endpoint https://www.machupicchu.org/wp-json/wonders-mcp/v1/jsonrpc

allow
verdict
thin-slow-solo
cluster
ok_tools
answers
4
tools served

Dependency rating derived

allow — thin-slow-solo — safe to depend on

Cluster thin-slow-solo · distinctiveness 0.368 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency378 ms
vs populationslow
protocolcurrent
authopen
Use — can it use it?
tools4
vs populationmid
capabilities2
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_99a2a11353cca63326edf0a6 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

get_destination get_posts_by_intent list_destinations_by_region search_destinations

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific4/4
has a description4/4
description is substantive4/4

4 of 4 tools graded · no input schema captured yet — parameter checks await the next probe cycle, so this grade so far reflects name + description only. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
1.1.2
server version wonders-mcp

Capabilities: resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T20:00:36Zok_tools2003782025-06-18
2026-08-12T05:35:52Zok_tools2004612025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/org.machupicchu/wonders-mcp.svg)](https://robinsaige.com/s/org.machupicchu/wonders-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview