Skip to main content
Glama
Sign In
qingping-mcp

qingping-mcp

by nicolascoutureau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to qingping-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-airq-cloud

      CorantGmbH
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the air-Q Cloud API, enabling remote retrieval of air quality sensor data and historical analysis through read-only tools like listing devices, fetching readings, and exporting charts or data.
      46 PyPI
      Apache 2.0

    • IQAir MCP Server

      Nanparam
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables retrieval of real-time air quality data from IQAir, including AQI, pollutant levels, weather, and forecasts for any location, via an MCP-compatible interface without an official API key.
      -

    • AQICN MCP Server

      mattmarcin
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with the World Air Quality Index to fetch real-time air quality data for cities and coordinates worldwide via Model Context Protocol (MCP).
      1
      MIT

    • Zepp Cloud MCP

      aryarfani
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Amazfit/Zepp fitness data via the unofficial Zepp cloud API, exposing normalized health and workout metrics to MCP clients.
      AGPL 3.0

    • @aag/mcp-server

      GitHubMoreLikeGitGud
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a household assistant to answer personalized air-quality and pollen questions, plan outdoor activities, issue threshold-based alerts, and log symptoms using live Open-Meteo data. It exposes these capabilities as tools with spoken responses and structured content for MCP clients.
      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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools map to clearly distinct operations: latest readings, historical aggregation, alert retrieval, and interval configuration. There is no meaningful overlap between current vs. history or alerts vs. readings.

    Naming Consistency5/5

    All tools use a consistent `qingping_` prefix followed by a concise snake_case noun or verb phrase. The pattern is predictable and readable throughout.

    Tool Count5/5

    Four tools is well-scoped for a focused sensor-monitoring server, with each tool covering a distinct part of the lifecycle. No tool feels redundant or out of place.

    Completeness4/5

    The surface covers live readings, history, alerts, and device interval configuration, which are the core monitoring workflows. A device listing or sensor inventory tool would help multi-sensor setups, but the existing set is otherwise complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources