WonderKit Discover
REMOTE · WONDERKIT.APP
Read-only city guides and public itineraries for family and group trips.
Available components
Last scanned (19 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
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 4 Nov 2026 · Probed https://wonderkit.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wonderkit.app | CN=WR3,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | b88238acebc4db220a9e68b5864ff69a |
| SANs: wonderkit.app, www.wonderkit.app | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of wonderkit.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| wonderkit.app. | present | 12812 | 8 | Verified |
| wonderkit.app. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(self), camera=(), microphone=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wonderkit.app/mcp | Verified | 200 | |
| http (plaintext) | http://wonderkit.app/mcp | HTTPS enforced | 301 | https://wonderkit.app/mcp |
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 →
continue_in_wonderkit Continue in WonderKit ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | – | false when the lookup did not resolve |
| guideList | string | – | – |
| hint | string | – | – |
| itinerariesUrl | string | – | WonderKit itineraries for this city |
| links | array | yes | – |
| 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 | yes | 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 |
No examples provided.
find_activities Find activities ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Who the plan is for: families, friends, or couples. |
| city | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No examples provided.
get_itinerary Get itinerary ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name or WonderKit city key, such as "Paris" or "paris-france". |
| slug | string | yes | Itinerary slug from list_itineraries or search_itineraries, such as "3-day-weekend-for-couples". |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No examples provided.
list_cities List cities ~62
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No examples provided.
list_itineraries List itineraries ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No examples provided.
plan_trip_link Plan trip link ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | One line saying what the link opens |
| hint | string | – | – |
| notPrefilled | array | – | Inputs the link cannot carry |
| url | string | yes | Guest planner link to give the person |
No examples provided.
search_itineraries Search itineraries ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No examples provided.
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.
remote · wonderkit.app
claude mcp add --transport http app-wonderkit-discover 'https://wonderkit.app/mcp'
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.