FairWhere
Actively maintained
≈ 4visits/mo
Little sign of use · estimate, read Oct 13, 2026
- For
- People in London arranging group meetups who want journeys to be fair for everyone
- Activity
- Actively maintainedsite updated 5 days ago
- Company
- FairWhere Limited · Domain since 2026privacy policy · domain registered
- Used for
- shortlist venues that keep travel times even across the group
- compare candidate venues by the gap between journeys
- check evening venues against last trains home
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsfairwhere.com ↗
Price not read
- Run byFairWhere Limitedprivacy policy ↗
- Privacy policy updated2026-10-09privacy policy ↗
These are FairWhere's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP servercom.fairwhere/fairwhereverified in the MCP registry
- Stateanswers, 6 toolschecked 2026-10-20
- Address to connectwww.fairwhere.com/mcp
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use FairWhere for?
Sign in to leave a noteWhat is FairWhere?
Ranks London venues and curated placelists by the journey-time gap each person in a group faces when meeting up.
Who is FairWhere for?
People in London arranging group meetups who want journeys to be fair for everyone
Is FairWhere free?
No. Its pricing page showed no free plan on 2026-10-20.
Do people use FairWhere?
Little sign of use: ≈ 4 visits/mo · estimate, 2026-10.
Is FairWhere still maintained?
Actively maintained: site updated 5 days ago.
Who owns FairWhere?
FairWhere is run by FairWhere Limited, per its privacy policy (2026-10-20).
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.