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.

Pinpoint Flights

REMOTE · PINPOINT.FLIGHTS

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

Available components

+4 this week 71 Trust /100

Last scanned (22 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Usability48
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 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 +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.

  • 20 Nov 26 0
    • 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 security
  • 19 Nov 26 +1
    • “search_flights” reworded the description of “bags” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 66

    First indexed and scored.

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://pinpoint.flights/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pinpoint.flights CN=YE1,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 69d5cf8bd166ed93138651d7b9eaeb3f2f1
SANs: *.pinpoint.flights, pinpoint.flights
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 pinpoint.flights. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
flights. DS published 64106 8 Verified
pinpoint.flights. 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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pinpoint.flights/mcp Verified 200
http (plaintext) http://pinpoint.flights/mcp HTTPS enforced 301 https://pinpoint.flights/mcp
MCP tools · 1 exposed · ~2,838 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
search_flights ~2,838

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),…

NameTypeReqDescription
airlinesobject–Airlines and alliances to prefer, to rather not fly (soft), or never to fly (hard), with any exceptions
amenitiesobject–On-board needs: wifi, a lie-flat seat, and the flight length from which they matter
arriveByobject–A deadline at the destination: the date, and optionally the local time, they must have arrived by
bagsobject–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
blackoutsarray–YYYY-MM-DD dates the user cannot travel, only if stated absolutely
budgetobject–The most the traveller will pay in USD, per person or for the whole group
cabinobject–Cabin class, whether mixing cabins between legs is fine, and any upgrade the traveller wants priced
departEarliestobject–Earliest date the traveller can leave: an absolute date, days from today, or a whole month
departLatestobject–Latest date the traveller can leave; the same as departEarliest for one fixed date
destinationobject–Where the trip goes: one place, or several as alternatives (the cheapest wins)
exactFlightsobject–'Prefer exact flight': a specific flight the traveller wants to be on, such as the one someone they travel with is booked on
fareobject–Fare rules: basic economy excluded or not, refundable, changeable, largest acceptable change fee, seat selection
oneWayboolean–true for a one-way trip; leave out for a round trip
originobject–Where the trip starts: the places the traveller named, and whether nearby airports are acceptable
outboundDaysobject–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)
outboundTimesobject–Clock-time limits for the depart flight: hard not-before / not-after bounds and softer ideal windows, for departure and arrival
rankBystring–cheapest only if the user says the absolute cheapest / price is all that matters / doesn't care about duration or stops
returnDaysobject–Days of the week for the return flight, hard or soft as for outboundDays
returnEarliestobject–Earliest date the traveller can fly back
returnLatestobject–Latest date the traveller can fly back
returnTimesobject–Clock-time limits for the return flight, as for outboundTimes
routeobject–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
stopoverobject–A deliberate multi-day stop on the way: where, on which direction, for how many days, and how much extra it may cost
timesApplyToBothDirectionsstring–yes when the traveller gave one set of times meant for both the depart and the return flight
travelersobject–Who is flying: adults, each child's age, babies on a lap or in their own seat, and nationalities when given
tripLengthobject–How many days the stay lasts: a minimum, a preferred length, a maximum, and whether a different length is fine when cheaper

No output schema declared.

No examples provided.

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.

remote · pinpoint.flights

# add to Claude Code
claude mcp add --transport http flights-pinpoint-pinpoint-flights 'https://pinpoint.flights/mcp'
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.