Remote MCP · Endpoint

Fair Fare MCP server

No. Fair Fare answered an MCP handshake 29 minutes ago.

UpLast checked 29 minutes ago

Server URL

https://goodturn-mcp.pages.dev/fairfare/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/fairfare
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
42 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
What a taxi, Uber or Lyft should cost, airport pickup rules, and overcharge checks.
Listing
From the official MCP registry (active).
Recent checks of Fair Fare
CheckedResultHandshake
29 minutes agoHandshake completed42 ms
3 days agoHandshake completed17 ms
13 days agoHandshake completed25 ms
14 days agoHandshake completed46 ms
15 days agoHandshake completed18 ms
16 days agoHandshake completed61 ms
17 days agoHandshake completed195 ms
18 days agoHandshake completed73 ms
19 days agoHandshake completed91 ms
21 days agoHandshake completed61 ms
23 days agoHandshake completed98 ms
25 days agoHandshake completed78 ms
27 days agoHandshake completed137 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 23.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Fair Fare and makes no claim about it beyond what these checks measured.