Skip to main content
Glama

Related Servers

Alternatives to minia2a-mcp

  • A
    license
    Not graded
    quality
    F
    maintenance
    MCP server for the x402 micropayment marketplace minia2a.uk, enabling AI agents to discover, call, and pay for 1,700+ services using USDC micropayments with no API keys or subscriptions. Supports registration, credits, service browsing, and autonomous calling with Claude Code auto-mode.
    1,698 npm
    1
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to discover and call pay-per-call APIs on the minia2a.uk marketplace, including service browsing, endpoint validation, and x402 payment-flow handling. Also supports self-custody wallet registration and live platform statistics.
    401 npm
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    AI Agent Hub is a pay-per-call API platform for AI agents Every call is billed automatically in USDC using the x402 protocol - there is no API key, no account, and no signup. Agents get instant access to data queries, file storage, and ad impressions, paying only for what they actually use. The same tools are also exposed natively over MCP, so any MCP-capable agent can discover and call them
    -

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation4/5

The tools mostly target distinct actions—listing services, getting details, registering, buying credits, calling services, and checking endpoints—so an agent can usually select correctly. The main overlap is that minia2a_credits also reports platform-level stats like minia2a_get_stats, and the payment-related paths in buy_credits and call_service could cause mild confusion.

Naming Consistency4/5

Six of eight tools follow a clear minia2a_<verb>_<noun> pattern, and all names share a consistent prefix and snake_case style. minia2a_register is a verb-only name and minia2a_credits is a noun-only name, which breaks the otherwise predictable pattern.

Tool Count5/5

Eight tools is well within the ideal range and each one covers a meaningful part of the x402 marketplace workflow. The size feels intentional: discovery, registration, payment, calling, and validation are all represented without unnecessary duplication.

Completeness4/5

The set supports the full consumer loop: discover services, inspect them, register a wallet, understand credits, buy/claim credits, call services, and validate endpoints. The only notable gap is the lack of a direct balance or transaction-history view, but the V5 design intentionally surfaces that state through call responses and 402 headers.

Maintenance

ActivityActive
ResponsivenessUnresponsive