Skip to main content
Glama

emap — Euskadi hyperlocal mobility

Server Details

Basque Country hyperlocal mobility: ES/EU semantic search, routing, open-data POIs, peak-bagging.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
r3tr0eth/emap-labs
GitHub Stars
0
Server Listing
Basque Country hyperlocal mobility

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsB

Average 3.4/5 across 5 of 5 tools scored.

Server CoherenceA
Disambiguation3/5

There is some overlap between explain_place, nearby_pois, and search_places, as all can return nearby services like toilets. However, each has a distinct primary purpose: broad context, specific layer queries, and semantic search. An agent can usually disambiguate based on the level of specificity requested.

Naming Consistency4/5

Most tools follow a verb_noun pattern (explain_place, plan_hike, plan_route, search_places), but nearby_pois uses an adjective_noun structure. The overall two-word snake_case convention is consistent, but the verb usage is not entirely uniform.

Tool Count5/5

With five tools, the set is well-scoped for a hyperlocal mobility server. It avoids bloat while covering core needs: place context, POI discovery, routing, hiking, and semantic search.

Completeness4/5

The server covers the main operations for its domain: explaining places, finding POIs, planning routes, and specialized hiking planning. Minor gaps exist, such as no direct way to retrieve all POIs of a type, but these are workable.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

  • F
    license
    A
    quality
    C
    maintenance
    OSM-backed multimodal navigation MCP server enabling geocoding, route planning, POI discovery, and urban layout analysis. It provides a structured city graph to LLM apps without proprietary map APIs.
    8
  • A
    license
    A
    quality
    A
    maintenance
    A read-only MCP server for OpenStreetMap offering geocoding, routing, route optimization, isochrones, and POI search—requiring no API key and built for AI travel planning.
    11
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Finds marked hiking routes from OpenStreetMap filtered by locally-computed elevation gain, distance, loop shape, and car/chairlift access, providing consistent and tunable metrics instead of third-party scraped data.
    1
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Lets an LLM plan hikes anywhere in Switzerland by combining named routes, elevation profiles, weather forecasts, and public transport.
    7

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.