FairWhere MCP server
com.fairwhere/fairwherefairwhere.comstreamable-httpv0.5.0Scanned
Free London beta meetup planner. Ranks curated Placelists by journey fairness for the whole group.
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the FairWhere MCP server can do
The FairWhere MCP server is published by fairwhere.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: fair_shortlist and open_plan_link), but cannot delete data. 4 tools only read.
2 tools bring in text other people can write (fair_shortlist and get_meet_pair).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 0.5.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 2Claude Code: ask
fair_shortlistRank the venues in one or more curated FairWhere Placelists by FairWhere Score for this group.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Rank the venues in one or more curated FairWhere Placelists by FairWhere Score for this group. Free estimate-only path: no Google calls, no credits. Returns top venues with banded scores, per-person journey burden, score-factor breakdown, citations, and a continue_on_fairwhere link. Provide placelistIds and/or placelistSlugs (from list_placelists).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
open_plan_linkBuild a FairWhere deep link so the group can continue the plan on FairWhere (invite people, vote, live-check journeys).1 finding
Why it is in this group
- The name "open_plan_link" says "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "open_plan_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_plan_link" says "open": a word for a change.
Description, as the server wrote it Build a FairWhere deep link so the group can continue the plan on FairWhere (invite people, vote, live-check journeys). Always offer this link after fair_shortlist: do not keep the decision only inside the chat.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_meet_pairReturn the published FairWhere answer for where to meet between two London neighbourhoods (winner venue, minutes, gap, top venues, citation URL).Reads text others writeNo findings
Why it is in this group
- The name "get_meet_pair" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Return the published FairWhere answer for where to meet between two London neighbourhoods (winner venue, minutes, gap, top venues, citation URL). Use when the user asks “where should we meet between X and Y”. Do not invent a geographic midpoint.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_meet_pairsList published FairWhere pages that answer “where to meet between area A and area B” in London.No findings
Why it is in this group
- The name "list_meet_pairs" says "list": a word for reading.
Description, as the server wrote it List published FairWhere pages that answer “where to meet between area A and area B” in London. Each row has a winner venue, minute gap, FairWhere Score, and citation URL. Prefer this over inventing a midpoint when the user names two neighbourhoods. Only status=live pages are returned.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_placelistsDiscover public curated Placelists (venue collections) on FairWhere.No findings
Why it is in this group
- The name "list_placelists" says "list": a word for reading.
Description, as the server wrote it Discover public curated Placelists (venue collections) on FairWhere. Returns id, slug, name, description, best_for, categories, venue count, and canonical URLs. Call this before fair_shortlist. If count is 0 for an activity, that activity is unavailable: refuse to invent restaurants/cocktails and pivot to available_activities.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pingVerify the FairWhere MCP server is reachable.No findings
Why it is in this group
- The name "ping" says "ping": a word for reading.
Description, as the server wrote it Verify the FairWhere MCP server is reachable. Returns a greeting echoing the provided note.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.fairwhere.com/mcp: tools/list returned 6 tools to an anonymous client, including fair_shortlist (write), open_plan_link (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnopen_plan_link
The server marks "open_plan_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_plan_link" says "open": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fairwhere https://www.fairwhere.com/mcpclaude mcp add --transport http fairwhere https://www.fairwhere.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fairwhere__ping",
"mcp__fairwhere__list_placelists",
"mcp__fairwhere__list_meet_pairs",
"mcp__fairwhere__get_meet_pair"
],
"ask": [
"mcp__fairwhere__fair_shortlist",
"mcp__fairwhere__open_plan_link"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fairwhere. Review it before you use it.
Capability tags behind 2 rules
- mcp__fairwhere__fair_shortlist untrusted-input
- mcp__fairwhere__get_meet_pair untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.fairwhere/fairwhere/verify?hash=959020f5259e6af7540f0733018d2587e71b498a0c00af736b48e30a43c7b43c" | jq -e '.changed == false'Pinned hash 959020f5259e, from Nov 13, 2026, 05:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.fairwhere/fairwhere/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.fairwhere/fairwhere)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
FairWhere MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the FairWhere MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the FairWhere MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the FairWhere MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the FairWhere MCP server have?
- 6 tools: 2 write, 4 read. fair_shortlist, open_plan_link, ping, list_placelists, list_meet_pairs and get_meet_pair.
Does the FairWhere MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the FairWhere MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the FairWhere MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.