Skip to main content
Glama
nonameuserd

paybond-mcp

by nonameuserd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to paybond-mcp

No user-submitted related servers found.

    Related Servers

    • pact-mcp

      pact-layer
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Pact, an escrow protocol for agent-to-agent commerce, enabling agents to create pacts, fund escrow, deliver work, and settle with an LLM evaluator as dispute backstop.
      25 npm
      MIT

    • WhitePact

      Guruprasath-Annadurai
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      48 PyPI
      2
      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

    • l402-kit-mcp

      ShinyDapps
      A
      license
      A
      quality
      C
      maintenance
      MCP server for l402-kit — enables AI agents (Claude, Cursor, etc.) to autonomously pay Bitcoin Lightning-protected APIs. Tools: l402_fetch, l402_balance, l402_spending_report. Run with: npx l402-kit-mcp
      4
      53 npm
      3
      MIT

    • Amanah MCP

      SyaugiAlkaf
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to propose USDC payments on the Soroban blockchain with deterministic policy enforcement and injection protection, while providing payment status and attestation tools.
      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

    A3.6/5.0

    Scored across 31 tools

    Disambiguation3/5

    The descriptions contain strong cross-references, but the tool set still has several overlapping families: low-level versus high-level intent creation/evidence submission, multiple receipt get/verify tools, and multiple Signal analytics reads. An agent can pick the wrong tool without carefully reading the lengthy do-not-use guidance.

    Naming Consistency5/5

    Every tool follows the same paybond_<verb>_<noun> snake_case pattern, with protocol-versioned tools consistently marked _v1. The high-level and low-level pairs use clear qualifiers like spend_intent versus intent, so the naming convention is uniform and predictable.

    Tool Count2/5

    Thirty-one tools is well beyond the typical well-scoped range and makes the server feel heavy. Several tools could be consolidated into shared families or split into separate servers by domain, such as Harbor intents, Signal analytics, A2A discovery, and receipt verification.

    Completeness2/5

    The descriptions reference paybond_fund_intent as a prerequisite for spend authorization, but that tool is not exposed in this set. The Harbor intent lifecycle also lacks visible update, cancel, release, or refund tools, so an agent cannot complete a full end-to-end spend workflow without hitting dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources