Skip to content
CitedTravel logo

CitedTravel MCP server

Which MCP servers are CitedTravel's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to CitedTravel

Whose server it is
  • Registry namecom.citedtravel/citedtravelverified in the MCP registry

The registry name sits under citedtravel.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools9
  • Server calls itselfcitedtravel
  • Server version0.2.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 55 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Look up money, plugs and emergency numbers for a country; Answer traveler questions with dated, sourced facts; Check public holidays and tipping norms before a trip.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "Look up money, plugs and emergency numbers for a country", the likely first call is get_country_facts.
  • For "Answer traveler questions with dated, sourced facts", the likely first call is resolve_country.
  • For "Check public holidays and tipping norms before a trip", the likely first call is resolve_country.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer109 ms
  • Space in an agent's context≈ 4,472 tokensthe definitions of all its tools (9), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Look up money, plugs and emergency numbers for a country
  • can do · Answer traveler questions with dated, sourced facts
  • can do · Check public holidays and tipping norms before a trip

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers9 tools · read 2026-10-27
  • resolve_country

    Turns a country name, alias or code (English, Japanese, Chinese) into ISO codes: matches[] {iso2, iso3, name, score}, best first, max 5, empty if none. Call it first when you only have a name: get_country_facts, check_entry_requirements…

  • get_country_facts

    Several cited facts for one country in one call: power, currency, emergency numbers, driving side, this year's public holidays, tipping (data.<category>.<field>; a category without data is {}). Use it for a country overview. For one topic…

  • check_power_compatibility

    Does a traveller need a plug adapter or voltage converter? verdict {adapter: not_needed | needed | depends_on_plug, converter: not_needed | usually_not_needed | needed_for_single_voltage_devices | unknown, plug_fit[], frequency_note…

  • get_emergency_numbers

    Emergency numbers for one country: data.numbers.value {police, ambulance, fire, general, all_numbers}. A role without its own number is null: then use general, else all_numbers (in 58 countries only all_numbers is filled). Use it when…

  • get_tipping_norms

    Tipping customs for one country: data.norms.value {overall_context, situations {<situation>: {expectation, guidance_type, percent_min, percent_max}}}; percentages only where a source states them. Use it for "should I tip, and how much?"…

  • get_public_holidays

    National public holidays between two dates: data.holidays[] {date, name} by date, plus one citation per year in data.facts[]. Use it to check travel dates for closures and crowds; get_country_facts has this year's list with other facts…

  • check_entry_requirements

    Visa/entry information for a short tourist stay, for a pilot set of passports, from official government sources, with verbatim quotes, official links and a mandatory advisory. Decision support only: never a go/no-go verdict. Returns…

  • get_trip_brief

    Whole-trip brief for 1-5 destinations: per destination, in order, entry (as check_entry_requirements, if passport given), power verdict from home_country, currency, emergency numbers, driving side, tipping and holidays between from and…

  • list_recent_changes

    Dataset change feed, newest first: data[] {changed_on, fact_id, country, category, change: added | updated | removed, old_value, new_value, source_url}. Use it to refresh caches or alert users when a fact changes, then fetch the current…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "citedtravel": {
      "type": "http",
      "url": "https://citedtravel.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http citedtravel https://citedtravel.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://citedtravel.com/mcp as a custom connector in the settings.

OpenAPI spec

14 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.