Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
AlgoTrips 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.
93/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Plan priced day-by-day trips: flights, hotels, activities and transfers. Book on algotrips.com.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http algotrips-mcp https://api.algotrips.com/mcp
# 2 — ask your agent for something these tools do
# destination_facts, my_trips, plan_trip and 2 more
AlgoTrips costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ALAll 1 server
algotrips1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http algotrips-mcp https://api.algotrips.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 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.
Facts about a travel destination (a city or region) from the AlgoTrips destination guides: country, a short overview, what the full guide covers, and links to the guide and to plan a trip there when available. If the place is not found, it names close matches to try instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| place | string | yes | A city or region, for example "Kyoto" or "Bali". |
The signed-in AlgoTrips account's 10 most recent trips, newest first: title, cities, dates, status and a link to open each one on AlgoTrips. Needs the person to be signed in to AlgoTrips.
No parameter schema on file.
Builds a full day-by-day trip with live prices in the signed-in AlgoTrips account: flights from the home city (unless gettingAround is none), hotels, activities and transfers for each city, for the cities, start date, travellers and home city given. The kind of hotel (hotelStars) and what the travellers enjoy (interests) shape the hotels and activities picked. A field name the tool does not take i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cities | array | yes | The cities to stay in, in order (1 to 6). |
| startDate | string | no | The exact day the trip starts, YYYY-MM-DD. Needed to build: without it nothing is built. |
| month | integer | no | The month of travel (1 to 12), when the person has no exact day yet. With month + year and no startDate nothing is built: the answer suggests a start date (suggestedStartDate). |
| year | integer | no | The year of travel, with month. |
| totalNights | integer | no | Nights for the whole trip, when some cities have no nights of their own (split between them). |
| adults | integer | yes | Adults travelling (1 to 9). |
| childrenAges | array | no | Each child's age (0 to 17), at most 6 children. |
| homeCity | string | yes | The city the travellers fly from and come back to. |
| pace | string | no | How full each day is: relaxed, balanced or fast. |
| hotelStandard | string | no | Hotel standard: budget, comfort or luxury. |
| hotelStars | array | no | The kinds of hotel the person wants, the choices on the website: 1 = hostels, 2 = value for money, 3 = 3-star (mid-range), 4 = 4-star (comfortable), 5 = 5-star (luxury). The best rated hotel of these |
| interests | array | no | What the travellers enjoy, the choices on the website: Culture, Food & Dining, Art & Museums, Beach, Nightlife, Shopping, History, Nature. Left out: a bit of everything. |
| activityStyle | string | no | mix (some tours, some on your own), self_guided (mostly on your own) or all_inclusive (guided tours). |
| budgetInr | integer | no | The whole trip budget in Indian rupees, a whole number (₹4.5 lakh = 450000). Left out: a typical amount for this trip is used. |
| keepCityOrder | boolean | no | true keeps the cities in the order given. false or left out lets AlgoTrips pick the best order for flights and getting around. |
| gettingAround | string | no | How the travellers get there and between cities, the choices on the website: auto (AlgoTrips picks a flight or road / rail for each hop), all (a flight on every hop that has one), edge (flights to the |
| choicesConfirmed | boolean | no | true: any of budgetInr, the kind of hotel (hotelStars or hotelStandard), pace, activityStyle, gettingAround and (2 or more cities) keepCityOrder left out gets its default. false or left out: with any |
How a trip build is going, by its build id: while it builds, what it is working on; when it is ready, the total price, nights, hotel (with its star rating and guest score out of 10) and number of activities per city, the order of the cities and why when AlgoTrips changed it, a day-by-day outline with the flights, and the link to open and book it on AlgoTrips. Needs the person to be signed in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | The build id returned when the trip build started. |
Searches one-way flights on AlgoTrips for one day between two cities or airports, with current prices. Returns up to 5 options (airline, flight numbers, times, duration, stops, baggage, refund, fare and price for all passengers), each with a link to book it on AlgoTrips, and a link to see every flight. Nothing is booked or paid here. The prices are the signed-in AlgoTrips account's own; needs the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Where the flight leaves from: a city ("Mumbai", or "Hyderabad, India" when the name is shared) or a 3-letter airport code ("BOM"). |
| to | string | yes | Where the flight goes: a city or a 3-letter airport code, as for from. |
| date | string | yes | The day of the flight, YYYY-MM-DD, from today up to 330 days ahead. |
| departAfter | string | no | The earliest departure time, HH:MM (24-hour clock, local time at the departure airport). |
| departBefore | string | no | The latest departure time, HH:MM (24-hour clock, local time at the departure airport). |
| preferredTime | string | no | A preferred departure time, HH:MM. Without departAfter or departBefore, only flights leaving within 2 hours of it are returned. The flight nearest to it is always among the options. |
| adults | integer | no | Adults (12 and over) travelling, 1 to 9. Left out: 1. |
| childrenAges | array | no | Each child's age, 2 to 11. Adults and children together are at most 9. |
| infants | integer | no | Infants under 2 (on a lap), 0 to 4, no more than the adults. |
| cabin | string | no | Cabin: economy, premium_economy, business or first. Left out: every cabin. |
| directOnly | boolean | no | true: nonstop flights only. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 AlgoTrips or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 5 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest57042f23754bd60baab75eca4493773e2f602ed9ca3d9317f8322e2a7f701c9f
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| destination_facts | no tags | |
| my_trips | no tags | |
| plan_trip | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| trip_status | no tags | |
| search_flights | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest57042f23754bd60b
Scanned2026-11-05
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish AlgoTrips can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.