Skip to main content
Glama

Related Servers

Alternatives to AgentaOS

  • A
    license
    Not graded
    quality
    C
    maintenance
    The Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.
    21,738 npm
    2,032
    -
  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that provides tools for interacting with the Paddle Billing API, enabling users to manage products, prices, customers, transactions, subscriptions, and create custom financial reports.
    63
    608 npm
    49
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    The Dodo Payments MCP Server integrates with agentic frameworks to provide a lightweight, serverless-compatible interface for AI-driven payment operations like billing, subscriptions, and customer management. It enables autonomous agents to securely act on behalf of users using the Dodo Payments
    2,118 npm
    54
    Apache 2.0

Related Servers

  • A
    license
    A
    quality
    D
    maintenance
    MCP server for MAIB e-commerce payments (Moldova). Supports payments, refunds, recurring billing, one-click payments, and transaction status via OAuth 2.0.
    8
    13 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Payment infrastructure MCP server enabling AI agents to make gasless USDC payments on Base and JIT single-use virtual card checkouts, with zero-trust card handling, merchant checkout hints, and signed receipts.
    13
    602 npm
    1
    MIT
  • F
    license
    B
    quality
    D
    maintenance
    MCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.
    15
    58 npm
    -

TDQS

A3.5/5.0

Scored across 31 tools

Disambiguation4/5

Most tools target a distinct resource+action and descriptions clarify boundaries well. The one real hazard is agenta_subscriptions_credit (adds credit) vs agenta_subscriptions_credits (lists credits) — near-identical names with opposite effects, plus verify_submit/verify_resubmit and audit_request/audit_show require reading descriptions to separate.

Naming Consistency4/5

Everything uses the agenta_ prefix with snake_case and a predictable resource_verb order (products_create, pay_checkout, discounts_archive), which is very consistent. The credit/credits singular-plural pair is the main blemish on an otherwise uniform scheme.

Tool Count3/5

31 tools is heavy against the rubric's 25+ threshold, though the domain genuinely spans many resources (verification, businesses, products, subscriptions, discounts, invoices, customers, pay, audit). It is defensible but at the upper edge of comfortable scoping.

Completeness4/5

Coverage is broad and lifecycle-aware: full verification flow, business management, product/subscription/discount/invoice operations, and checkout listing. Minor gaps exist — products have no update/delete/archive, and customers can only be listed, not fetched individually.

Maintenance

ActivityActive
ResponsivenessUnresponsive