Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ourway – Camino de Santiago

REMOTE · MCP.OURWAY.TRAVEL

Plan, quote & book the Camino de Santiago: routes, stages, live hotels, one package price, FAQ.

+3 this week 83 Trust /100

Last scanned (12 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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 Security74
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 8824 tokens (~519/item across 17 items; 14 tools + 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "camino_transfer_options" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +3
    • Schema quality: 436 → 519 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 2.1.1 → 2.1.2 functional
    • “create_camino_booking_proposal” reworded the description of “poblacion_inicio_id” cosmetic
    • “adjust_camino_package” reworded the description of “noche_num” cosmetic
    • “adjust_camino_package” reworded the description of “objetivo” cosmetic
    • “adjust_camino_package” reworded the description of “oferta_paquete_firmada” cosmetic
    • “camino_de_santiago_info” reworded the description of “idioma” cosmetic
    • “camino_de_santiago_info” reworded the description of “question” cosmetic
    • “camino_extras_catalog” reworded the description of “camino_slug” cosmetic
    • “camino_extras_catalog” reworded the description of “nacionalidad” cosmetic
    • “camino_hotel_alternatives” reworded the description of “noche_num” cosmetic
    • “camino_hotel_alternatives” reworded the description of “oferta_paquete_firmada” cosmetic
    • “camino_proposal_status” reworded the description of “codigo” cosmetic
    • “camino_route_towns” reworded the description of “camino_slug” cosmetic
    • “camino_transfer_options” reworded the description of “destino_poblacion_id” cosmetic
    • “camino_transfer_options” reworded the description of “fecha” cosmetic
    • “camino_transfer_options” reworded the description of “num_pasajeros” cosmetic
    • “camino_transfer_options” reworded the description of “origen_poblacion_id” cosmetic
    • “create_camino_booking_proposal” reworded the description of “camino_slug” cosmetic
    • “create_camino_booking_proposal” reworded the description of “cliente” cosmetic
    • “create_camino_booking_proposal” reworded the description of “formulario” cosmetic
    • “create_camino_booking_proposal” reworded the description of “idioma_codigo” cosmetic
    • “create_camino_booking_proposal” reworded the description of “oferta_paquete_firmada” cosmetic
    • “create_camino_booking_proposal” reworded the description of “poblacion_inicio_nombre” cosmetic
    • “list_camino_routes” reworded the description of “tipo” cosmetic
    • “plan_camino_itinerary” reworded the description of “camino_continuacion_slug” cosmetic
    • “plan_camino_itinerary” reworded the description of “camino_slug” cosmetic
    • “plan_camino_itinerary” reworded the description of “extender_hasta_id” cosmetic
    • “plan_camino_itinerary” reworded the description of “fecha_inicio” cosmetic
    • “plan_camino_itinerary” reworded the description of “km_max_etapa” cosmetic
    • “plan_camino_itinerary” reworded the description of “num_noches” cosmetic
    • “plan_camino_itinerary” reworded the description of “pernoctas_ids” cosmetic
    • “plan_camino_itinerary” reworded the description of “poblacion_destino_id” cosmetic
    • “plan_camino_itinerary” reworded the description of “poblacion_inicio_id” cosmetic
    • “plan_camino_itinerary” reworded the description of “ritmo” cosmetic
    • “plan_camino_itinerary” reworded the description of “solo_paso_final_id” cosmetic
    • “quote_camino_package” reworded the description of “camino_slug” cosmetic
    • “quote_camino_package” reworded the description of “categoria_alojamiento” cosmetic
    • “quote_camino_package” reworded the description of “etapas” cosmetic
    • “quote_camino_package” reworded the description of “extras_ids” cosmetic
    • “quote_camino_package” reworded the description of “habitaciones” cosmetic
    • “quote_camino_package” reworded the description of “incluir_mochila” cosmetic
    • “quote_camino_package” reworded the description of “mascotas” cosmetic
    • “quote_camino_package” reworded the description of “meal_plan” cosmetic
    • “quote_camino_package” reworded the description of “nacionalidad” cosmetic
    • “quote_camino_package” reworded the description of “presupuesto” cosmetic
    • “quote_camino_package” reworded the description of “residente_espana” cosmetic
    • “quote_camino_package” reworded the description of “solo_paso_final” cosmetic
    • “quote_camino_package” reworded the description of “traslados” cosmetic
    • “swap_camino_hotel” reworded the description of “alternativa_id” cosmetic
    • “swap_camino_hotel” reworded the description of “noche_num” cosmetic
    • “swap_camino_hotel” reworded the description of “oferta_paquete_firmada” cosmetic
    • “update_camino_package_extras” reworded the description of “camino_slug” cosmetic
    • “update_camino_package_extras” reworded the description of “extras_ids” cosmetic
    • “update_camino_package_extras” reworded the description of “incluir_mochila” cosmetic
    • “update_camino_package_extras” reworded the description of “nacionalidad” cosmetic
    • “update_camino_package_extras” reworded the description of “oferta_paquete_firmada” cosmetic
    • “update_camino_package_extras” reworded the description of “residente_espana” cosmetic
    • “update_camino_package_extras” reworded the description of “traslados” cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Oct 26 80
    • Tool “plan_camino_itinerary” rewrote its description, which is the text the model reads security
    • Tool “quote_camino_package” rewrote its description, which is the text the model reads security
    • “plan_camino_itinerary” added an optional parameter “camino_continuacion_slug” cosmetic
    • “plan_camino_itinerary” added an optional parameter “extender_hasta_id” cosmetic
    • “plan_camino_itinerary” added an optional parameter “solo_paso_final_id” cosmetic
    • “quote_camino_package” added an optional parameter “solo_paso_final” cosmetic
  • 20 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “camino_extras_catalog” rewrote its description, which is the text the model reads security
    • Tool “camino_hotel_alternatives” rewrote its description, which is the text the model reads security
    • Tool “camino_transfer_options” rewrote its description, which is the text the model reads security
    • New tool “update_camino_package_extras” functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.ourway.travel/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ourway.travel CN=YE2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA384 5c75b6c39f59680ec10da0feddaffc9a840
SANs: mcp.ourway.travel
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.ourway.travel. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
travel. DS published 589 8 Verified
ourway.travel. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ourway.travel/mcp Verified 200
http (plaintext) http://mcp.ourway.travel/mcp HTTPS enforced 301 https://mcp.ourway.travel/mcp
MCP tools · 14 exposed · ~5,239 tokens

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 →

Tool Tokens
adjust_camino_package ~293

Propose per-night hotel swaps on a quoted Camino de Santiago package to reach a goal: cheaper, higher category, closer to the town centre or with breakfast. `objetivo`: bajar_precio | subir_categoria | mas_centrico | con_desayuno; optional `noche_num` to limit to one night. Use it when the client asks to LOWER THE PRICE, UPGRADE, sleep MORE CENTRAL or ADD BREAKFAST — do not re-quote. Returns each proposal with its change in the total and the total if all are applied; apply accepted ones one by one with swap_camino_hotel, chaining the new offer. If there are no proposals, offer to re-quote with another category/itinerary. (es: ajustar_paquete)

NameTypeReqDescription
noche_num––Limit the proposals to this night of the package; omit to consider every night.
objetivostringyesGoal of the adjustment: bajar_precio (cheaper) | subir_categoria (upgrade) | mas_centrico (closer to the centre) | con_desayuno (with breakfast).
oferta_paquete_firmadastringyesThe latest `oferta_paquete_firmada` returned by quote_camino_package, swap_camino_hotel or update_camino_package_extras, passed verbatim.

Structured output declared, but exposes no named fields.

No examples provided.

camino_de_santiago_info ~401

Practical, up-to-date answers about the Camino de Santiago from Ourway's specialist team — use it for ANY Camino question even when the user is not booking: pilgrim credential (credencial), the Compostela certificate and the 100 km / 200 km rule, best time of year and weather, which route to choose (Camino Francés, Portugués Central or Coastal from Porto/Tui, Norte, Primitivo, Inglés from Ferrol, Vía de la Plata, Finisterre-Muxía), how many days from Sarria / Tui / Porto / Roncesvalles / Saint-Jean-Pied-de-Port / Oviedo, daily distances and difficulty, luggage & backpack transfer, what to pack, walking with kids or seniors, cycling the Camino, pets, accommodation types (albergues, hostales, hotels, casas rurales), budget, how far ahead to book, getting to the start and back from Santiago, safety, food (pilgrim menu) and etiquette. `question`: free text in any language; `idioma`: es | en (auto-detected if omitted). Cheap and instant (no availability check). / Respuestas prácticas del equipo Ourway sobre el Camino de Santiago: credencial, Compostela, 100 km, mejor época, qué ruta elegir, etapas, mochila, niños, bici, mascotas, presupuesto… Úsala ante cualquier duda sobre el Camino aunque el usuario no quiera reservar. (es: info_camino)

NameTypeReqDescription
idioma––Answer language: es | en. Auto-detected from the question if omitted.
questionstringyesThe pilgrim's question in free text, in any language (e.g. 'Do I need a credential?', '¿Cuántos días desde Sarria?').

Structured output declared, but exposes no named fields.

No examples provided.

camino_extras_catalog ~257

Official Ourway catalog of pilgrim extras for the Camino de Santiago: pilgrim credential (credencial), travel insurance, luggage / backpack transfer between stages, guided visits and activities. No unit prices (extras are folded into the package total via update_camino_package_extras(extras_ids=…) on a quoted package, or quote_camino_package(extras_ids=…) before quoting). `preseleccionado` marks the defaults (credential + insurance by nationality). Pass the route's `camino_slug` to get only the activities of the towns along that Camino (plus the generic pilgrim extras). The ONLY extras that may be offered. / Extras oficiales del catálogo, sin precio unitario y sin mostrar IDs; con `camino_slug`, solo las actividades de las poblaciones de ese camino. (es: catalogo_extras)

NameTypeReqDescription
camino_slug––Route slug from list_camino_routes; limits activities to towns along that Camino. Omit for the whole catalog.
nacionalidad––Customer's nationality or country of residence (e.g. Spain, ES, German); decides which insurance is preselected.

Structured output declared, but exposes no named fields.

No examples provided.

camino_hotel_alternatives ~255

Up to 3 alternative hotels for ONE night of a quoted Camino de Santiago package, of ANY accommodation category and as close as possible in price to the current one, each with the change in the package total (`variacion_total_eur`), room, meal plan and distance to the centre. Use it when the client wants a different hotel in a town — do NOT re-quote the whole trip. It checks live availability for that night, so it can find options even when the quote reported `alternativas_disponibles: 0` (takes a few seconds). Then apply the choice with swap_camino_hotel (`alternativa_id`). / Alternativas de cualquier categoría y de precio parecido para una noche; nunca precios por noche. (es: alternativas_alojamiento)

NameTypeReqDescription
noche_numintegeryesNight of the package to change (noche_num from the quote).
oferta_paquete_firmadastringyesThe latest `oferta_paquete_firmada` returned by quote_camino_package, swap_camino_hotel or update_camino_package_extras, passed verbatim.

Structured output declared, but exposes no named fields.

No examples provided.

camino_proposal_status ~115

Check the status of a Camino de Santiago booking proposal created through this channel (code PET-123): active / confirmed / expired, plus its link and deadline. Use it when the customer comes back asking about "my proposal", "my booking" or gives a PET code. / Estado de una propuesta creada por este canal. (es: estado_propuesta)

NameTypeReqDescription
codigostringyesProposal code in the form PET-123, as returned by create_camino_booking_proposal.

Structured output declared, but exposes no named fields.

No examples provided.

camino_route_towns ~170

Towns along a Camino de Santiago route in trail order (Sarria, Portomarín, O Cebreiro, Tui, Porto, Roncesvalles, Ferrol…), with id, name, cumulative km and GPS coordinates. Use it to pick the starting town (`poblacion_inicio_id` for plan_camino_itinerary), to check where the 100 km Compostela threshold falls, and to validate overnight stops. / Poblaciones de un camino en orden de trazado con km acumulados y coordenadas. Las etapas reservables las construye plan_camino_itinerary. (es: poblaciones_ruta)

NameTypeReqDescription
camino_slugstringyesCamino route slug from list_camino_routes (e.g. camino-frances).

Structured output declared, but exposes no named fields.

No examples provided.

camino_transfer_options ~315

Private transfer options to add to a Camino de Santiago package (e.g. Santiago airport or city → Sarria before the first stage, or back from the last town): one option per vehicle type with enough seats, with distance, duration and how much it ADDS to the package total (`variacion_total_eur`). Town ids come from camino_route_towns. To include one in an already quoted package, call update_camino_package_extras with the full `traslados` list ([{ origen_poblacion_id, destino_poblacion_id, fecha, categoria_id}]); before the first quote, pass it to quote_camino_package(traslados=…). / Opciones de traslado privado para añadir al paquete del Camino, con lo que suma cada una al total. Para incluirla en un paquete ya cotizado, update_camino_package_extras. (es: opciones_traslado)

NameTypeReqDescription
destino_poblacion_idintegeryesDrop-off town ID, from camino_route_towns (e.g. the first town of the itinerary).
fechastringyesTransfer date, YYYY-MM-DD, today or later.
num_pasajerosintegeryesNumber of passengers, 1-20 (usually every traveller).
origen_poblacion_idintegeryesPick-up town ID, from camino_route_towns (e.g. Santiago de Compostela before going to the first town).

Structured output declared, but exposes no named fields.

No examples provided.

camino_trip_intake_form ~157

Intake form contract for a tailor-made Camino de Santiago trip: the fields to collect conversationally from the customer BEFORE quoting anything (rooms with children's ages, nationality/residence, start date and nights, walking or cycling, route and starting town, daily pace, accommodation category, meal plan, luggage transfer, pets, budget per person, comments). Call it at the start of any planning request. / Espejo del formulario 'Camino a medida' de ourway.travel. No llames a quote_camino_package sin `presupuesto` ni a create_camino_booking_proposal sin los datos de contacto. (es: iniciar_peticion_medida)

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

create_camino_booking_proposal ~352

Create the Ourway booking request for a quoted Camino de Santiago package and return the customer's personal proposal link (valid 7 days) where they review the trip day by day, confirm and pay securely. ONLY call it after the customer explicitly approves the itinerary and the package total and gives real contact details (full name, email, phone, nationality). Accepts no prices: only the signed offer from quote_camino_package / swap_camino_hotel. / Crea la petición en Ourway y devuelve el enlace de la propuesta (única llamada a la acción). (es: crear_propuesta)

NameTypeReqDescription
camino_slugstringyesRoute slug from list_camino_routes (e.g. camino-frances).
cliente–yesCustomer's real contact details: full name, email, phone with international prefix and nationality.
formulario–yesThe intake form answers collected with camino_trip_intake_form (rooms, travel type, itinerary, category, meal plan, budget, luggage, contact preference, comments).
idioma_codigostringyesLanguage of the proposal and its emails as a 2-letter code, the customer's language (e.g. es, en).
oferta_paquete_firmadastringyesThe latest `oferta_paquete_firmada` returned by quote_camino_package, swap_camino_hotel or update_camino_package_extras, passed verbatim. Prices are taken only from it.
poblacion_inicio_id––Starting town ID from camino_route_towns (preferred over poblacion_inicio_nombre).
poblacion_inicio_nombre––Starting town name, only when its ID is unknown.

Structured output declared, but exposes no named fields.

No examples provided.

list_camino_routes ~220

List the Camino de Santiago routes Ourway sells and can book: Camino Francés (French Way), Camino Portugués (Central & Coastal), Camino del Norte, Camino Primitivo, Camino Inglés, Vía de la Plata / Sanabrés, Finisterre-Muxía and more, with slug, name and total km. Start here for any Camino de Santiago trip question ("which Camino should I walk?", "routes from Porto / Sarria / Tui"). `tipo`: a_pie (walking) | en_bicicleta (cycling) | a_caballo. / Lista los Caminos de Santiago que Ourway comercializa: solo estos son reservables. El itinerario reservable lo construye plan_camino_itinerary. (es: listar_caminos)

NameTypeReqDescription
tipostring–How the pilgrim travels: a_pie (walking, default) | en_bicicleta (cycling) | a_caballo (on horseback).

Structured output declared, but exposes no named fields.

No examples provided.

plan_camino_itinerary ~889

Build a day-by-day Camino de Santiago itinerary (walking stages, km per day, overnight towns, dates, route map image) following the camino's OFFICIAL stages adapted to the pilgrim's daily pace. Use it for any Camino itinerary, stage plan or "how many days from Sarria/Tui/Porto/Roncesvalles" question: it is the itinerary Ourway books. `ritmo`: tranquilo (18-22 km/day) | medio (22-28) | experimentado (28-35); use `km_max_etapa` instead for an explicit km cap or cycling (~2x). `fecha_inicio` (YYYY-MM-DD, first night) is optional: without it dates come back "to be confirmed" — call it anyway. Only pass `num_noches` when the client fixes the number of nights. Each stage lists `alternativas_pernocta`: nearby towns where the client could sleep instead; to apply a change call again with `pernoctas_ids` (the overnight town of EVERY night, in walking order; repeat a town on consecutive nights for a rest day). Optional edits, all requiring `pernoctas_ids`: `solo_paso_final_id` = town reached walking on the last day without sleeping there; `extender_hasta_id` = extend the trip beyond the last stop up to that town (the new part is split at the pace); `camino_continuacion_slug` = route continuing after the goal (only `camino-finisterre-muxia`, starting in Santiago). Each stage has `tipo` (marcha | descanso | solo_paso), `dia_num`, `noche_num` (null on the arrival without night) and `intermedias` (towns inside the stage where to stop earlier); `continuaciones` lists where the trip can be extended. Returns `mapa_url`: a real PNG map of the route with numbered overnight stops — show it in the chat right after the stage table (`![Mapa](mapa_url)`). / Fuente del itinerario reservable: úsala para proponer o revisar etapas, aunque el cliente aún no tenga fecha. Presenta el…

NameTypeReqDescription
camino_continuacion_slug––Requires pernoctas_ids. Route that continues after the goal; only camino-finisterre-muxia (from Santiago).
camino_slugstringyesCamino route slug from list_camino_routes (e.g. camino-frances).
extender_hasta_id––Requires pernoctas_ids. Extend the trip beyond the last stop up to this town ID (see `continuaciones`); the new part is split at the pace.
fecha_inicio––Date of the first night, YYYY-MM-DD. Optional: without it dates come back 'to be confirmed'.
km_max_etapa––Explicit cap in km per day (a client's own limit, or ~2x the walking pace when cycling). Overrides ritmo.
num_noches––Number of nights, ONLY when the client fixes it. Omit it and the stages follow the official route and the pace.
pernoctas_ids––Overnight town ID of EVERY night in walking order, to apply changes (alternativas_pernocta); repeat a town on consecutive nights for a rest day.
poblacion_destino_id––ID of the final town, from camino_route_towns. Omit to walk to the end of the route (usually Santiago de Compostela).
poblacion_inicio_idintegeryesID of the starting town (where the first night is spent), from camino_route_towns.
ritmo––Daily walking pace: tranquilo (18-22 km/day) | medio (22-28) | experimentado (28-35). Ignored if km_max_etapa is given.
solo_paso_final_id––Requires pernoctas_ids. Town reached walking on the last day without sleeping there (arrival without night).

Structured output declared, but exposes no named fields.

No examples provided.

quote_camino_package ~1,156

Quote a complete Camino de Santiago trip as ONE all-in package price (hotels night by night with LIVE availability + pilgrim extras) — the source of the official Ourway package price. Use it whenever the user asks how much a Camino costs, wants a quote, or approves an itinerary from plan_camino_itinerary. It auto-selects the best accommodation for each night (Ourway quality filters: verified meal plan, close to the centre, guest rating) and returns a single `total_paquete_eur`. NEVER returns per-hotel, per-night or per-extra prices. `presupuesto` is REQUIRED (per person, whole trip, EUR): sin_preferencia | lt_500 | 500_1000 | 1000_1500 | gt_1500. `meal_plan`: RO | BB | HB | FB. `categoria_alojamiento`: recomendado | hoteles_encanto | casas_rurales | albergues. `extras_ids` from camino_extras_catalog (default: pilgrim credential + insurance; luggage transfer if incluir_mochila=true, one bag per traveller, priced by Ourway as bags × official stages of the Camino covered, so a day that spans two official stages counts two; pass the route's `camino_slug` from plan_camino_itinerary). `traslados`: private transfers chosen from camino_transfer_options (arrival to the first town, return from the last…); their price goes inside the total and they are listed in `traslados_incluidos`. `etapas` = one entry per night; consecutive nights in the same town (rest day) get the same hotel. `solo_paso_final` = arrival without night from plan_camino_itinerary ({poblacion_id, fecha} with fecha = check-out of the last night): no hotel, but the luggage transfer covers that last stage. ALWAYS pass `nacionalidad` (or `residente_espana`): it sets the insurance. `mascotas=true` when travelling with a pet. If a category has no availability one night the best alternative category is chosen…

NameTypeReqDescription
camino_slug––Route slug from plan_camino_itinerary; needed to price the luggage transfer by official stages.
categoria_alojamientostring–Accommodation category: recomendado (default) | hoteles_encanto | casas_rurales | albergues.
etapasarrayyesOne entry per night (1-30) from plan_camino_itinerary: noche_num, poblacion_id, fecha_entrada, fecha_salida. Consecutive nights in the same town get the same hotel.
extras_ids––suplemento_id values from camino_extras_catalog. Omit for the defaults (pilgrim credential + insurance by nationality).
habitacionesarrayyesRooms (1-4), each with its adults and children's ages.
incluir_mochilaboolean–true to add luggage transfer between stages (one bag per traveller, priced by official stages covered).
mascotasboolean–true when travelling with a pet: filters for hotels that accept pets (unconfirmed cases are flagged in `avisos`).
meal_planstring–Meal plan: RO (room only) | BB (breakfast, default) | HB (half board) | FB (full board).
nacionalidad––Customer's nationality or country of residence, free text or ISO code (e.g. Spain, ES, German). Sets the included travel insurance; pass it or `residente_espana`.
presupuestostringyesREQUIRED budget per person for the whole trip, in EUR: sin_preferencia | lt_500 | 500_1000 | 1000_1500 | gt_1500.
residente_espana––true if the travellers live in Spain, false otherwise; overrides `nacionalidad` when choosing the insurance.
solo_paso_final––Arrival without night from plan_camino_itinerary: {poblacion_id, fecha} with fecha = check-out of the last night. No hotel; the luggage transfer covers that stage.
traslados––Private transfers chosen from camino_transfer_options, each {origen_poblacion_id, destino_poblacion_id, fecha, categoria_id}. Omit or [] for none.

Structured output declared, but exposes no named fields.

No examples provided.

swap_camino_hotel ~204

Apply one alternative from camino_hotel_alternatives or adjust_camino_package to a quoted Camino de Santiago package and get a NEW signed offer (`oferta_paquete_firmada`) with the new package total. Always use the most recent offer for create_camino_booking_proposal. / Sustituye el hotel de esa noche y devuelve una nueva oferta firmada con el nuevo total. (es: cambiar_alojamiento)

NameTypeReqDescription
alternativa_idstringyesalternativa_id of the option chosen, as returned by camino_hotel_alternatives or adjust_camino_package for that night.
noche_numintegeryesNight whose hotel is replaced (the noche_num of the chosen alternative).
oferta_paquete_firmadastringyesThe latest `oferta_paquete_firmada` returned by quote_camino_package, swap_camino_hotel or update_camino_package_extras, passed verbatim.

Structured output declared, but exposes no named fields.

No examples provided.

update_camino_package_extras ~455

Change the pilgrim extras, private transfers or luggage transfer of an ALREADY QUOTED Camino de Santiago package, keeping the same hotels night by night: no new availability check, answers in a few seconds. Pass the COMPLETE new selection: `extras_ids` (from camino_extras_catalog; omit for the default credential + insurance), `traslados` (from camino_transfer_options; omit or [] for none) and `incluir_mochila`. Returns the same shape as quote_camino_package with the new single `total_paquete_eur` and a NEW `oferta_paquete_firmada` that replaces the previous one. Use it instead of quote_camino_package whenever only extras or transfers change. / Añade o quita extras y traslados del paquete ya cotizado sin volver a cotizar los hoteles. (es: actualizar_extras_paquete)

NameTypeReqDescription
camino_slug––Route slug from plan_camino_itinerary; needed to price the luggage transfer by official stages.
extras_ids––COMPLETE new list of suplemento_id values from camino_extras_catalog. Omit for the defaults (pilgrim credential + insurance by nationality).
incluir_mochilaboolean–true to add luggage transfer between stages (one bag per traveller, priced by official stages covered).
nacionalidad––Customer's nationality or country of residence, free text or ISO code (e.g. Spain, ES, German). Sets the included travel insurance; pass it or `residente_espana`.
oferta_paquete_firmadastringyesThe latest `oferta_paquete_firmada` returned by quote_camino_package, swap_camino_hotel or update_camino_package_extras, passed verbatim.
residente_espana––true if the travellers live in Spain, false otherwise; overrides `nacionalidad` when choosing the insurance.
traslados––COMPLETE new list of private transfers from camino_transfer_options, each {origen_poblacion_id, destino_poblacion_id, fecha, categoria_id}. Omit or [] for none.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Ourway – Camino de Santiago MCP server?

Ourway – Camino de Santiago is a hosted endpoint at https://mcp.ourway.travel/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 · mcp.ourway.travel

# add to Claude Code
claude mcp add --transport http travel-ourway-camino-de-santiago 'https://mcp.ourway.travel/mcp'
Common questions

What is the Ourway – Camino de Santiago MCP server?

Ourway – Camino de Santiago is an MCP server listed in the public MCP registry as travel.ourway/camino-de-santiago. Plan, quote & book the Camino de Santiago: routes, stages, live hotels, one package price, FAQ. This page covers its hosted endpoint (https://mcp.ourway.travel/mcp).

Is the Ourway – Camino de Santiago MCP server safe to use?

Ourway – Camino de Santiago scores 83 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 Ourway – Camino de Santiago MCP server expose?

Ourway – Camino de Santiago exposes 14 tools: camino_de_santiago_info, list_camino_routes, camino_route_towns, plan_camino_itinerary, quote_camino_package, and 9 more. Their descriptions and schemas cost roughly 5,239 tokens of context every time the server is loaded.

Does the Ourway – Camino de Santiago MCP server require authentication?

No. We connected to Ourway – Camino de Santiago without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ourway – Camino de Santiago MCP server still maintained?

Ourway – Camino de Santiago is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ourway – Camino de Santiago MCP server?

VerifyMCP ran 13 checks on Ourway – Camino de Santiago, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.