# Aventuro (remote · mcp.aventuro.io)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.aventuro.io`: 71/100 (this document), [markdown](https://verifymcp.io/servers/io-aventuro-mcp/mcp.md), [page](https://verifymcp.io/servers/io-aventuro-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.aventuro.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.6`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http io-aventuro-mcp 'https://mcp.aventuro.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-aventuro-mcp": {
      "url": "https://mcp.aventuro.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-aventuro-mcp": {
      "type": "http",
      "url": "https://mcp.aventuro.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-aventuro-mcp]
url = "https://mcp.aventuro.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-aventuro-mcp": {
      "type": "remote",
      "url": "https://mcp.aventuro.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-aventuro-mcp --url 'https://mcp.aventuro.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-aventuro-mcp:
    url: "https://mcp.aventuro.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-aventuro-mcp": {
      "Transport": "http",
      "Url": "https://mcp.aventuro.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-aventuro-mcp -t streamable-http -u 'https://mcp.aventuro.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-aventuro-mcp": {
      "type": "http",
      "url": "https://mcp.aventuro.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 71, +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.

### 2026-10-16 (score 70, +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.

### 2026-10-15 (score 69, 0)

- [security] 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

### 2026-10-14 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-13 (score 68)

First indexed and scored.

## MCP tools (2)

### `find_places` (~657 tokens)

Find places

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.

Input parameters:

- `categories` (array): Only these categories. Empty means all.
- `detail` (string): brief: summary and top tips. full: the whole stored description.
- `lang` (string): Language of names and descriptions. Falls back to English per place.
- `lat` (number): Latitude of the search center, decimal degrees. Required (with lng) unless q is given.
- `limit` (integer): How many places to return (max 20, or 5 with detail=full).
- `lng` (number): Longitude of the search center, decimal degrees. Required (with lat) unless q is given.
- `needs` (array): Practical needs every result must meet.
- `parking` (string): Parking requirement.
- `q` (string): Free text: a city, country or place name, optionally with a category ("zoo valencia"). Required unless lat/lng are given.
- `radius_km` (number): Search radius in km around lat/lng. Out-of-range values are clamped. Ignored without lat/lng.
- `setting` (string): Indoor or outdoor.
- `tags` (array): Free-text themes (e.g. "castle", "sunset"). They only move matching places up; nothing is excluded.
- `tastes` (array): Who or what the place should suit.

Output parameters:

- `about_score` (string)
- `applied` (object)
- `count` (integer)
- `error` (object)
- `filter_semantics` (string)
- `hint` (string|null)
- `notes` (array)
- `places` (array)
- `resolved_as` (string)
- `search_area` (object|null)
- `truncated` (boolean)

### `get_place` (~320 tokens)

Get place details

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.

Input parameters:

- `detail` (string): full (default): the whole stored description. brief: summary and top tips.
- `lang` (string): Language of the name and description. Falls back to English.
- `slug` (string, required): The place: the last part of a find_places url (e.g. "old-fortress"), or that whole url.

Output parameters:

- `atmosphere` (string|null)
- `attributes` (object)
- `avoid` (string|null)
- `best_time` (string|null)
- `category` (string|null)
- `city` (string|null)
- `content_status` (string)
- `coordinates` (object)
- `country` (string|null)
- `distance_km` (number|null)
- `error` (object)
- `etiquette` (string|null)
- `facts` (array)
- `fallback_reason` (string|null)
- `images` (array)
- `landmarks` (string|null)
- `lang` (string)
- `matched_needs` (array)
- `matched_tags` (array)
- `matched_tastes` (array)
- `name` (string)
- `parking` (object)
- `photo_spot` (string|null)
- `schedule_notes` (string|null)
- `score` (integer|null)
- `setting` (string|null)
- `summary` (string|null)
- `tips` (array)
- `url` (string|null)
- `visit_minutes` (integer|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-aventuro-mcp/mcp#diagnostics

## Score history

- 2026-10-18: 71
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 68

## 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.

## Links

- Remote endpoint: https://mcp.aventuro.io/mcp
- Website: https://mcp.aventuro.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-aventuro-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-aventuro-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-aventuro-mcp/mcp