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.

Fair Fare

REMOTE · GOODTURN-MCP.PAGES.DEV

What a taxi, Uber or Lyft should cost, airport pickup rules, and overcharge checks.

+3 this week 85 Trust /100

Last scanned (10 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

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
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1219 tokens (~152/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

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 5 Nov 2026 · Probed https://goodturn-mcp.pages.dev/fairfare/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=goodturn-mcp.pages.dev CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 590c8ade87714dff31f31ce636eafc7da48
SANs: *.goodturn-mcp.pages.dev, goodturn-mcp.pages.dev
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 goodturn-mcp.pages.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
pages.dev. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://goodturn-mcp.pages.dev/fairfare/mcp Verified 200
http (plaintext) http://goodturn-mcp.pages.dev/fairfare/mcp HTTPS enforced 301 https://goodturn-mcp.pages.dev/fairfare/mcp
MCP tools · 8 exposed · ~1,051 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
best_time_to_ride ~173

Cheapest time of day to take a ride. For New York, typical Uber and Lyft prices for a trip of a given length at every hour of the week, from the city's trip records, with the cheapest and most expensive hours today and whether waiting saves money. For other cities, how the taxi meter rates change by time of day.

NameTypeReqDescription
citystring–Tariff city id, for example nyc, london or chicago. Defaults to nyc.
milesnumber–Trip length in miles (New York only). Defaults to 3.
whenstring–When the trip starts, in local time: now (the default), a time like 18:30 or 6pm, or a date and time like 2026-10-09T18:30.

No output schema declared.

No examples provided.

check_driver_licence ~149

Check a New York taxi or ride-app driver's licence. Whether a TLC licence number is active on New York City's daily open data for for-hire (Uber, Lyft, car service) and taxi drivers, its expiry date, and, if a name is given, whether it matches (the name on the licence is never returned). Other cities get the official way to check.

NameTypeReqDescription
citystring–City: nyc (live check) or another city id for guidance. Defaults to nyc.
namestring–Optional name the driver gave, to check it matches.
numberstring–The TLC licence number shown in the app or on the partition card.

No output schema declared.

No examples provided.

check_fare ~251

Was I overcharged? Check a fare that was paid. Compares what was paid with the official meter tariff, the airport flat fare or New York's typical Uber and Lyft prices for the same trip and hour, gives a verdict (fair, high or overcharged), the next steps for that company or city regulator, and a short message to send asking for a refund.

NameTypeReqDescription
citystring–Tariff city id, when giving miles instead of from and to.
fromstring–Where the trip started.
kindstring–Kind: taxi, uber, lyft, bolt or minicab. Defaults to taxi.
milesnumber–Trip length in miles, instead of from and to.
minutesnumber–Trip time in minutes, if known.
paidstringyesWhat was paid, without the tip, for example 48.50.
tostring–Where it ended.
whenstring–When the trip starts, in local time: now (the default), a time like 18:30 or 6pm, or a date and time like 2026-10-09T18:30.

No output schema declared.

No examples provided.

check_fleet_file ~68

Check a cab firm's fleet.json. Reads a taxi or minicab firm's fleet.json (the open format at fairfare.pages.dev/fleet that lets assistants find and book local firms directly) and lists anything to fix.

NameTypeReqDescription
urlstringyesThe https address of the fleet.json file.

No output schema declared.

No examples provided.

estimate_fare ~211

What a trip should cost by taxi, Uber or Lyft. Distance and time by road between two places, the licensed taxi meter fare with the extras that apply at that hour, any airport flat fare, typical Uber and Lyft prices in New York, airport pickup rules, a pre-booked transfer option for airport trips, and links that open Uber, Lyft or public transport directions with the trip filled in.

NameTypeReqDescription
citystring–Optional tariff city id from list_cities, when the place names are ambiguous.
fromstringyesWhere the trip starts: an address, landmark, postcode, airport code (JFK, LHR) or lat,lon.
tostringyesWhere the trip ends, in the same forms as from.
whenstring–When the trip starts, in local time: now (the default), a time like 18:30 or 6pm, or a date and time like 2026-10-09T18:30.

No output schema declared.

No examples provided.

get_airport ~87

Getting a ride at an airport. Where Uber and Lyft pick up, how the taxi rank works, flat taxi fares, drop-off and pickup charges for cars, meet and greet rules, public transport into the city with prices, and tips, from each airport's own pages.

NameTypeReqDescription
codestringyesAirport code or name, for example JFK, LAX, LHR or Heathrow.

No output schema declared.

No examples provided.

get_taxi_tariff ~81

A city's official taxi meter tariff. The starting charge, the rate per mile or kilometre, the waiting rate, time-of-day tariffs, extras and surcharges, flat fares, tipping custom and the official source.

NameTypeReqDescription
citystringyesTariff city id from list_cities, for example nyc, chicago, london or birmingham.

No output schema declared.

No examples provided.

list_cities ~31

Cities and airports covered. Every city whose official taxi tariff is on file and every airport with ground transport facts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Fair Fare MCP server?

Fair Fare is a hosted endpoint at https://goodturn-mcp.pages.dev/fairfare/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 · goodturn-mcp.pages.dev

# add to Claude Code
claude mcp add --transport http goodturnstudio-fairfare 'https://goodturn-mcp.pages.dev/fairfare/mcp'
Common questions

What is the Fair Fare MCP server?

Fair Fare is an MCP server listed in the public MCP registry as io.github.GoodTurnStudio/fairfare. What a taxi, Uber or Lyft should cost, airport pickup rules, and overcharge checks. This page covers its hosted endpoint (https://goodturn-mcp.pages.dev/fairfare/mcp).

Is the Fair Fare MCP server safe to use?

Fair Fare scores 85 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 Fair Fare MCP server expose?

Fair Fare exposes 8 tools: estimate_fare, check_fare, best_time_to_ride, get_airport, get_taxi_tariff, and 3 more. Their descriptions and schemas cost roughly 1,051 tokens of context every time the server is loaded.

Does the Fair Fare MCP server require authentication?

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

Is the Fair Fare MCP server still maintained?

Fair Fare is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.