Skip to main content
Glama
stablevoy-mcp

stablevoy-mcp

Official

Related Servers

Alternatives to stablevoy-mcp

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to perform and manage payments through the Model Context Protocol, including paying, checking balances and history, registering bots, setting spending limits, discovering supported networks and tokens, inspecting commissions, and managing bot pools. It also supports governed tool calls with policy decisions, human approval, and tamper-evident audit traces.
    12
    7 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to accept non-custodial crypto payments by creating hosted checkout sessions and invoices, tracking payments and wallets, registering and verifying signed webhooks, purchasing prepaid credits, and querying or exporting the book of record. Test-mode payment simulation lets agents verify the full flow end to end.
    MIT
  • A
    license
    B
    quality
    B
    maintenance
    Enables an AI coding assistant to create and manage products, prices, payment links, invoices, customers, subscriptions, entitlements, refunds, and webhooks, simulate test payments, read payments and receipts, and verify buyer access through a crypto payment API.
    38
    211 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables merchants to preview, create, list, and track invoices with line items, VAT, payment links, due dates, and PDFs using an assistant secret key, while ensuring payments go to the merchant's wallet and never spend funds.
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Enables conversational AI agents to manage Razorpay payments directly, including payment lookups, order creation, refunds, UPI QR generation, and real-time webhook triage via the Model Context Protocol.
    -

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct resource and action: list_stores vs get_store, and list_invoices vs get_invoice vs create_invoice. The descriptions explicitly explain when to use each alternative, leaving no meaningful overlap.

Naming Consistency5/5

All five tools follow a consistent snake_case verb_noun pattern: list_stores, get_store, list_invoices, get_invoice, create_invoice. There are no mixed conventions or vague verbs.

Tool Count4/5

Five tools is a reasonable, focused surface for store and invoice operations. It is slightly thin in that stores are read-only and invoices lack lifecycle actions, but every included tool has a clear purpose.

Completeness3/5

The server covers listing stores, inspecting store settings, creating invoices, and retrieving/listing invoices. However, invoice lifecycle operations such as canceling, updating, or refunding are absent, and store settings are read-only by design, leaving notable gaps for agents handling payment workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues