# AlgoTrips

> Plan priced day-by-day trips: flights, hotels, activities and transfers. Book on algotrips.com.

- name: com.algotrips/algotrips
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 88/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.algotrips%2Falgotrips
- tools: https://api.protogrid.dev/v1/servers/com.algotrips%2Falgotrips/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "algotrips": {
      "type": "http",
      "url": "https://api.algotrips.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-10d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 88/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 94 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,522 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 100 (weight 15)

- pass `stability.changes`: 2 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 2,522 tokens to load them all
- tool set hash: 0cbaa9258e28d79a0e6bfd848d9600bd
- tools last changed: 2026-11-13T01:26:46.250Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.algotrips/algotrips.svg)](https://protogrid.dev/servers/com.algotrips/algotrips)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-13 `plan_trip` changed (description, inputSchema, outputSchema)
  - before: 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 is refused: nothing is built, and the answer names the right field. Returns a build id at once. The trip takes about 3 to 6 minutes, and AlgoTrips emails the person when it is ready (the price and the link), or if it could not build it, when it has their email (the answer says so). With choicesConfirmed not true and any of the budget, the kind of hotel, pace, activities, getting around or (2 or more cities) the city order left out, nothing is built: the answer lists those choices with their questions and defaults. Booking and payment happen on algotrips.com. Needs the person to be signed in to AlgoTrips.
  - after: 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 is refused: nothing is built, and the answer names the right field. Returns a build id at once. The trip takes about 3 to 6 minutes, and AlgoTrips emails the person when it is ready (the price and the link), or if it could not build it, when it has their email (the answer says so). With any of the budget, the kind of hotel, pace, activities, getting around or (2 or more cities) the city order left out, nothing is built when choicesConfirmed is not true, or when it is true but these choices were not listed to this account through this assistant at least 15 seconds and at most 2 hours earlier (a build started uses that up): the answer lists those choices with their questions and defaults. Booking and payment happen on algotrips.com. Needs the person to be signed in to AlgoTrips.
- 2026-11-04 `search_flights` added
  - 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 person to be signed in to AlgoTrips. A city that is not found or is shared by several cities returns close matches instead (status needs_changes).

Full history: https://api.protogrid.dev/v1/servers/com.algotrips%2Falgotrips/changes

## Remotes

- https://api.algotrips.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `destination_facts`: 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.
- `my_trips`: 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.
- `plan_trip`: 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 is refused: nothing is built, and the answer names the right field. Returns a build id at once. The trip takes about 3 to 6 minutes, and AlgoTrips emails the person when it is ready (the price and the link), or if it could not build it, when it has their email (the answer says so). With any of the budget, the kind of hotel, pace, activities, getting around or (2 or more cities) the city order left out, nothing is built when choicesConfirmed is not true, or when it is true but these choices were not listed to this account through this assistant at least 15 seconds and at most 2 hours earlier (a build started uses that up): the answer lists those choices with their questions and defaults. Booking and payment happen on algotrips.com. Needs the person to be signed in to AlgoTrips.
- `search_flights`: 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 person to be signed in to AlgoTrips. A city that is not found or is shared by several cities returns close matches instead (status needs_changes).
- `trip_status`: 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.