lokal
Related Servers
Alternatives to lokal
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and compare Norwegian grocery prices across multiple chains, retrieve price history, and access product details through the kassal.app API.MIT
- FlicenseAqualityCmaintenanceEnables natural-language search and retrieval of live statistics from Norway's Statistics Norway, including table discovery, dimension selection, and latest-figure queries, all indexed locally for fast responses.6-
- AlicenseNot gradedqualityCmaintenanceProvides LLM-friendly weather tools and Norwegian place name resolution via MCP, enabling weather forecasts, air quality, marine conditions, and activity planning.1MIT
- AlicenseBqualityAmaintenanceMCP server providing typed tools for Norwegian public data sources, enabling natural language queries to official datasets like SSB, Brønnøysund, MET, Kartverket, Entur, and more, without requiring API keys.47MIT
- AlicenseAqualityBmaintenanceEnables AI agents to access Norwegian public transport and geospatial data, including trip planning, stop departures, address search, elevation, and administrative boundaries, via the Entur and Kartverket APIs.2135 npmMIT
- AlicenseAqualityBmaintenanceEnables searching products, viewing product details, managing the basket, and accessing order history on nemlig.com through natural language. It does not support placing orders or accessing payment cards.6MIT
TDQS
Scored across 4 tools
The tools have overlapping purposes that could cause confusion. 'lokal_discover' and 'lokal_search' both search for producers, with 'discover' offering structured filtering and 'search' using natural language, making them potentially ambiguous. 'lokal_info' and 'lokal_stats' are distinct, but the two search tools may lead to misselection due to unclear boundaries in their use cases.
All tool names follow a consistent 'lokal_' prefix with a descriptive suffix pattern (e.g., discover, info, search, stats). This predictable verb_noun-like structure is clear and uniform throughout the set, with no deviations in style or convention.
With 4 tools, the count is reasonable and well-scoped for a food producer registry server. It covers key operations like searching, retrieving details, and getting platform stats, though it might feel slightly thin if more advanced features are expected, but overall it's appropriate for the domain.
The tool set covers basic search and retrieval functions but has notable gaps. There is no ability to create, update, or delete producer data, which limits CRUD coverage. However, for a read-only registry focused on discovery and information, it handles core workflows adequately, leaving agents to work around the lack of write operations.