# WonderKit Discover (remote · wonderkit.app)

Read-only city guides and public itineraries for family and group trips.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `wonderkit.app`: 84/100 (this document), [markdown](https://verifymcp.io/servers/app-wonderkit-discover/wonderkit.md), [page](https://verifymcp.io/servers/app-wonderkit-discover/wonderkit)

## Channel facts

- Endpoint: `https://wonderkit.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

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

- **Endpoint Security**: 83/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1324 tokens (~189/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 WonderKit Discover MCP server?

WonderKit Discover is a hosted endpoint at https://wonderkit.app/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 app-wonderkit-discover 'https://wonderkit.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-wonderkit-discover": {
      "url": "https://wonderkit.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-wonderkit-discover": {
      "type": "http",
      "url": "https://wonderkit.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-wonderkit-discover]
url = "https://wonderkit.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-wonderkit-discover --url 'https://wonderkit.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-wonderkit-discover:
    url: "https://wonderkit.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-wonderkit-discover": {
      "Transport": "http",
      "Url": "https://wonderkit.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-wonderkit-discover -t streamable-http -u 'https://wonderkit.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-wonderkit-discover": {
      "type": "http",
      "url": "https://wonderkit.app/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-11-03 (score 84, +1)

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

### 2026-11-01 (score 83, +1)

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

### 2026-10-30 (score 82, +1)

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

### 2026-10-28 (score 81, +1)

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

### 2026-10-26 (score 80, +1)

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

### 2026-10-24 (score 79, +1)

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

### 2026-10-21 (score 78, +1)

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

### 2026-10-19 (score 77, +1)

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

## MCP tools (7)

### `list_cities` (~62 tokens)

List cities

Use this when someone asks which cities WonderKit covers or needs a valid city key. Lists cities that have a published city guide of real things to do, with their keys. Reads public guides only; it cannot plan, save, or look up a private trip.

Output parameters:

- `cities` (array)
- `found` (boolean): false when the lookup did not resolve
- `hint` (string)
- `itinerariesUrl` (string): WonderKit itineraries for this city
- `matches` (array): Candidate cities when the name is ambiguous
- `nearest` (array): Covered cities in or near the asked-for area. Not the city that was asked for
- `note` (string): Read-only reminder; not user content
- `planDescription` (string): One line saying what planUrl opens
- `planUrl` (string): Guest planner link for the destination as asked; it plans any city
- `reason` (string): unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, …
- `region` (string): The state, country, or area the city ask was read as
- `suggestions` (array): Near-miss spellings, or same-name cities elsewhere, when the name is unknown
- `truncated` (boolean)

### `find_activities` (~149 tokens)

Find activities

Use this when someone asks what to do in one city: weekend ideas, events, food, or kid-friendly, date-night, or group activities. Returns published picks from the WonderKit city guide and the page URL. Returns single activities, not multi-day plans, and cannot see anyone's own trips.

Input parameters:

- `audience` (string): Who the plan is for: families, friends, or couples.
- `city` (string, required): City name or WonderKit city key, such as "Paris" or "paris-france".
- `query` (string): Optional words to match against activity titles and descriptions, such as "museums" or "dinner". Plurals match singulars.

Output parameters:

- `activities` (array)
- `audience` (string)
- `city` (string)
- `cityKey` (string)
- `found` (boolean): false when the lookup did not resolve
- `hint` (string)
- `itinerariesUrl` (string): WonderKit itineraries for this city
- `matches` (array): Candidate cities when the name is ambiguous
- `nearest` (array): Covered cities in or near the asked-for area. Not the city that was asked for
- `note` (string): Read-only reminder; not user content
- `pageUrl` (string): WonderKit page to cite
- `planDescription` (string): One line saying what planUrl opens
- `planUrl` (string): Guest planner link for the destination as asked; it plans any city
- `reason` (string): unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, …
- `region` (string): The state, country, or area the city ask was read as
- `suggestions` (array): Near-miss spellings, or same-name cities elsewhere, when the name is unknown
- `truncated` (boolean)

### `list_itineraries` (~153 tokens)

List itineraries

Use this when someone wants to browse WonderKit's public multi-day itineraries and place guides, for all cities or one city and audience. Plans that are in season this month come first. Each summary has dayCount (days or themed sections) and stopCount (anchors plus backups; before 2026-09-28 stopCount held the day count). Browses by city and audience only; it does not rank by a free-text description. Does not book or edit a trip.

Input parameters:

- `audience` (string): Who the plan is for: families, friends, or couples.
- `city` (string): City name or WonderKit city key, such as "Paris" or "paris-france".

Output parameters:

- `availableAudiences` (array)
- `city` (string)
- `cityKey` (string)
- `found` (boolean): false when the lookup did not resolve
- `hint` (string)
- `itineraries` (array)
- `itinerariesUrl` (string): WonderKit itineraries for this city
- `matches` (array): Candidate cities when the name is ambiguous
- `nearest` (array): Covered cities in or near the asked-for area. Not the city that was asked for
- `note` (string): Read-only reminder; not user content
- `planDescription` (string): One line saying what planUrl opens
- `planUrl` (string): Guest planner link for the destination as asked; it plans any city
- `reason` (string): unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, …
- `region` (string): The state, country, or area the city ask was read as
- `suggestions` (array): Near-miss spellings, or same-name cities elsewhere, when the name is unknown
- `truncated` (boolean)

### `search_itineraries` (~271 tokens)

Search itineraries

Use this when someone describes the trip they want, such as "romantic weekend in October", "museums with kids", or "Christmas markets", and needs matching public itineraries across cities. Ranks by the words they used, who it is for, and season fit. Pass a city to stay in one city. Do not use it to create or save a trip; it only reads published guides.

Input parameters:

- `audience` (string): Who the plan is for: families, friends, or couples.
- `city` (string): City name or WonderKit city key, such as "Paris" or "paris-france".
- `limit` (integer): How many results to return, up to 8.
- `month` (integer): Travel month, 1-12. Boosts plans whose peak months include it. Wins over season.
- `query` (string): What they want, in their words, such as "romantic weekend", "museums with kids", or "fall foliage". Plurals match singulars.
- `season` (string): Season they are travelling in. "now" means the current month. Northern-hemisphere seasons.
- `shape` (string): day-plan for a day-by-day plan, places-guide for a themed list of places.

Output parameters:

- `city` (string)
- `cityKey` (string)
- `found` (boolean): false when the lookup did not resolve
- `hint` (string)
- `itineraries` (array): Best match first
- `itinerariesUrl` (string): WonderKit itineraries for this city
- `matches` (array): Candidate cities when the name is ambiguous
- `nearest` (array): Covered cities in or near the asked-for area. Not the city that was asked for
- `note` (string): Read-only reminder; not user content
- `planDescription` (string): One line saying what planUrl opens
- `planUrl` (string): Guest planner link for the destination as asked; it plans any city
- `rankedFor` (object): The month or season used for the season-fit ranking
- `reason` (string): unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, …
- `region` (string): The state, country, or area the city ask was read as
- `suggestions` (array): Near-miss spellings, or same-name cities elsewhere, when the name is unknown
- `truncated` (boolean)

### `get_itinerary` (~166 tokens)

Get itinerary

Use this when someone wants the full plan for one public itinerary, by its slug: day-by-day or themed stops with real venues and map links, rainy-day and where-to-eat sections, and the best season. Returns dayCount and stopCount (anchors plus backups; before 2026-09-28 stopCount held the day count), the page URL, and planUrl, which opens the WonderKit planner prefilled from this plan. Read-only; it cannot change a plan.

Input parameters:

- `city` (string, required): City name or WonderKit city key, such as "Paris" or "paris-france".
- `slug` (string, required): Itinerary slug from list_itineraries or search_itineraries, such as "3-day-weekend-for-couples".

Output parameters:

- `audience` (string)
- `city` (string)
- `cityKey` (string)
- `dayCount` (number)
- `days` (array)
- `found` (boolean): false when the lookup did not resolve
- `hint` (string)
- `imageUrl` (string): Hero photo of the plan
- `itinerariesUrl` (string): WonderKit itineraries for this city
- `lastReviewed` (string)
- `lede` (string): One-line promise of the plan
- `markdownUrl` (string): The same plan as Markdown
- `matches` (array): Candidate cities when the name is ambiguous
- `nearest` (array): Covered cities in or near the asked-for area. Not the city that was asked for
- `note` (string): Read-only reminder; not user content
- `planDescription` (string): One line saying what planUrl opens
- `planUrl` (string): Give this to the person to plan this trip: the WonderKit planner prefilled from this itinerary
- `reason` (string): unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, …
- `region` (string): The state, country, or area the city ask was read as
- `season` (object)
- `sections` (array): Rainy-day backups, where to eat, and similar
- `shape` (string)
- `slug` (string)
- `stopCount` (number): Named stops (anchors plus backups), not days; see dayCount. Until 2026-09-28 this carried the day count
- `suggestions` (array): Near-miss spellings, or same-name cities elsewhere, when the name is unknown
- `summary` (string)
- `title` (string)
- `truncated` (boolean)
- `url` (string): WonderKit page to cite

### `plan_trip_link` (~191 tokens)

Plan trip link

Use this when someone wants to start planning their own trip to a destination in WonderKit. Returns one guest-planner link with the city (and vibe) filled in, plus a one-line description. It creates nothing and cannot book; the person adds dates and travelers in the planner. The link is a planner, not a citable guide page.

Input parameters:

- `city` (string, required): Destination as the person said it, such as "Lisbon" or "Asheville, NC". Any city works.
- `endDate` (string): Last day, YYYY-MM-DD, if they gave one.
- `kidsAges` (array): Ages of children travelling, if any.
- `startDate` (string): First day, YYYY-MM-DD, if they gave one.
- `travelers` (integer): How many people are going.
- `vibe` (string): The feel they want, if they said.

Output parameters:

- `description` (string): One line saying what the link opens
- `hint` (string)
- `notPrefilled` (array): Inputs the link cannot carry
- `url` (string): Guest planner link to give the person

### `continue_in_wonderkit` (~103 tokens)

Continue in WonderKit

Use this when someone wants to save, share, or keep working on a plan from a public guide or itinerary. Returns the WonderKit web links for that city guide, itinerary, and the guest planner. This server cannot save or share anything itself.

Input parameters:

- `city` (string): City name or WonderKit city key, such as "Paris" or "paris-france".
- `slug` (string): Optional itinerary slug to link a specific public plan.

Output parameters:

- `found` (boolean): false when the lookup did not resolve
- `guideList` (string)
- `hint` (string)
- `itinerariesUrl` (string): WonderKit itineraries for this city
- `links` (array)
- `matches` (array): Candidate cities when the name is ambiguous
- `nearest` (array): Covered cities in or near the asked-for area. Not the city that was asked for
- `note` (string): Read-only reminder; not user content
- `planDescription` (string): One line saying what planUrl opens
- `planUrl` (string): Guest planner link for the destination as asked; it plans any city
- `reason` (string): unknown_city, region_not_city, no_city_guide, no_itineraries_for_city, ambiguous_city, no_published_guide, no_matches, unknown_itinerary, lookup_failed, …
- `region` (string): The state, country, or area the city ask was read as
- `suggestions` (array): Near-miss spellings, or same-name cities elsewhere, when the name is unknown

## Diagnostics

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

## Score history

- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 75
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 74

## Common questions

### What is the WonderKit Discover MCP server?

WonderKit Discover is an MCP server listed in the public MCP registry as app.wonderkit/discover. Read-only city guides and public itineraries for family and group trips. This page covers its hosted endpoint (https://wonderkit.app/mcp).

### Is the WonderKit Discover MCP server safe to use?

WonderKit Discover scores 84 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 WonderKit Discover MCP server expose?

WonderKit Discover exposes 7 tools: list_cities, find_activities, list_itineraries, search_itineraries, get_itinerary, and 2 more. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.

### Does the WonderKit Discover MCP server require authentication?

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

### Is the WonderKit Discover MCP server still maintained?

WonderKit Discover is still listed as active in the MCP registry. We last reached this channel on 4 November 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://wonderkit.app/mcp
- Website: https://wonderkit.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-wonderkit-discover/wonderkit.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-wonderkit-discover/wonderkit.json
- HTML version of this page: https://verifymcp.io/servers/app-wonderkit-discover/wonderkit