Skip to main content
Glama
lostnumber07

SHEARLINE

by lostnumber07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SHEARLINE

No user-submitted related servers found.

    Related Servers

    • Weather MCP Server

      azwawy
      F
      license
      Not graded
      quality
      D
      maintenance
      A demo MCP server that provides AI assistants access to live US weather data via the free National Weather Service API, offering forecast and alert tools without requiring an API key.
      -

    • mcp-hazards

      jsuich
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents grounded access to US natural-hazard data — weather alerts, forecasts, earthquakes, and FEMA flood zones — from free, keyless US government APIs.
      MIT

    • mcp-weather

      minwoo129
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework to provide weather-related tools and data to AI clients. It enables integration of weather capabilities and custom tools into the MCP ecosystem for use with platforms like Claude Desktop.
      9 npm
      -

    • Weather MCP Demo

      huanhuang1
      F
      license
      Not graded
      quality
      C
      maintenance
      This MCP server provides tools to get current weather, forecasts, and weather alerts from the US National Weather Service via REST APIs, enabling AI agents to query live weather data.
      1
      -

    • pythonWeatherMCP

      savkolar
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides US National Weather Service forecasts and active weather alerts through MCP tools, using no API key but supporting US locations only.
      -
    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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a clearly different severe-weather data source or time horizon: warnings, outlook, analyzed environment, forecast trend, MRMS products, lightning, current reports, historical reports, radar metadata, and a composite brief. Even the two radar-related tools are cleanly separated by purpose, and get_point_environment/get_environment_trend are explicitly distinguished as now vs forecast.

    Naming Consistency5/5

    All ten tools follow a consistent get_<descriptive_noun> pattern that reflects both action and resource. The names are uniformly snake_case with no mixed conventions or vague verbs.

    Tool Count5/5

    Ten tools is well within the ideal range and each one corresponds to a distinct severe-weather data product needed for situational awareness. The count is neither bloated nor too thin for the server's stated domain.

    Completeness5/5

    The surface covers the full severe-weather assessment workflow: current warnings, forecast outlooks, current and trended environment parameters, observed radar/lightning, recent and historical storm reports, and a synthesizing brief. There are no obvious dead ends or missing operations for a point-based CONUS severe-weather tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources