Skip to main content
Glama
AgentaOS

AgentaOS

Official
by AgentaOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to AgentaOS

No user-submitted related servers found.

    Related Servers

    • maib-mcp

      theYahia
      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

    • Z-ZERO MCP

      Dempty-glitch
      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
      138 npm
      1
      MIT

    • buchpilot-mcp

      makririch
      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
      40 npm
      -
    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

    C2.8/5.0

    Scored across 19 tools

    Disambiguation4/5

    Tools are largely distinct, with clear resource-action separation (e.g., audit_request vs audit_show, pay_checkout vs pay_get). Minor potential confusion between agenta_status_get (account/go-live overview) and agenta_verify_status (verification progress), but descriptions differentiate them well.

    Naming Consistency4/5

    Consistent agenta_<resource>_<action> snake_case pattern throughout. Minor deviations: some actions are nouns (status, declaration, receipt) rather than verbs, but the pattern remains predictable.

    Tool Count4/5

    19 tools is slightly above the ideal 3-15 range but reasonable for a full payments and merchant onboarding platform. Each tool appears to serve a distinct function without obvious redundancy.

    Completeness3/5

    Core onboarding (audit, verification) and payment workflows (checkout, subscriptions, invoices) are covered. Notable gaps include refund operations, product/customer update or delete, and subscription creation, which may limit agents in some scenarios.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources