overpass.ch MCP server
ch.overpass/overpassoverpass.chstreamable-httpv1.3.0Scanned
Overpass API on the full planet with history, plus geocoding and elevation. Needs an account.
7 tools: 3 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
3 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 overpass.ch MCP server can do
The overpass.ch MCP server is published by overpass.ch, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: overpass_query, elevation_points and elevation_profile), but cannot delete data. 4 tools only read.
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 asks for sign-in and publishes OAuth metadata, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 4, 2026, version 1.3.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.
7 tools
Changes things 3Claude Code: ask
elevation_pointsHeights above sea level in metres for a list of points, negative at sea.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 Heights above sea level in metres for a list of points, negative at sea. Switzerland and Liechtenstein: swissALTI3D, a 2 m grid of the ground (credit "© swisstopo"). Elsewhere on land: Copernicus GLO-30, a 30 m grid of the surface that includes buildings and trees. At sea: GEBCO. Each point counts as one lookup; account_status shows the plan maximum per call.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
elevation_profileElevation profile along a path of two or more points: distance, ascent, descent, the lowest and the highest point, and up to 100 points along the way (distance from the start, heig…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 Elevation profile along a path of two or more points: distance, ascent, descent, the lowest and the highest point, and up to 100 points along the way (distance from the start, height, lat, lon). The path is sampled every 90 m unless samples or interval_m is set. Each sample counts as one lookup, up to the plan maximum per call.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
overpass_queryRuns an Overpass QL query on the full OpenStreetMap planet at overpass.ch (minutely updates) and returns the matching nodes, ways and relations with their tags.1 finding
Why it is in this group
- The name "overpass_query" says "query": a word for reading.
- The description's first verb is "run": 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 "overpass_query" 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 "overpass_query" says "query": a word for reading.
Description, as the server wrote it Runs an Overpass QL query on the full OpenStreetMap planet at overpass.ch (minutely updates) and returns the matching nodes, ways and relations with their tags. Start the query with a settings line such as [out:json][timeout:25]; JSON is used when the query does not set [out:]. [timeout:N] stops the query after N s: at most 120 s through this tool, and the plan may allow less. Patterns: - Box (south,west,north,east): nwr["amenity"="cafe"](47.36,8.53,47.38,8.55); out center; - Radius in metres around lat,lon: nwr["amenity"="pharmacy"](around:1000,47.3769,8.5417); out center; - In a place: overpass_area_id from geocode_search, then area(id:3600051701)->.a; nwr["tourism"="hotel"](area.a); out center; - By name (exact, local language): area["name"="Wien"]["admin_level"="4"]->.a; - Count: out count; Tags only: out tags; At most 50: out center 50; Lines with coordinates: out geom; (large) - Regex, any case: ["name"~"^Bahnhof",i] - By id: node(3470507586); out; way(id:1,2,3); out tags; - The map at a past date (Medium and Large plans): [date:"2015-01-01T00:00:00Z"] in the settings line. The answer starts with counts and the date of the data, then one JSON object per element and line, up to max_chars characters. When it is cut, call again with offset, or narrow the query. Each call counts as one request of the plan, a cut one too. Data © OpenStreetMap contributors, ODbL.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
Only reads 4Show 4 read-only tools
account_statusThe plan of the API key of this connection and its use this month: Overpass requests used and left, when the allowance starts again, running queries, elevation lookups, geocoding r…No findings
Why it is in this group
- The name "account_status" says "status": a word for reading.
Description, as the server wrote it The plan of the API key of this connection and its use this month: Overpass requests used and left, when the allowance starts again, running queries, elevation lookups, geocoding requests, and the date of the data. It names the products on a free plan, which is not for commercial use. It does not count as a request.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
geocode_reverseFinds the address or place at a point (reverse geocoding).No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it Finds the address or place at a point (reverse geocoding). detail chooses what to return: the nearest address or object (address, the default), the street, the district, the city, the county, the state or the country that contains the point. The result has the same fields as those of geocode_search. One call counts as one geocoding request.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
geocode_searchFinds places, addresses and points of interest by name (geocoding).No findings
Why it is in this group
- The name "geocode_search" says "search": a word for reading.
Description, as the server wrote it Finds places, addresses and points of interest by name (geocoding). Partial text works, as for autocomplete. Each result has the name, the address, lat and lon, a bounding box (south, west, north, east), the OpenStreetMap element (osm), and for ways and relations an overpass_area_id to use in overpass_query as area(id:N). Languages: en, de, fr. One call counts as one geocoding request.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
overpass_examplesSearches the cookbook of overpass.ch: Overpass queries that were tested on the full planet, with explanations.No findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Description, as the server wrote it Searches the cookbook of overpass.ch: Overpass queries that were tested on the full planet, with explanations. Give a topic in a few words, such as "bakeries in a city", "hiking routes", "count buildings" or "changes since a date", and get the 5 closest examples with their query and a link. Free: it does not count as a request.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
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 19, 2026, 17:22 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://api.overpass.ch/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata
- https://api.overpass.ch/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://overpass.ch
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
Posture changes
- Nov 12, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://api.overpass.ch/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://api.overpass.ch/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://overpass.ch
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
- Warnoverpass_query
The server marks "overpass_query" 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 "overpass_query" says "query": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 7 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://api.overpass.ch/.well-known/oauth-protected-resource/mcp
- RFC 9728 protected resource metadata: none to https://api.overpass.ch/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://overpass.ch
- Dynamic client registration: not observed to no
- Client ID metadata documents: not observed to yes
Tools3 added, 3 removed, 2 changed.+3 added−3 removed~2 changedView diff
- Added:elevation_pointsChanges things
- Added:geocode_reverseOnly reads
- Added:geocode_searchOnly reads
- Removed:elevation
- Removed:geocode
- Removed:reverse_geocode
- Changed:account_statusOnly readsdescription
- Changed:overpass_queryChanges thingsdescription
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http overpass https://api.overpass.ch/mcpclaude mcp add --transport http overpass https://api.overpass.ch/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__overpass__overpass_examples",
"mcp__overpass__geocode_search",
"mcp__overpass__geocode_reverse",
"mcp__overpass__account_status"
],
"ask": [
"mcp__overpass__overpass_query",
"mcp__overpass__elevation_points",
"mcp__overpass__elevation_profile"
],
"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 overpass. 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/ch.overpass/overpass/verify?hash=dafdb6c84bc9d07b83ceb6572b826843cb4a84f08189115b943885cf4aefed37" | jq -e '.changed == false'Pinned hash dafdb6c84bc9, from Nov 4, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ch.overpass/overpass/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ch.overpass/overpass)Source: MCP Registry · repository. Synced Nov 14, 2026, 10:17 UTC.
overpass.ch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the overpass.ch MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 3 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 overpass.ch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the overpass.ch 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 overpass.ch MCP server have?
- 7 tools: 3 write, 4 read. overpass_query, elevation_points, elevation_profile, overpass_examples, geocode_search, geocode_reverse and account_status.
Does the overpass.ch MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728).
Does the overpass.ch MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the overpass.ch MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.