Skip to main content
Glama
MohamedXAdel

fortyguard-mcp

by MohamedXAdel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fortyguard-mcp

No user-submitted related servers found.

    Related Servers

    • HeatShield

      AscilCH
      A
      license
      A
      quality
      B
      maintenance
      HeatShield MCP server enables AI assistants with real-time spatial reasoning for urban heat wave safety. It provides tools for geocoding, weather/heat risk, air quality, finding cooling spots, and heat safety advice.
      6
      MIT

    • climate-risk-mcp-server

      AiAgentKarl
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with access to CO2 emissions data, climate projections, and risk assessments for heat, flooding, and drought, supporting ESG analysis and CSRD compliance.
      MIT

    • EnergyAI MCP

      jdhart81
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides free energy intelligence APIs for AI agents: solar production estimates, US clean-energy incentives by ZIP, home Energy Node Scores, contractor search, and consented installer routing.
      MIT

    • tes-mcp-server

      Traia-IO
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes public weather and climate data through a standardized API, allowing AI agents to retrieve current conditions, 7-day forecasts, and historical data. It enables weather-aware automation and data enrichment for conversational agents and travel planning.
      -
    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.1/5.0

    Scored across 12 tools

    Disambiguation3/5

    create_heatmap and submit_heatmap both submit heatmaps and differ only in whether they wait inline, which creates real selection ambiguity. The other submit_* tools are clearly separated by modality, and validate_aoi/split_aoi/get_* tools have distinct purposes.

    Naming Consistency4/5

    Tool names mostly follow a consistent snake_case verb_noun pattern, with clear submit_* and get_* families plus check_status. The outlier is create_heatmap, which semantically overlaps with submit_heatmap and breaks the established submit_* convention.

    Tool Count5/5

    12 tools is well within the ideal range and each tool has a clear role covering local AOI utilities, account/storage info, several analysis submission types, result retrieval, and status checking. None of the tools feel redundant or extraneous.

    Completeness4/5

    The server covers the core workflow well: validate and split AOIs, submit heatmaps synchronously or asynchronously, poll status, retrieve and slice results, and get environmental parameters. There is no explicit cancel/list-jobs or archive-deletion tool, but those are not essential given the designed workflow and user-managed local storage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources