Skip to main content
Glama
com.macaroonnetwork/mcp-server

com.macaroonnetwork/mcp-server

macaroonnetwork-mcp

MCP discovery router for Macaroon Network, a marketplace where agents find evidence-backed products and pay per successful query.

The payment rail exposed by this release is x402 using USDC on Base mainnet. The package never holds a wallet or signs a payment. It returns the exact x402 challenge for the caller's own wallet infrastructure to sign, then accepts that signed proof on the retry.

Tools

  • macaroons_search — search sale-ready products by natural-language intent. Free.

  • macaroons_metadata — retrieve free freshness and content-hash metadata for a feed target.

  • macaroons_categories — retrieve the canonical category registry and exact mapped-product counts. Free.

  • macaroons_discover_mcp — retrieve evidenced live Macaroon MCP servers and their transports. Free.

  • macaroons_sources — retrieve reviewed source and rights records, with explicit partial-coverage reporting. Free.

  • macaroons_execute — execute an x402 USDC product and receive the predicate-verified result and receipt.

Related MCP server: hypawave

Paying with x402

When a product needs payment, macaroons_execute returns an x402_payment_required result instead of hiding the challenge:

{
  "x402_payment_required": true,
  "resource_url": "https://api.macaroonnetwork.com/execute/...",
  "amount_atomic": "3000",
  "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "network": "eip155:8453",
  "pay_to": "0x33cc...",
  "extra_name": "USD Coin",
  "extra_version": "2",
  "max_timeout_seconds": 60,
  "x402_version": 2
}

Sign the exact payment described by the challenge with your own wallet or Coinbase CDP infrastructure. Then call macaroons_execute again with identical arguments plus payment_signature. x402 exact settlement uses one signed retry; there is no invoice-polling flow.

Install

pip install macaroonnetwork-mcp

Use with an MCP client

{
  "mcpServers": {
    "macaroonnetwork": {
      "command": "macaroonnetwork-mcp"
    }
  }
}

The default registry is https://api.macaroonnetwork.com. For local development, override it with MACAROONS_REGISTRY_URL.

License

MIT

Available Tools

4 tools
macaroons_executeA

Execute a paid marketplace capability by capability_id. Pays via Lightning L402 against a hold invoice — payment only settles if the acceptance predicate passes against the bridge response; bridge errors and predicate failures refund. If no wallet is configured (the default), returns payment_required with a real invoice for you to pay yourself.

Inputs: input (required), capability_id (required), predicate, max_spend_sats, +1 more.

macaroons_metadataA

Get free metadata for a feed target before purchasing. Returns freshness and content_hash. No payment required.

Inputs: target_id (required).

macaroons_purchaseA

Purchase change-events for a feed target. Pays via Lightning L402 against a hold invoice — payment only settles if the acceptance predicate passes against the delivered payload; otherwise it is fully refunded. If no wallet is configured (the default), returns payment_required with a real invoice for you to pay yourself.

Inputs: predicate (required), target_id (required), limit, since, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct stage: search discovers capabilities, metadata inspects a specific feed target pre-purchase, purchase acquires change-events, and execute runs a paid capability. Search and metadata both return freshness, which causes slight overlap, but their inputs and outputs are different enough for an agent to choose correctly.

    Naming Consistency4/5

    All tools share the macaroons_ prefix and mostly follow a macaroons_<action> pattern. Three are clear verbs (search, purchase, execute), while metadata is a noun rather than get_metadata, creating a minor inconsistency but not a confusing one.

    Tool Count5/5

    Four tools is well-scoped for this marketplace-focused server: discover, inspect, acquire, and use. Each tool has a clear purpose and none feel redundant or extraneous.

    Completeness4/5

    The core lifecycle for a paid capability marketplace is covered: find capabilities, inspect feed metadata, purchase change-events, and execute capabilities. A minor gap is the lack of a tool to list previously purchased capabilities or check wallet/payment status, but agents can likely work around that using returned capability IDs.

    Maintenance

    ActivitySlowing
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to discover, purchase, and query blockchain-based datasets using Filecoin/IPFS storage with Ethereum NFT access controls and Lit Protocol encryption. Provides a decentralized marketplace for secure dataset trading with automatic purchase workflows and SQL query capabilities.
      0
      -
    • A
      license
      A
      quality
      B
      maintenance
      Give your agent an address: private agent-to-agent messaging, free encrypted file handoffs, and Lightning commerce. Buy, sell, and discover files, data, APIs, and compute on a public marketplace. Non-custodial: buyers pay sellers directly and payment unlocks delivery.
      27
      132 npm
      MIT No Attribution
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to access verifiable DePIN supply-side telemetry, browse and purchase data products using credits, query datasets, and verify data provenance with cryptographic and zero-knowledge tools.
      10
      91 npm
      MIT