Skip to main content
Glama
Mmarucr7

customer-refund-mcp-server

by Mmarucr7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to customer-refund-mcp-server

No user-submitted related servers found.

    Related Servers

    • trigger_refund

      havvari
      F
      license
      A
      quality
      B
      maintenance
      Enables clients to issue refunds over stdio through a JSON-RPC tool call backed by a ledger. Malformed arguments are rejected with a real -32602 error code instead of the SDK's default isError result.
      1
      -

    • customer-mcp

      dkreme514
      F
      license
      B
      quality
      C
      maintenance
      Enables retrieval of customer records and triggering refunds via MCP tools, supporting both stdio and streamable HTTP transports.
      2
      -

    • resolve.mcp_server

      yusufdeveloper2903
      A
      license
      A
      quality
      B
      maintenance
      Exposes the customer-support tool registry over stdio so Claude Desktop or Claude Code can look up customers and orders, track shipments, search help-center articles, update shipping addresses, issue policy-checked refunds and escalate to a human. It reuses the same pydantic validation, ownership and refund policy, approval gate and audit logging as the HTTP agent, with the customer identity taken from server configuration rather than the model.
      7
      MIT

    • mcp-member-ops

      Lilim-ing
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to query member segment summaries, campaign history, and masked member profiles over stdio JSON-RPC, with role-based capability gating that reserves row-level profile data and campaign task creation for higher-privilege roles. Also serves segment-definition and schema resources plus a churn-review prompt, while logging every allowed and denied call to an audit trail.
      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

    A3.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves a customer record, while the other performs a refund action. There is no meaningful overlap or risk of selecting the wrong tool for a given task.

    Naming Consistency5/5

    Both names use a consistent snake_case verb_noun pattern: get_customer_record and trigger_refund. The verbs differ, but they accurately reflect distinct actions and remain predictable.

    Tool Count3/5

    Two tools are enough for a minimal lookup-and-refund workflow, but the surface feels thin for a refund server. There is little room for supporting operations such as refund status checks or history retrieval.

    Completeness3/5

    The core path of retrieving a customer and issuing a refund is covered, but lifecycle coverage is incomplete. There are notable gaps around refund history, refund status, idempotency, or canceling/querying previously issued refunds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources