Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Travel Agent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Travel Agent MCP with free travel tools plus live x402 Travel Pulse, day-trip, weekend, creator, weather, and mobility services.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user travel-agent-mcp '--' npx -y @forgemeshlabs/travel-agent-mcp
# 2 — ask your agent for something these tools do
# list_tools, list_travel_categories, plan_flight_route and 12 more
Travel Agent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Travel Agent as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user travel-agent-mcp '--' npx -y @forgemeshlabs/travel-agent-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take TRAVEL_AGENT_SERVER_URL (Optional ForgeMesh travel-agent backend base URL override. Defaults to https://travel-agent.forgemesh.io.) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
FREE. Lists every paid travel-agent tool with its live price, so an agent can pick before paying. Fetches GET /menu from the backend with no payment; the backend may attach a labeled sponsored data field, passed through untouched.
No parameter schema on file.
FREE live category guide from the ForgeMesh travel-agent backend. Use this first to see the available travel flows and choose the next useful call: free airport/timing/coverage tools or paid x402 planning services. Read-only, no account setup, no booking side effects.
No parameter schema on file.
Plan one flight route between two airports. Use when a traveler wants a clear starting point for a specific origin and destination; use compare_airport_routes for multiple route choices, create_booking_link only when route details are already known, and get_airport_details only to validate one…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Origin airport IATA code (e.g. 'LAX', 'JFK'). Case-insensitive. |
| destination | string | yes | Destination airport IATA code (e.g. 'LHR', 'NRT'). Case-insensitive. |
| departure_date | string | no | Departure date in YYYY-MM-DD format. Optional — omit for open date searches. |
| return_date | string | no | Return date in YYYY-MM-DD format. Omit for one-way trips. |
| currency | string | no | ISO 4217 currency code (default: USD). Used in booking link parameters. |
FREE look up details for one airport by IATA code. Use to validate or explain a single airport before route planning; use plan_flight_route for an actual trip route and compare_airport_routes for multiple origin-destination pairs. Read-only, no account setup, no external booking links, and no…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Three-letter IATA airport code (e.g. 'SFO'). Case-insensitive. |
Compare two or more airport route pairs side by side. Use when a traveler is choosing between alternate origins, destinations, or nearby airports; use plan_flight_route for one dated route and get_airport_details for a single airport lookup. Read-only, no account setup, no booking side effects.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| routes | array | yes | Array of route pairs to compare. Minimum 1, typically 2-5. |
Create an external booking link for an already chosen route. Use after route details are known or after compare_airport_routes or plan_flight_route; use another planning tool first when the traveler still needs help choosing. Read-only, no account setup, no booking completion, and no reservation…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | no | Origin IATA code (e.g. 'IAH'). Case-insensitive. |
| destination | string | no | Destination IATA code (e.g. 'CDG'). Case-insensitive. |
| departure_date | string | no | Departure date in YYYY-MM-DD format. Optional. |
| return_date | string | no | Return date in YYYY-MM-DD format. Optional — omit for one-way. |
| currency | string | no | ISO 4217 currency code (default: USD). |
FREE practical travel timing advice, including booking windows, airport arrival timing, layovers, and seasonal considerations. Use for questions like when to book or how early to arrive; use plan_flight_route when the traveler wants route planning. Read-only, no account setup, no external booking…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | no | Origin IATA code. Optional — used to determine if route is international. |
| destination | string | no | Destination IATA code. Optional — used to determine if route is international. |
FREE live reference-rate currency conversion from the ForgeMesh travel-agent backend. Use when a traveler or agent needs quick spending context before deciding whether to ask for richer x402 trip guidance. Read-only, no account setup, no payment, and not a transaction quote.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount | number | no | Amount to convert. Default: 1. |
| from | string | yes | Source ISO 4217 currency code, such as USD. |
| to | string | yes | Target ISO 4217 currency code, such as EUR. |
| date | string | no | Optional reference date in YYYY-MM-DD format when supported by the backend. |
Connect to the live paid x402 creator-experience service for travelers, creators, influencers, and agents planning a shareable day trip, weekend, layover, or destination story. Use when the traveler cares about visuals, story, timing, food stops, scenic movement, weather-aware backups, or content…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Destination, city, region, route, or place the influencer experience should be built around. |
| trip_length | string | no | Trip length, such as day trip, 24 hours, weekend, layover, or 3 days. Default: day trip. |
| content_style | string | no | Desired style, such as cinematic, cozy, budget, food-focused, outdoorsy, romantic, luxury, hidden-gem, or short-form video. |
| budget | string | no | Budget preference, such as free, low-cost, mid-range, luxury, or a specific amount. |
| audience | string | no | Who the content should speak to, such as couples, solo travelers, families, students, food lovers, or weekend explorers. |
| mobility | string | no | Mobility or pace preference, such as easy walking, stroller-friendly, low stairs, car-free, or relaxed. |
| season | string | no | Season, month, weather context, or event timing. |
| must_include | array | no | Optional list of moments or constraints to include. |
| avoid | array | no | Optional list of things to avoid. |
Connect to the live paid x402 day-trip service for a destination, route, or origin-based ask. Use when a traveler wants a relaxed day out with timing, water, food, transit, weather, and backup options. The MCP can return live server output or x402 request metadata for clients that can pay with x402.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | no | — |
| destination | string | no | — |
| lat | string | no | — |
| lon | string | no | — |
| radius_miles | string | no | — |
| max_distance_or_travel_time | string | no | — |
| date | string | no | — |
| time_window | string | no | — |
| transportation_modes | string | no | — |
| interests | string | no | — |
| theme | string | no | — |
| content_style | string | no | — |
| budget | string | no | — |
| include_local_context | boolean | no | — |
Connect to the live paid x402 weekend-getaway service for a short overnight escape. Use when the traveler wants a calmer planning brief with lodging posture, water/weather fit, transportation, and easy backup ideas. The MCP can return live server output or x402 request metadata for clients that…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | no | — |
| destination | string | no | — |
| lat | string | no | — |
| lon | string | no | — |
| start_date | string | no | — |
| end_date | string | no | — |
| transportation_modes | string | no | — |
| max_distance_or_travel_time | string | no | — |
| budget | string | no | — |
| lodging_style | string | no | — |
| trip_style | string | no | — |
| destination_currency | string | no | — |
Connect to the live paid x402 weather-aware planning service for a destination or coordinate pair. Use when the traveler wants rain, heat, wind, and indoor backup awareness before committing to outdoor time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | no | — |
| lat | string | no | — |
| lon | string | no | — |
| date | string | no | — |
| time_window | string | no | — |
| plan_type | string | no | — |
| transportation_modes | string | no | — |
| max_distance_or_travel_time | string | no | — |
Connect to the live paid x402 mobility-options service for a location and transportation type. Use when the traveler wants transit, rail, ferry, trails, bike/scooter options, or a location-filtered short list before planning the rest of the trip.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| location | string | no | — |
| transportation_type | string | no | — |
| trip_style | string | no | — |
| origin | string | no | — |
| destination | string | no | — |
Check for travel disruptions before departure or during a trip with the live paid x402 Travel Pulse service. Each $0.01 call is one on-demand disruption and emergency-awareness check: an agent can run it before the traveler leaves, then call it again during the trip if the user wants hourly,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | no | Destination, city, region, route, airport area, or place to check. |
| origin | string | no | Optional origin or route start. |
| lat | string | no | Latitude for a point-specific pulse check. |
| lon | string | no | Longitude for a point-specific pulse check. |
| trip_date | string | no | Trip date in YYYY-MM-DD format, if known. |
| time_window | string | no | Relevant window, such as before departure, next 3 hours, today, overnight, or during trip. |
| check_reason | string | no | Why the agent is checking, such as pre_trip, repeat_trip_check, weather_shift, event_day, or traveler_check_in. |
| water_site | string | no | Optional water gauge/site id when the traveler cares about flood or river context. |
FREE live backend call for requesting coverage for a town, neighborhood, local ritual, free experience, or source set. Use this when you want the system to remember a place worth watching: local vibe, freebie list, sunset walk, opening-soon pattern, or creator angle.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| town | string | no | — |
| location | string | no | — |
| destination | string | no | — |
| state | string | no | — |
| country | string | no | — |
| county | string | no | — |
| neighborhood | string | no | — |
| signal_types | string | no | — |
| source_links | string | no | — |
| creator_angle | string | no | — |
| content_style | string | no | — |
| contact | string | no | — |
| notes | string | no | — |
| recheck_days | number | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Travel Agent or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_tools | no tags | |
| list_travel_categories | no tags | |
| plan_flight_route | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_airport_details | no tags | |
| compare_airport_routes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_booking_link | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_travel_timing_advice | no tags | |
| convert_currency | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| creator_experiences | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_day_trip | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_weekend_getaway | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| plan_weather_aware_trip | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| find_transit_options | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_trip_disruptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| request_local_coverage | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.5. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Travel Agent can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.