InnerVault

Burnbound

Stale Official MCP Registry, dev.burnbound

Let your AI agent pay x402 APIs within daily caps, allowed hosts and human approval.

Open the source (opens burnbound.dev) https://burnbound.dev/docs?utm_source=mcp-registry&utm_medium=directory&utm_campaign=g4-registro-mcp

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: BURNBOUND_KEY. Use a key with the least access you can.

What it is

MCP servers from dev.burnbound.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

@burnbound/mcp@0.7.0

From the server's entry in the official MCP Registry

Settings it asks for

  • BURNBOUND_KEY secret required · Agent key (bb_agent_…) created in the Burnbound dashboard. Sent only to the Burnbound API.
  • BURNBOUND_API · Burnbound API base URL. https:// only (http:// only for loopback). Set it for a self-hosted or local API.
  • BURNBOUND_AGENT_ID · Only with an org key instead of an agent key: the agent the tools act for. Ignored with an agent key.
  • BURNBOUND_WALLET_PROFILE · Local wallet profile for client-side signing (created with `npx -y @burnbound/mcp wallet init`). 1–32 of a-z, 0-9, _ and -.
  • BURNBOUND_HOME · Directory for the local wallet file when the OS keychain is not used.
  • BURNBOUND_MAX_RESPONSE_BYTES · fetch_paid response body cap in bytes (maximum 10485760). Longer bodies are truncated.
  • BURNBOUND_FETCH_TIMEOUT_MS · fetch_paid deadline for the whole exchange with the URL, between 1000 and 120000 ms.
  • BURNBOUND_APP_URL · Origin of the Burnbound panel, for the approval link a held payment returns (and opens in clients with URL-mode elicitation). Default: the API origin when it…
  • BURNBOUND_APPROVAL_WAIT_MS · How long fetch_paid waits for the human's decision once the approval page is opened from the chat, between 0 and 50000 ms. 0 returns pending_approval at once.
  • BURNBOUND_BASE_RPC_URL · diagnose_payment: Base RPC used to read the paying wallet's USDC balance. https:// only. Only the wallet address is sent to it.
  • BURNBOUND_BASE_SEPOLIA_RPC_URL · diagnose_payment: Base Sepolia RPC used to read the paying wallet's USDC balance. https:// only.

Related

  1. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  2. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  3. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  4. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  5. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation

  6. Playwright MCP

    MCP servers

    Lets an agent drive a real browser: open pages, click, fill in forms and read what's on screen.

    Hand-checked InnerVault (hand-checked), Microsoft Apache-2.0

    claude mcp add playwright npx @playwright/mcp@latest