Map Parser
REMOTE · MAPPARSER.TRAVEL-TRACKER.ORG
Parse Google Maps links into stops with coordinates. Geocode, route, and export.
Available components
Last scanned (20 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 414 tokens (~103/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mapparser.travel-tracker.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mapparser.travel-tracker.org | CN=YR1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 6ec5b6f76b44f932d3452bcd11076a14c32 |
| SANs: mapparser.travel-tracker.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mapparser.travel-tracker.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| travel-tracker.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mapparser.travel-tracker.org/mcp | Verified | 200 | |
| http (plaintext) | http://mapparser.travel-tracker.org/mcp | HTTPS enforced | 301 | https://mapparser.travel-tracker.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_waypoints Export waypoints ~100
Turn a Google Maps link or a list of stops into a CSV (import into Google My Maps) or KML (Google Earth, My Maps) file. Returns the file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | – |
| url | string | – | Google Maps directions link, full (google.com/maps/dir/...) or short (maps.app.goo.gl/...) |
| waypoints | array | – | Stops to export, when no url is given |
No output schema declared.
No examples provided.
geocode Geocode ~71
Look up a place name or address (forward) or a coordinate (reverse) with OpenStreetMap Nominatim. Returns the "State, Country code" region and the full address.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | – |
| lng | number | – | – |
| query | string | – | Place name or address |
No output schema declared.
No examples provided.
get_route Get route ~58
Distance and travel time through stops in order, per leg and in total, using OpenStreetMap routing (OSRM). Pass the waypoints from parse_map_link.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Default driving |
| waypoints | array | yes | – |
No output schema declared.
No examples provided.
parse_map_link Parse Google Maps link ~108
Extract the stops (names and coordinates) of a Google Maps directions link, plus the likely region. Short links are expanded; links that hide stop names are opened in a headless browser, which can take up to a minute.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Google Maps directions link, full (google.com/maps/dir/...) or short (maps.app.goo.gl/...) |
| useBrowser | boolean | – | Force the slower browser mode, e.g. when names come back as coordinates |
No output schema declared.
No examples provided.
How do I install the Map Parser MCP server?
Map Parser is a hosted endpoint at https://mapparser.travel-tracker.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mapparser.travel-tracker.org
claude mcp add --transport http changzhiai-map-parser 'https://mapparser.travel-tracker.org/mcp'
What is the Map Parser MCP server?
Map Parser is an MCP server listed in the public MCP registry as io.github.changzhiai/map-parser. Parse Google Maps links into stops with coordinates. Geocode, route, and export. This page covers its hosted endpoint (https://mapparser.travel-tracker.org/mcp).
Is the Map Parser MCP server safe to use?
Map Parser scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Map Parser MCP server expose?
Map Parser exposes 4 tools: parse_map_link, geocode, get_route, export_waypoints. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Does the Map Parser MCP server require authentication?
No. We connected to Map Parser without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Map Parser MCP server still maintained?
Map Parser is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.