Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Aventuro

REMOTE · MCP.AVENTURO.IO

Find travel places (sights, museums, parks, beaches) and read place cards. Read-only, no auth.

Available components

71 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1200 tokens (~600/item across 2 items; 2 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Changelog

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.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_places” rewrote its description, which is the text the model reads security
  • 14 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Oct 26 68

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Probed https://mcp.aventuro.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.aventuro.io CN=YE1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 65fec5885941c1c35a5bd197e6fee151d96
SANs: mcp.aventuro.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.aventuro.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
aventuro.io. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.aventuro.io/mcp Verified 200
http (plaintext) http://mcp.aventuro.io/mcp HTTPS enforced 301 https://mcp.aventuro.io/mcp
MCP tools · 2 exposed · ~977 tokens

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 →

Tool Tokens
find_places ~657

Use this when the user asks for places, parks, sights, museums, beaches or things to visit in a city, region or near a point. Finds interesting places (sights, museums, parks, nature, beaches and more), ordered by popularity. Returns name, category, city, country, coordinates, distance, a link to the place page (url), a popularity score, a stored travel description and one verified photo with its credit (image, or null). For more about one place, call get_place with the last part of its url. Give q (a place, city or country name, optionally with a category, e.g. "valencia" or "zoo valencia"), or lat/lng of the area the user asks about, or both (q narrowed to radius_km around lat/lng). Optional filters: categories, needs, tastes, parking, setting; tags only rank matching places higher. Write each place name as a markdown link [name](url) when url is present, and show each place's url as the source link. When image is present, show image.url as a markdown image with the author credit. visit_minutes is the typical time visitors spend there, not the time to see everything. attributes gives the five needs as true (known yes) or null (unknown, never a no), and matched_needs lists which of the requested needs the place has. setting (indoor, outdoor, both or null) and parking ({free, paid}, each true or null) follow the same rule. matched_tastes and matched_tags list which of the requested tastes and tags the place hit. content_status is no_description when no travel description is stored; fallback_reason is translation_unavailable when lang differs from the requested one. With q, search_area shows the area q was read as. filter_semantics says how the filters combine.

NameTypeReqDescription
categoriesarray–Only these categories. Empty means all.
detailstring–brief: summary and top tips. full: the whole stored description.
langstring–Language of names and descriptions. Falls back to English per place.
latnumber–Latitude of the search center, decimal degrees. Required (with lng) unless q is given.
limitinteger–How many places to return (max 20, or 5 with detail=full).
lngnumber–Longitude of the search center, decimal degrees. Required (with lat) unless q is given.
needsarray–Practical needs every result must meet.
parkingstring–Parking requirement.
qstring–Free text: a city, country or place name, optionally with a category ("zoo valencia"). Required unless lat/lng are given.
radius_kmnumber–Search radius in km around lat/lng. Out-of-range values are clamped. Ignored without lat/lng.
settingstring–Indoor or outdoor.
tagsarray–Free-text themes (e.g. "castle", "sunset"). They only move matching places up; nothing is excluded.
tastesarray–Who or what the place should suit.
NameTypeReqDescription
about_scorestring––
appliedobject––
countinteger––
errorobject––
filter_semanticsstring––
hintstring|null––
notesarray––
placesarray––
resolved_asstring––
search_areaobject|null––
truncatedboolean––

No examples provided.

get_place ~320

Use this when the user picks a place from find_places or asks to tell more about it: pass slug = the last part of that place's url (or the whole url). Returns the full details of one Aventuro place: name, category, city, country, coordinates, a link to the place page, the popularity score, the typical time visitors spend there in minutes (visit_minutes, not the time to see everything) and the whole stored travel description (facts, tips, best time, etiquette and more), plus up to 3 verified photos with author and licence credits (images, may be empty). Write the place name as a markdown link [name](url) when url is present and show the url as the source link. When images are present, show each images[].url as a markdown image with its author credit. attributes gives the five needs as true (known yes) or null (unknown, never a no); matched_needs, matched_tastes and matched_tags are always empty here. setting and parking follow the same true-or-null rule. content_status is no_description when no travel description is stored; fallback_reason is translation_unavailable when lang differs from the requested one.

NameTypeReqDescription
detailstring–full (default): the whole stored description. brief: summary and top tips.
langstring–Language of the name and description. Falls back to English.
slugstringyesThe place: the last part of a find_places url (e.g. "old-fortress"), or that whole url.
NameTypeReqDescription
atmospherestring|null––
attributesobject––
avoidstring|null––
best_timestring|null––
categorystring|null––
citystring|null––
content_statusstring––
coordinatesobject––
countrystring|null––
distance_kmnumber|null––
errorobject––
etiquettestring|null––
factsarray––
fallback_reasonstring|null––
imagesarray––
landmarksstring|null––
langstring––
matched_needsarray––
matched_tagsarray––
matched_tastesarray––
namestring––
parkingobject––
photo_spotstring|null––
schedule_notesstring|null––
scoreinteger|null––
settingstring|null––
summarystring|null––
tipsarray––
urlstring|null––
visit_minutesinteger|null––

No examples provided.

Install

How do I install the Aventuro MCP server?

Aventuro is a hosted endpoint at https://mcp.aventuro.io/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 · mcp.aventuro.io

# add to Claude Code
claude mcp add --transport http io-aventuro-mcp 'https://mcp.aventuro.io/mcp'
Common questions

What is the Aventuro MCP server?

Aventuro is an MCP server listed in the public MCP registry as io.aventuro/mcp. Find travel places (sights, museums, parks, beaches) and read place cards. Read-only, no auth. This page covers its hosted endpoint (https://mcp.aventuro.io/mcp).

Is the Aventuro MCP server safe to use?

Aventuro scores 71 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 Aventuro MCP server expose?

Aventuro exposes 2 tools: find_places, get_place. Their descriptions and schemas cost roughly 977 tokens of context every time the server is loaded.

Does the Aventuro MCP server require authentication?

No. We connected to Aventuro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Aventuro MCP server still maintained?

Aventuro is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.