Skip to main content
Glama
inviti8

Obolus

by inviti8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Obolus

No user-submitted related servers found.

    Related Servers

    • xpay

      xona-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.
      335 npm
      1
      MIT

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT
    • mpp32-mcp-server by MPP32

      mpp32-mcp-serverofficial

      MPP32
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that allows AI agents to discover and pay for thousands of APIs (x402 on Solana/Base) using a single key, with automatic payment handling and a federated catalog of machine-payable endpoints.
      234
      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

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool covers a distinct part of the workflow: fetching a paid URL, inspecting wallet state, and getting funding instructions. There is no meaningful overlap or likely misselection between them.

    Naming Consistency4/5

    All names are lowercase snake_case and clearly grouped by domain: x402_fetch for the payment fetch action, wallet_status and wallet_funding_info for wallet concerns. The one minor inconsistency is that x402_fetch is verb-led while the other two are noun-led, but the pattern is still predictable and readable.

    Tool Count5/5

    Three tools is small but ideal for this narrow purpose: one action tool, one status tool, and one funding-info tool. Each earns its place and none feel redundant.

    Completeness4/5

    The set covers the full user journey: check if the wallet can pay, perform the paid fetch, and get funding instructions if the wallet cannot pay. Minor gaps exist, such as no tool for adjusting caps or spending limits, but those appear to be intentionally configuration-level concerns rather than agent actions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources