Skip to main content
Glama
muhammadashir0

MandatePay

by muhammadashir0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MandatePay

No user-submitted related servers found.

    Related Servers

    • Safe4 by Safe4AI

      Safe4official

      Safe4AI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to verify proposed payments against their assigned task, budgets, permitted categories, and counterparties, returning an ALLOW or DENY decision with a tamper-evident audit trail.
      MIT

    • genpark-agentic-payment

      Alpha-Park
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to issue and validate cryptographic delegated payment mandates for tokenized checkout, enforcing spend limits, velocity thresholds, and merchant whitelists. Generates ephemeral single-use authorization tokens so commerce and workplace agents can complete purchases within policy boundaries.
      7
      MIT

    • gvnr

      instruxi-io
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables MCP clients to ask permission before an agent acts, returning allow, deny, or ask_human with receipts, and to monitor agent spend, limits, and recent decisions.
      430 npm
      Functional Source , Version 1.1, ALv2 Future

    • interlock-mcp

      Mustaqeem-Rafi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to use payment APIs safely by gating every tool call through deterministic mandates, value checks, and an exactly-once ledger, so they cannot pay twice or exceed authorisation.
      39 npm
      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.9/5.0

    Scored across 1 tool

    Disambiguation5/5

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

    Naming Consistency5/5

    A single tool follows a consistent verb_noun pattern ('request_payment_authorization'), which is clear and descriptive. No inconsistencies exist by definition.

    Tool Count3/5

    The server has only one tool, which feels thin for a system named 'MandatePay'—implying broader mandate management. While the tool itself is well-scoped, the overall surface is borderline minimal.

    Completeness2/5

    The tool covers only payment authorization, but the domain suggests the need for related operations like mandate creation, listing, updating, or checking status. Without these, agents face significant dead ends when managing mandates.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources