emap — Euskadi hyperlocal mobility
REMOTE · GAIZKAJIMENEZ.COM
Basque Country hyperlocal mobility: ES/EU semantic search, routing, open-data POIs, peak-bagging.
Available components
Last scanned (23 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
Recent critical change
TLS certificate (13 Aug 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Aug 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HSTS header: unverified → pass ▲ security
- TLS certificate: fail → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Score status: failed → scored ▲ functional
- 13 Aug 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.57 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://gaizkajimenez.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gaizkajimenez.com | CN=YR2,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 556a940332cd1c4e1a81fae9c6fa42595fa |
| SANs: gaizkajimenez.com, www.gaizkajimenez.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 gaizkajimenez.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gaizkajimenez.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 308 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gaizkajimenez.com/mcp | Redirected | 308 | https://www.gaizkajimenez.com/mcp |
| http (plaintext) | http://gaizkajimenez.com/mcp | HTTPS enforced | 308 | https://gaizkajimenez.com/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 →
explain_place ~87
Contexto de un punto: barrio/municipio y servicios cercanos (rail, bus, aseos…) con distancias. · Puntu baten testuingurua: auzoa eta zerbitzu hurbilak. · What's around a point: neighborhood and nearby services with distances.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
nearby_pois ~147
POIs más cercanos de una capa concreta. Capas: fountains (fuentes), toilets (aseos), parking, bikepark (aparcabicis), defib (DEA), beaches (playas), ev (cargadores), cameras, fuel (gasolineras), peaks (cimas), metro, euskotren, cercanias, bilbobus, bizkaibus. · Geruza bateko POI hurbilenak. · Nearest POIs of a given layer.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| layer | string | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
plan_hike ~152
El monte en transporte público: cimas de Euskadi (2.825, OSM) alcanzables por transporte — para cada candidata, su parada/estación más cercana entre 9 redes. · Mendia garraio publikoz: tontor iritsgarriak. · Peak-bagging by public transport. HONESTO: distancias en línea recta, no ruta a pie; usa plan_route hasta la parada para el trayecto real.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
| max_results | integer | – | – |
| max_stop_dist_m | integer | – | – |
| min_ele_m | integer | – | – |
No output schema declared.
No examples provided.
plan_route ~112
Ruta real entre dos puntos con la infraestructura propia de emap (OSRM/OTP). mode: transit | walk | bike | car. · Bi punturen arteko ibilbidea. · Real route between two points. Devuelve duración, distancia y tramos (sin geometría completa).
| Name | Type | Req | Description |
|---|---|---|---|
| from_lat | number | yes | – |
| from_lon | number | yes | – |
| mode | string | – | – |
| to_lat | number | yes | – |
| to_lon | number | yes | – |
No output schema declared.
No examples provided.
search_places ~117
Búsqueda semántica local en español o euskera ("dónde beber agua", "haurra aldatzeko lekua"). · Bilaketa semantikoa gaztelaniaz edo euskaraz. · Semantic local search in Spanish or Basque. Devuelve POIs cercanos al punto (lat, lon) o abstención honesta si no entiende la consulta.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | – |
| lat | number | yes | – |
| lon | number | yes | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the emap — Euskadi hyperlocal mobility MCP server?
emap — Euskadi hyperlocal mobility is a hosted endpoint at https://gaizkajimenez.com/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 · gaizkajimenez.com
claude mcp add --transport http r3tr0eth-emap 'https://gaizkajimenez.com/mcp'
What is the emap — Euskadi hyperlocal mobility MCP server?
emap — Euskadi hyperlocal mobility is an MCP server listed in the public MCP registry as io.github.r3tr0eth/emap. Basque Country hyperlocal mobility: ES/EU semantic search, routing, open-data POIs, peak-bagging. This page covers its hosted endpoint (https://gaizkajimenez.com/mcp).
Is the emap — Euskadi hyperlocal mobility MCP server safe to use?
emap — Euskadi hyperlocal mobility scores 25 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 emap — Euskadi hyperlocal mobility MCP server expose?
emap — Euskadi hyperlocal mobility exposes 5 tools: search_places, nearby_pois, explain_place, plan_route, plan_hike. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.
Does the emap — Euskadi hyperlocal mobility MCP server require authentication?
Its publisher declares no required credentials for emap — Euskadi hyperlocal mobility. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the emap — Euskadi hyperlocal mobility MCP server still maintained?
emap — Euskadi hyperlocal mobility 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.