Skip to main content
Glama
baseline-mcp
by swannman

Related Servers

Alternatives to baseline-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides AI agents with read access to Trane Tracer SC+ building automation systems for inventory and telemetry retrieval.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Pulls readings from a grower's own weather station and soil probes via vendor cloud APIs using the patron's own keys, normalizing every measurement to one schema in SI units and UTC. Enables listing stations and sensors, fetching current or historical series, and computing per-day agronomic summaries like temperature extremes, frost hours, rain, and degree-days.
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables interaction with Neptune Apex aquarium controllers through their local REST API, providing read-only monitoring of probes, outlets, power, inputs, and history by default, with opt-in write tools for outlet control, feed cycles, and guarded program edits.
      14
      AGPL 3.0
    • F
      license
      A
      quality
      F
      maintenance
      Query and control Orbit B-Hyve irrigation systems from MCP-compatible clients like Claude Code and Cursor.
      12
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Reads thermostat status and controls HVAC modes, holds, schedules, comfort sensors, settings, vacations, fan runtime, and on-screen messages for a single thermostat account, hosted remotely on Cloudflare Workers with bearer-protected, stateless access.
      109 npm
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Provides read-only access to DNSFilter's DNS security and filtering API, enabling users to query organizations, networks, policies, categories, block pages, and traffic and threat reports.
      57
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a unique read operation (listing, getting live data, history, etc.) with no overlaps. Tools like baseline_get_live and baseline_get_status are distinct: live gives a single device reading, status gives controller-wide snapshot.

    Naming Consistency5/5

    All tools follow a consistent 'baseline_verb_noun' pattern in snake_case. Verbs are either 'get' or 'list', with 'whoami' being the only exception but still clearly readable.

    Tool Count5/5

    With 12 tools, the server is well-scoped for an irrigation monitoring system. It covers key data types (companies, controllers, devices, zones, alarms, history, live, programs, reports, status) without overloading.

    Completeness4/5

    The tool set provides comprehensive read access to most data sources (alarms, history, live, programs, reports, status, device listing). Missing write operations (create, update, delete) which might be out of scope for a read-only server.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing