GeoLocale MCP server
io.geolocale/geolocalegeolocale.iostreamable-httpv1.0.0Scanned
What is around a neighborhood: counts of everyday places within 1 km, from OpenStreetMap.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- 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 GeoLocale MCP server can do
The GeoLocale MCP server is published by geolocale.io, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: compare_neighborhoods and neighborhood_facts), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
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 20, 2026, version 1.0.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.
3 tools
Changes things 2Claude Code: ask
compare_neighborhoodsSet the neighborhoods of one city side by side: the distance to the nearest rail or metro station, and how many parks, supermarkets, pharmacies, schools, restaurants and cafes lie …1 finding
Why it is in this group
- The name "compare_neighborhoods" says "compare": a word for reading.
- The description's first verb is "set": 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 "compare_neighborhoods" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "compare_neighborhoods" says "compare": a word for reading.
Description, as the server wrote it Set the neighborhoods of one city side by side: the distance to the nearest rail or metro station, and how many parks, supermarkets, pharmacies, schools, restaurants and cafes lie within 1 km of each neighborhood centre. Counted from OpenStreetMap; the answer carries the date of the map data.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
neighborhood_factsEverything GeoLocale counted around one neighborhood: for each kind of place, the number within 1 km of the centre and the name and distance of the nearest one, plus the similar ne…No 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.
Description, as the server wrote it Everything GeoLocale counted around one neighborhood: for each kind of place, the number within 1 km of the centre and the name and distance of the nearest one, plus the similar neighborhoods in other cities matched on the same counts. Counted from OpenStreetMap; the answer carries the date of the map data.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
find_citiesList the cities GeoLocale covers, filtered by part of a city name and/or a country.No findings
Why it is in this group
- The name "find_cities" says "find": a word for reading.
Description, as the server wrote it List the cities GeoLocale covers, filtered by part of a city name and/or a country. Returns each city's id, its number of neighborhoods, how many have counts, the date of its map data and the address of its page.
Annotations the server declares
- readOnlyHint: 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 untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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:19 UTC, unchanged since Nov 20, 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://geolocale.io/api/mcp: tools/list returned 3 tools to an anonymous client, including compare_neighborhoods (write), neighborhood_facts (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "compare_neighborhoods" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "compare_neighborhoods" says "compare": a word for reading.
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 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http geolocale https://geolocale.io/api/mcpclaude mcp add --transport http geolocale https://geolocale.io/api/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__geolocale__find_cities"
],
"ask": [
"mcp__geolocale__compare_neighborhoods",
"mcp__geolocale__neighborhood_facts"
],
"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 geolocale. Review it before you use it.
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/io.geolocale/geolocale/verify?hash=a2f5edf7146f096dc5a0707e4955e225862ae303cd8fda672d7010c924cfeb51" | jq -e '.changed == false'Pinned hash a2f5edf7146f, from Nov 20, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.geolocale/geolocale/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.geolocale/geolocale)Source: MCP Registry. Synced Nov 20, 2026, 07:17 UTC.
GeoLocale MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GeoLocale MCP server safe?
- No scan can promise that. What its definitions show: 3 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 GeoLocale MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the GeoLocale 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 GeoLocale MCP server have?
- 3 tools: 2 write, 1 read. compare_neighborhoods, neighborhood_facts and find_cities.
Does the GeoLocale MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the GeoLocale MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the GeoLocale MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.