Skip to main content
Glama
RAMB4pi

Harthad Status MCP

by RAMB4pi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Harthad Status MCP

No user-submitted related servers found.

    Related Servers

    • identity-mcp

      CarlademarchiV
      F
      license
      Not graded
      quality
      C
      maintenance
      Institutional MCP server that centralizes access to identity, institutional profiles, and basic person data. Currently a bootstrap with no business logic or tools implemented.
      -

    • Universal MCP Tool Framework

      ttacleinad-boop
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a reusable MCP server foundation with explicit tool registration, operation-mode separation, scope-based permissions, structured results, and built-in health/status tools.
      MIT

    • nitro-mcp-server

      peterbud
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP client interaction via streamable HTTP, providing example tools (echo, getPostsByUser) and resources (posts, users) with pluggable authentication providers.
      6
      MIT

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -
    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

    B3.2/5.0

    Scored across 10 tools

    Disambiguation3/5

    Most tools have clear resource+action targets, but create_entry vs create_changelog_entry vs create_comment blur together, and update_service (status change creates a changelog atomically) overlaps conceptually with create_changelog_entry (records a status transition atomically). The read tools (get_status, get_context, get_profile, get_changelog) are distinguishable but adjacent enough to require careful reading.

    Naming Consistency5/5

    All ten tools follow a clean verb_noun snake_case pattern (get_, create_, update_, list_). The only mild quirk is that create_entry doesn't name the entity type the way create_changelog_entry and create_service do, but the convention itself is unbroken.

    Tool Count5/5

    Ten tools is well within the ideal range, and each maps to a plausible operation (read profile/status/context, manage services, manage changelog and entries, comment). No filler or redundant wrappers.

    Completeness3/5

    The service and changelog surfaces are reasonably covered, but there is no read/list for entries or comments (only creation), no delete or update for entries/changelog, and no delete_service. Agents attempting to inspect or clean up created data will hit dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources