Skip to main content
Glama
thezeivier

mcp-reliable-adapter

by thezeivier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to mcp-reliable-adapter

No user-submitted related servers found.

    Related Servers

    • io.github.GSterlingPress/once

      GSterlingPress
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that prevents duplicate side effects in AI agents by using idempotency keys and durable receipts, ensuring actions like refunds, emails, or orders execute exactly once even across retries.
      -

    • fairlead

      yashaswip
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes customer record lookup and refund triggering over stdio, with a gateway layer for authorization, streaming PII redaction, rate limiting, and failover to a backup provider.
      -

    • mcpgov

      harsha-moparthy
      F
      license
      Not graded
      quality
      B
      maintenance
      A production-grade MCP server over Postgres, providing secure data operations with tenant isolation, exact-once mutations, loop-aware rate limiting, and a tamper-evident audit trail.
      -

    • MCP Server for Intercom

      raoulbia-ai
      A
      license
      A
      quality
      F
      maintenance
      An MCP-compliant server that enables AI assistants like Claude Desktop to access and analyze Intercom support tickets with full conversation history.
      4
      8
      Apache 2.0

    • Shoot Email

      powersurge01
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides AI agents with a persistent, agent-native email mailbox for sending, receiving, and managing emails through bounded-context retrieval, idempotent operations, and explicit acknowledgement.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one submits a support ticket, the other retrieves delivery status for a previously submitted ticket. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: submit_support_ticket and get_delivery_status. The naming style is uniform and predictable.

    Tool Count3/5

    With only two tools, the server feels thin, but the tools form a natural pair for a reliable adapter focused on submission and status tracking. The count is borderline but not unreasonable for the narrow scope.

    Completeness4/5

    The core workflow of durably accepting a ticket and checking its delivery state is covered. A retry or cancellation operation could be useful, but the primary path has no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources