Skip to main content
Glama

Related Servers

Alternatives to mister-parc-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables users to inspect ephemeral GitHub Actions runner fleet status, SLOs, incidents, capacity recommendations, and cost evidence through read-only MCP tools, without allowing infrastructure or cluster mutations.
      5
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      Provides coding agents read-only access to Depot's CI failure diagnoses, container build forensics, run history, cache effectiveness, registry contents, and usage data through MCP tools.
      28
      76 npm
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to list fleet packages, generate merged MCP configs, run production checklists and doctor reports, inspect catalog health, and execute release ship gates. It provides a single MCP interface for connecting and validating the production toolchain.
      101 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for MOJAQ: give any AI assistant natural-language access to your EU-hosted app's deploys, errors, logs, uptime and incidents.
      10 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that lets an assistant read Club Alpin Français section websites running plateforme-club-alpin: outing and training agendas, outing details with places left and prices, and — with a member login — your own registrations, history and profile. It only issues GET requests against an allow-list, so nothing on the site can be changed.
      7
      MIT

    TDQS

    A3.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    The tools divide cleanly into `parc_*` observability queries and `socle_*` shared-foundation queries, with list/detail distinctions made explicit (`depots` vs `depot`, `etat` vs `a_faire`, `offre` vs `module`/`workflow`/`usage`). The two search tools, `parc_chercher` and `socle_chercher`, target different domains and their descriptions clarify the boundary.

    Naming Consistency4/5

    Names consistently use a domain prefix (`parc_` or `socle_`) plus a French noun or verb phrase, and singular/plural forms are used meaningfully. The set is not a strict verb_noun convention and mixes nouns with verbs like `chercher`, but it remains predictable and readable.

    Tool Count4/5

    Twenty tools is on the heavy side, but the server covers several distinct subdomains: repository health, alerts, sites, trends, libraries, Renovate, and the shared socle. Each tool appears to earn its place rather than duplicating another, though the surface is broad enough to be slightly unwieldy.

    Completeness4/5

    The read-only monitoring and socle-inspection surface is largely complete: repository summaries and details, CI failures, PRs, alerts, sites, Renovate, libraries, trends, journal, and socle modules/workflows/docs are all covered. Minor gaps may remain for deep per-PR or per-workflow-run inspection, but agents can work around them.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing