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.
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.
Tool Definition Quality
Average 3.4/5 across 5 of 5 tools scored.
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.
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.
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.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseAqualityCmaintenanceOSM-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
- AlicenseAqualityAmaintenanceA 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.11MIT
- AlicenseAqualityAmaintenanceFinds 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.1MIT
- FlicenseNot gradedqualityCmaintenanceLets an LLM plan hikes anywhere in Switzerland by combining named routes, elevation profiles, weather forecasts, and public transport.7
Your Connectors
Sign in to create a connector for this server.