# io.github.tickadoo/tickadoo-mcp (remote · mcp.tickadoo.com)

Search and book theatre, attractions, tours across 681 cities. 13,090+ products.

- Trust score: 73/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://mcp.tickadoo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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-08-03.

- **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**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5459 tokens (~218/item across 25 items; 23 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http tickadoo-tickadoo-mcp https://mcp.tickadoo.com/mcp
```

### Codex

```toml
[mcp_servers.tickadoo-tickadoo-mcp]
url = "https://mcp.tickadoo.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add tickadoo-tickadoo-mcp --url https://mcp.tickadoo.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tickadoo-tickadoo-mcp:
    url: "https://mcp.tickadoo.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "tickadoo-tickadoo-mcp": {
      "type": "http",
      "url": "https://mcp.tickadoo.com/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-08-03 (score 73, +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-08-01 (score 72, +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.

### 2026-07-31 (score 71, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-07-28 (score 68, +1)

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

### 2026-07-27 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (23)

### `search_experiences` (~770 tokens)

Use this when the user names a city plus a category, query, or filter set and wants a ranked list of bookable experiences. Returns products each with a stable product_id, plus name, slug, city, category, price, rating, review count, and tags. To show the results as visual cards, pass the product_id values from these results into render_experience_cards (experience_ids). Pair with get_experience_details for richer fields.

Input parameters:

- `category` (string): Category slug, e.g., "theatre", "tours", "museums", "attractions".
- `city` (string): City slug, e.g., "london", "new-york", "paris".
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `indoor_outdoor` (string): Setting filter. 'indoor' / 'outdoor' resolve via the products.tags column (~2,100 indoor and ~5,000 outdoor products are tagged in the catalogue). 'either' applies no filter.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `limit` (integer): Number of results to return (1-50). Default 10.
- `max_price` (number): Maximum price per person in the listed currency. A positive value applies a cap; 0 (or unset) means no price cap (unbounded).
- `min_rating` (number): Minimum aggregate rating on a 0-5 scale.
- `min_review_count` (integer): Minimum number of customer reviews. Use to filter out new or sparsely-reviewed products.
- `popular_only` (boolean): DEPRECATED: use restrict_to_top_rated. Alias for the destructive top-rated filter (rating >= 4.5 AND review_count >= 100). The name implies a sort hint but it is a hard WHERE clause. Existing callers…
- `query` (string): Free-text query matched against title, venue, and description.
- `restrict_to_top_rated` (boolean): DESTRUCTIVE FILTER. When true, hard-restricts results to products with rating >= 4.5 AND review_count >= 100. This is a WHERE clause, not a sort hint. Anything failing the floor is dropped from the r…
- `tags` (array): Filter by experience tags. Multiple tags are AND-combined (every tag must match) so adding more tags narrows the result set. Use lowercase singular forms; matching is substring-based against the tag…

Output parameters:

- `pagination` (object)
- `results` (array): Ranked bookable experiences.

### `search_local_experiences` (~546 tokens)

Use this when the user mentions a place, neighbourhood, landmark, or area but does not give exact coordinates. Examples: 'near the Louvre', 'in Trastevere', 'around Times Square', "walking distance from St Paul's Cathedral". Returns experiences matched first by exact venue/neighbourhood, then by city centre fallback. Do not use for general city-wide search; use search_experiences for that.

Input parameters:

- `city` (string): City slug or name to disambiguate. Recommended for any place_hint that could exist in multiple cities.
- `date_from` (string)
- `date_to` (string)
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `limit` (integer)
- `neighbourhood` (string): Optional: a known neighbourhood within the city to narrow results.
- `place_hint` (string, required): Free-text place reference: a landmark, neighbourhood, monument, station, or street name. E.g. 'Louvre Museum', 'Trastevere', 'Soho', 'Times Square'. Required.
- `radius_hint` (string): Optional: how broadly to interpret the place_hint. 'walking' is ~1km, 'short_drive' is ~5km, 'city_wide' falls back to the whole city. Default 'walking'.
- `tags` (array): Filter by experience tags. Multiple tags are AND-combined (every tag must match) so adding more tags narrows the result set. Use lowercase singular forms; matching is substring-based against the tag…

### `find_nearby_experiences` (~167 tokens)

Use this when a non-ChatGPT client supplies exact latitude and longitude and wants experiences near that coordinate. ChatGPT clients should use search_local_experiences instead because it accepts coarse place hints.

Input parameters:

- `category` (string): Optional category slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `latitude` (number, required): Latitude coordinate.
- `limit` (integer)
- `longitude` (number, required): Longitude coordinate.
- `radius_km` (number): Search radius in kilometres.

### `whats_on_tonight` (~210 tokens)

Use this when the user asks what is on in a city tonight. Returns evening-appropriate experiences currently on sale, with seasonal products filtered out and evening-led options ranked first. Top results carry start_time (venue-local) when the live supplier calendar confirms a performance in the evening window (late afternoon onward), and timed rows sort soonest-first; rows without start_time have no confirmed evening time. Confirm the selected experience with get_availability before stating it is bookable tonight.

Input parameters:

- `category` (string): Optional category slug to narrow results.
- `city` (string, required): City slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `max_results` (integer): Default 10, max 30.

Output parameters:

- `pagination` (object)
- `results` (array): Ranked bookable experiences.

### `get_last_minute` (~204 tokens)

Use this when the user wants something to do within the next few hours. Returns currently-on-sale experiences with seasonal products filtered out, ranked by popularity. Rows may include start_time, countdown_text, and seats_remaining hints when known, but none are guaranteed: confirm the selected experience with get_availability before stating it starts soon or is available today.

Input parameters:

- `city` (string, required): City slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `hours` (integer): How many hours ahead to look (1-12). Default 3.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `latitude` (number): Optional latitude to bias toward nearby venues.
- `longitude` (number): Optional longitude to bias toward nearby venues.

### `get_whats_on_this_week` (~137 tokens)

Use this when the user wants ideas for the coming week in a city. Returns a ranked list of currently on-sale experiences (search rows), not a day-by-day calendar. Assemble any weekly structure yourself and verify specific dates with get_availability.

Input parameters:

- `city` (string, required): City slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.

### `recommend_experiences` (~237 tokens)

Use this when the user describes what they want in natural language rather than naming a category. Parses the query for audience, mood, constraints, occasion, and time of day, then returns scored recommendations with a reason field explaining the match.

Input parameters:

- `city` (string): Optional city slug. If omitted, the city is parsed from the query.
- `date` (string): Optional ISO date (YYYY-MM-DD) for availability-aware ranking.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `limit` (integer): Number of recommendations to return (1-20). Default 5.
- `pax` (integer): Number of people. Default 2.
- `query` (string, required): Natural-language preference, e.g., "romantic evening in Paris under 100 euros" or "rainy day in Edinburgh with kids 8 and 12".

### `get_city_guide` (~136 tokens)

Use this when the user wants an orientation overview of a city for trip planning. Returns a ranked list of the city's most popular bookable experiences (search rows); derive the dominant categories and price levels from those rows rather than expecting a structured guide payload.

Input parameters:

- `city` (string, required): City slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.

### `get_travel_tips` (~158 tokens)

Use this when the user asks practical logistics questions about a city. Currently returns a ranked list of relevant bookable experiences (search rows); the topic filter is accepted but not yet applied, and the payload contains no tips text, emergency numbers, or phrases.

Input parameters:

- `city` (string, required): City slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `topic` (string): Optional topic filter. When omitted, returns a summary across all topics.

### `compare_experiences` (~137 tokens)

Use this when the user wants a side-by-side comparison of 2-5 specific products. Pass the slug for each. Returns a comparison table plus per-axis winners (value, rating, popularity, family-fit).

Input parameters:

- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `slugs` (array, required): Product slugs from earlier search or recommend results.

### `get_hidden_gems` (~164 tokens)

Use this when the user wants lower-profile options rather than headline bestsellers. Excludes Bestseller, hop-on-hop-off, and CityPass tagged products and prefers highly rated rows with fewer reviews; falls back to the standard ranked list when a city has too few qualifying rows (results may then overlap with headline search).

Input parameters:

- `city` (string, required): City slug.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `max_results` (integer): Default 5, max 20.

### `get_family_day` (~195 tokens)

Use this when the user wants family-suitable options for a day in one city. Returns a flat ranked list of family-appropriate experiences (search rows), not a structured morning/lunch/afternoon/evening plan. Compose the day yourself and verify age suitability per pick via get_experience_details.

Input parameters:

- `budget` (number): Optional max budget in the listed currency.
- `city` (string, required): City slug.
- `date` (string): Optional ISO date (YYYY-MM-DD).
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `kids_ages` (array): Children's ages. Drives age-suitability filtering on each slot.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.

### `get_date_night` (~205 tokens)

Use this when the user wants an evening for two. Returns a flat ranked list of evening-appropriate experiences (search rows), not a structured pre-dinner/dinner/show arc, and rows are not guaranteed couples-filtered. Compose the evening yourself (search_by_mood with mood 'romantic' can bias the pool).

Input parameters:

- `budget` (string): Budget band. 'low' = under 100 per person, 'medium' = 100-200, 'high' = 200+. In the listed currency.
- `city` (string, required): City slug.
- `date` (string): Optional ISO date (YYYY-MM-DD).
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.

### `plan_itinerary` (~282 tokens)

Use this when the user wants a multi-day plan for a single city. Returns a flat ranked candidate list of experiences (search rows), not structured day slots or a running cost. Arrange the candidates into days yourself and compute totals only from returned price fields.

Input parameters:

- `audience` (string): Target audience. Currently 'family' is the strongest signal in the catalogue (resolves via the 'family' tag, ~3,200 products). Other values are best-effort and may be sparsely populated; for guarante…
- `budget` (string): Budget band per day per person.
- `city` (string, required): City slug.
- `days` (integer, required): Number of days to plan (1-7).
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `interests` (string): Free-text interest seed, e.g., "history, food, river".
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `pace` (string): Itinerary density. relaxed = 1-2 stops per day, packed = 4-5.

### `list_cities` (~141 tokens)

Use this when the user wants to browse supported cities before searching. Returns city names, slugs, country codes, and product counts.

Input parameters:

- `country` (string): Optional country code or country name filter.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `limit` (integer): Maximum number of cities to return (1-50). Defaults to 50 when omitted.

### `get_experience_details` (~140 tokens)

Use this when the user selects a specific experience from search results and needs richer product, location, supplier, and booking fields. Accepts either product_id or slug.

Input parameters:

- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `product_id` (string): Stable product_id from a previous search result.
- `slug` (string): Product slug from a previous search result.

### `get_related_experiences` (~184 tokens)

Use this when a non-ChatGPT widget or client has a selected product_id and needs related products to pair with it, do after it, find nearby, or find similar alternatives. Returns cached graph and semantic related products for trio-style widgets.

Input parameters:

- `context` (string): Relationship type: pair, after, nearby, or similar.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `max_results` (integer): Number of related products to return. Default 6, max 10.
- `product_id` (string, required): Stable product_id or slug for the source experience.

### `get_availability` (~354 tokens)

Use this when the user is ready to check live bookable dates, times, prices, or remaining spaces for one selected product. This is the live supplier-check tool; pass product_id from search or slug plus city_slug. Slot price.amount is in MINOR currency units (pence/cents): amount 13125 with currency_code GBP means GBP 131.25. Slot time is venue-local; when the venue timezone is known, timezone carries its IANA name and datetime/next_available carry the real UTC offset (e.g. 2026-07-18T19:30:00+02:00), so they are safe for time math.

Input parameters:

- `as_of` (string): Previous ISO timestamp from stale card data; returns delta only when data changed.
- `city_slug` (string): City slug required when slug is used.
- `date_from` (string): Start date in YYYY-MM-DD. Defaults to today.
- `date_to` (string): End date in YYYY-MM-DD. Defaults to 14 days after date_from and is capped to a 365-day window.
- `fresh` (boolean): When true, bypasses the 60-second cache and performs a live supplier check, subject to rate limits.
- `idempotency_key` (string): Optional UUID. Reuse for identical responses within five minutes.
- `party_size` (integer): Number of guests. Default 2.
- `preferred_time` (string): Optional broad time preference such as morning, afternoon, or evening.
- `product_id` (string): Stable product_id from a search or details response. Preferred when available.
- `slug` (string): Product slug. Use with city_slug when product_id is unavailable.

### `check_availability` (~188 tokens)

Use this when the user has picked a specific experience and asks whether it is available on one date, what it costs for a party, or wants a booking link. This is the legacy-compatible date-specific availability interface.

Input parameters:

- `date` (string, required): Date to check in YYYY-MM-DD format.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `party_size` (integer): Number of guests or tickets to price. Default 2.
- `slug` (string, required): Product slug or legacy booking path, e.g. "london-dungeon-tickets" or "/london/london-dungeon-tickets".

### `search_by_mood` (~217 tokens)

Use this when the user describes the feeling or vibe they want rather than a category, such as romantic, relaxing, adventurous, family fun, foodie, luxury, or rainy day. Maps the mood to preset search filters and returns matching experiences.

Input parameters:

- `city` (string, required): City name or slug, e.g. "london", "new-york", or "paris".
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `limit` (integer): Maximum number of experiences to return (1-50). Defaults to the mood preset size when omitted.
- `mood` (string, required): Mood preset. Valid values: adventurous, romantic, relaxing, family_fun, cultural, thrill_seeking, foodie, budget_friendly, luxury, rainy_day.

### `get_transfer_info` (~180 tokens)

Use this when the user is arriving in a supported city and needs transfer guidance from an airport, station, or port to a hotel coordinate. Returns taxi, metro, bus, and train estimates with durations, costs, and directions.

Input parameters:

- `city` (string, required): Supported city: London, Paris, New York, Amsterdam, Barcelona, Rome, or Tokyo.
- `format` (string): Response shape. 'json' returns structured records; 'text' returns the same content rendered as a short narrative paragraph for chat surfaces.
- `from_type` (string, required): Arrival hub type.
- `language` (string): BCP-47 language code for human-readable fields (e.g., 'en', 'fr-FR'). Defaults to English when omitted.
- `to_latitude` (number, required): Hotel latitude.
- `to_longitude` (number, required): Hotel longitude.

### `render_experience_cards` (~272 tokens)

Use this immediately after ANY discovery or search tool (search_experiences, whats_on_tonight, get_last_minute, get_whats_on_this_week, recommend_experiences, search_by_mood, get_hidden_gems, get_family_day, get_date_night, search_local_experiences) returns results. It is the only tool that displays the visual experience cards, so always call it once for every result set you want shown. Take the experience_ids those tools provide and render them; pass the product_id values exactly as returned by those tools, never full product rows. Only experience_ids and render_type are required. Optionally pass render_context.intent_summary (a short phrase describing what the user asked for, e.g. city, date, audience) to set the carousel heading. Call it exactly once per result set, and do not also re-list the experiences as text.

Input parameters:

- `experience_ids` (array, required): The stable product_id values from search_experiences results (the product_id field of each returned row). Pass IDs only, never full product rows.
- `idempotency_key` (string): Optional UUID. Reuse for identical card render responses within five minutes.
- `render_context` (object)
- `render_type` (string, required): Visual layout requested for the widget.

Output parameters:

- `experience_ids` (array): The stable product ids rendered as cards.

### `report_quality_signal` (~175 tokens)

Use this to push a quality signal back to tickadoo about an experience or recommendation you previously surfaced. Examples: stale availability, a failed click-through, a supplier outage, or misleading content. Requires a real forward-event request_id returned within the last 30 days. Repeating the same signal for the same request is idempotent per caller.

Input parameters:

- `notes` (string): Optional free-text context. Required when signal_type is "other". Do not include PII.
- `request_id` (string, required): The request_id from a forward tool result in the last 30 days. Format: rq_YYYY_MM_DD_HHMMSS_<6-hex>.
- `signal_type` (string, required): The kind of issue you are reporting. Use "other" only when none of the specific types fit, and always include notes.

## Diagnostics

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

## Score history

- 2026-08-03: 73
- 2026-08-02: 72
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 68
- 2026-07-27: 67
- 2026-07-26: 66

## Links

- Remote endpoint: https://mcp.tickadoo.com/mcp
- Repository: https://github.com/tickadoo/tickadoo-mcp
- Changelog RSS feed: https://verifymcp.io/servers/tickadoo-tickadoo-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/tickadoo-tickadoo-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/tickadoo-tickadoo-mcp/mcp