Skip to main content
Glama
Flyingmiata-droid

paytriage

by Flyingmiata-droid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to paytriage

No user-submitted related servers found.

    Related Servers

    • payment-engineering-guardrail

      jonji886
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to safely integrate cross-border payments by providing structured payment knowledge, deterministic validation of idempotency, security, and state-machine rules, webhook testing, executable pytest generation, and diagnosis for Python/FastAPI Checkout projects.
      -
    • attest-mcp by attestagents

      attest-mcpofficial

      attestagents
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to scan payment endpoints for safety, returning a letter grade (A–F) and verdict before authorizing payments.
      2
      27 npm
      MIT

    • error-broker

      amsultan2010
      A
      license
      Not graded
      quality
      B
      maintenance
      Classifies agent errors and provides clear recovery actions (retry, escalate) with configurable categories and strategies, plus MCP tools for direct agent use.
      8 npm
      MIT

    • Payment Orchestrator MCP

      vryahn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to interrogate payment routing decisions through six tools: route transactions, explain decisions, simulate scenarios, inspect segment evidence, normalize decline codes, and review backtest summaries. It provides read-only access to the routing engine, allowing natural-language queries without modifying any decisions.
      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

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly singular and distinct.

    Naming Consistency5/5

    The single tool 'triage_payment_error' follows a clear verb_noun pattern, consistent with best practices. No inconsistency exists in a one-tool set.

    Tool Count3/5

    The tool count is at the thin end of the spectrum (1 tool), which feels minimal for a server, but the narrow scope of payment error triage makes it borderline acceptable.

    Completeness5/5

    The single tool fully addresses the stated purpose of triaging payment errors, providing cause, next steps, severity, and retry safety—no obvious gaps for this focused domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources