# Pinpoint Flights (remote · pinpoint.flights)

Flight search with very deep filters, from your assistant. Fla. Seller of Travel Reg. No. ST150266

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `pinpoint.flights`: 71/100 (this document), [markdown](https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint.md), [page](https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint)

## Channel facts

- Endpoint: `https://pinpoint.flights/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 48/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2943 tokens (~2943/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pinpoint Flights MCP server?

Pinpoint Flights is a hosted endpoint at https://pinpoint.flights/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.

### Claude

```bash
claude mcp add --transport http flights-pinpoint-pinpoint-flights 'https://pinpoint.flights/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "flights-pinpoint-pinpoint-flights": {
      "url": "https://pinpoint.flights/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "flights-pinpoint-pinpoint-flights": {
      "type": "http",
      "url": "https://pinpoint.flights/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.flights-pinpoint-pinpoint-flights]
url = "https://pinpoint.flights/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "flights-pinpoint-pinpoint-flights": {
      "type": "remote",
      "url": "https://pinpoint.flights/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add flights-pinpoint-pinpoint-flights --url 'https://pinpoint.flights/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  flights-pinpoint-pinpoint-flights:
    url: "https://pinpoint.flights/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "flights-pinpoint-pinpoint-flights": {
      "Transport": "http",
      "Url": "https://pinpoint.flights/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add flights-pinpoint-pinpoint-flights -t streamable-http -u 'https://pinpoint.flights/mcp'
```

### Other

```json
{
  "mcpServers": {
    "flights-pinpoint-pinpoint-flights": {
      "type": "http",
      "url": "https://pinpoint.flights/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search_flights” rewrote its description, which is the text the model reads

### 2026-11-19 (score 70, +1)

- [cosmetic] “search_flights” reworded the description of “bags”

### 2026-11-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 66)

First indexed and scored.

## MCP tools (1)

### `search_flights` (~2838 tokens)

Search flights

Search flights on Pinpoint Flights, a flight search with very deep filters: exact time windows, nonstop vs. price trade-offs, bags, fare rules, airlines to avoid, flexible dates and trip lengths, nearby airports, several destinations at once. Fill in only what the traveller said and leave everything else out (defaults apply). If something that changes the results is missing (dates, how long the stay is, an airport we can't place), no search runs: you get questions back to ask the traveller, then call again with the answers. Each traveller has 7 searches a day, so ask before searching when the request is vague, and don't run near-identical searches to compare: one search already prices many date combinations. Repeating a search from the last 24 hours is free. Results come with results_url, the full results page on pinpoint.flights (every fare, with filters and sorting, easy to compare), and each flight that can be booked has its own book_url, which opens booking for that exact flight. Give the traveller results_url first, then show the best match and every flight in each section (up to 10 in all), in rank order, each with its price, times, stops, airline and book_url, not just the top one or two; mention same-price swaps when a flight lists them; and tell them that when they find a flight they like, its book_url is where to book it.

How to fill the fields (these are the rules the site's own assistant follows; where they say "readback", that means what you tell the traveller):
\- Places: copy what the user said (city, airport code, country, region). Do not invent airport codes. If several destinations are named as alternatives ("Bali or Thailand"), list them all; the engine picks the cheapest. When the user names the airport they prefer in a city ("I strongly prefer DCA"), that airport is the place: don't also list the city, and don't describe a preference the filters can't hold.
\- Dates: express them as intents relative to today (relative_days), as months (YYYY-MM),…

Input parameters:

- `airlines` (object): Airlines and alliances to prefer, to rather not fly (soft), or never to fly (hard), with any exceptions
- `amenities` (object): On-board needs: wifi, a lie-flat seat, and the flight length from which they matter
- `arriveBy` (object): A deadline at the destination: the date, and optionally the local time, they must have arrived by
- `bags` (object): Bags the traveller brings: carry-ons and checked bags (per person, or shared across the group when pooled). Checked bag fees are listed beside each fare and counted in its all-in price
- `blackouts` (array): YYYY-MM-DD dates the user cannot travel, only if stated absolutely
- `budget` (object): The most the traveller will pay in USD, per person or for the whole group
- `cabin` (object): Cabin class, whether mixing cabins between legs is fine, and any upgrade the traveller wants priced
- `departEarliest` (object): Earliest date the traveller can leave: an absolute date, days from today, or a whole month
- `departLatest` (object): Latest date the traveller can leave; the same as departEarliest for one fixed date
- `destination` (object): Where the trip goes: one place, or several as alternatives (the cheapest wins)
- `exactFlights` (object): 'Prefer exact flight': a specific flight the traveller wants to be on, such as the one someone they travel with is booked on
- `fare` (object): Fare rules: basic economy excluded or not, refundable, changeable, largest acceptable change fee, seat selection
- `oneWay` (boolean): true for a one-way trip; leave out for a round trip
- `origin` (object): Where the trip starts: the places the traveller named, and whether nearby airports are acceptable
- `outboundDays` (object): Days of the week for the depart flight, as a requirement (hard) or a preference (soft, with how much more they would pay for it)
- `outboundTimes` (object): Clock-time limits for the depart flight: hard not-before / not-after bounds and softer ideal windows, for departure and arrival
- `rankBy` (string): cheapest only if the user says the absolute cheapest / price is all that matters / doesn't care about duration or stops
- `returnDays` (object): Days of the week for the return flight, hard or soft as for outboundDays
- `returnEarliest` (object): Earliest date the traveller can fly back
- `returnLatest` (object): Latest date the traveller can fly back
- `returnTimes` (object): Clock-time limits for the return flight, as for outboundTimes
- `route` (object): Stops and connections: nonstop as a requirement or a preference, layover lengths, overnight and self-transfer connections, airports or countries to avoid, total travel time
- `stopover` (object): A deliberate multi-day stop on the way: where, on which direction, for how many days, and how much extra it may cost
- `timesApplyToBothDirections` (string): yes when the traveller gave one set of times meant for both the depart and the return flight
- `travelers` (object): Who is flying: adults, each child's age, babies on a lap or in their own seat, and nationalities when given
- `tripLength` (object): How many days the stay lasts: a minimum, a preferred length, a maximum, and whether a different length is fine when cheaper

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 69
- 2026-11-16: 68
- 2026-11-15: 68
- 2026-11-14: 67
- 2026-11-13: 67
- 2026-11-12: 66
- 2026-11-11: 66

## Common questions

### What is the Pinpoint Flights MCP server?

Pinpoint Flights is an MCP server listed in the public MCP registry as flights.pinpoint/pinpoint-flights. Flight search with very deep filters, from your assistant. Fla. Seller of Travel Reg. No. ST150266. This page covers its hosted endpoint (https://pinpoint.flights/mcp).

### Is the Pinpoint Flights MCP server safe to use?

Pinpoint Flights scores 71 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 Pinpoint Flights MCP server expose?

Pinpoint Flights exposes 1 tool: search_flights. Their descriptions and schemas cost roughly 2,838 tokens of context every time the server is loaded.

### Does the Pinpoint Flights MCP server require authentication?

No. We connected to Pinpoint Flights without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pinpoint Flights MCP server still maintained?

Pinpoint Flights 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 Pinpoint Flights MCP server?

VerifyMCP ran 13 checks on Pinpoint Flights, 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.

## Links

- Remote endpoint: https://pinpoint.flights/mcp
- Repository: https://github.com/pinpoint-flights-llc/pinpoint-flights-mcp
- Website: https://pinpoint.flights/connect
- Changelog RSS feed: https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint.xml
- Changelog JSON feed: https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint.json
- HTML version of this page: https://verifymcp.io/servers/flights-pinpoint-pinpoint-flights/pinpoint
