Skip to main content
Glama
hniska

trafikverket-mcp

by hniska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to trafikverket-mcp

No user-submitted related servers found.

    Related Servers

    • aria-mcp-trafik-dk

      kimhjort
      A
      license
      A
      quality
      C
      maintenance
      Provides access to real-time Danish road traffic events, roadworks, and queues via public data from Vejdirektoratet, enabling AI assistants to check road conditions without any API keys.
      3
      MIT

    • trafikkmeldinger-mcp

      smlhus1
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Norwegian traffic messages (roadworks, closures, detours) from Statens vegvesen, filtered by route and time window. Supports both current and future travel times, with tools for route-based and general searches.
      3
      MIT

    • Apiverket MCP Server

      vinvuk
      A
      license
      A
      quality
      F
      maintenance
      Query Swedish public data from AI tools. Includes company data, SCB statistics, weather, transport, public agencies, and more through the Apiverket API.
      2
      35 npm
      2
      MIT

    • mcp-swedish-weather

      robobobby
      A
      license
      B
      quality
      D
      maintenance
      Provides access to current weather conditions and hourly forecasts for any location in Sweden using the SMHI Open Data API. It supports built-in city lists, coordinate inputs, and geocoding fallback to deliver detailed meteorological data without requiring authentication.
      2
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, such as cameras, weather stations, traffic situations, traffic flow, and road conditions. However, get_weather_station, list_weather_stations, get_weather_stations_near_location, and get_weather_observations have some overlap in weather-station-related retrieval, and get_road_conditions partially overlaps with weather station road condition data. Descriptions help clarify, but an agent could still hesitate between current station weather and historical observations.

    Naming Consistency4/5

    The set is almost entirely consistent snake_case with a get_ prefix (e.g., get_weather_station, get_cameras, get_traffic_flow), which is predictable. The one deviation is list_weather_stations, which uses a different verb but is still conventional and readable. Overall the naming is coherent with a minor stylistic variation.

    Tool Count5/5

    Ten tools is a well-scoped size for a domain-specific Swedish traffic and weather data server. Each tool covers a distinct data type or access pattern, and there is no evident bloat or missing essential operation within the count itself.

    Completeness4/5

    The surface covers cameras (list, near-location, image), weather stations (list, specific, near-location, historical observations), traffic situations, traffic flow, and road conditions. This is broad and lifecycle-appropriate for the apparent domain. Minor gaps may exist, such as no direct near-location query for traffic situations, but agents can likely work around that with existing filters.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources