npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agenticpay/mcp-bridge

v0.0.2

Published

Real MCP server (stdio + @modelcontextprotocol/sdk) that exposes x402-paywalled HTTP endpoints as MCP tools. Drop into Claude Desktop, Cursor, or any MCP client.

Readme

@agenticpay/mcp-bridge

A real MCP server (stdio transport, @modelcontextprotocol/sdk) that exposes x402-paywalled HTTP endpoints as MCP tools. Drop into Claude Desktop, Cursor, Continue.dev, or any MCP client.

The bridge holds a Solana keypair, signs each x402 payment payload, and settles via a facilitator on the agent's behalf. The MCP client sees normal MCP tools — it never touches the payment plumbing.

Why this exists

@agenticpay/mcp-server is the resource server (the place that wants to get paid). @agenticpay/mcp-bridge is the client adapter that makes those paid endpoints appear as native MCP tools to AI clients that already speak MCP.

Use case: you want Claude Desktop to be able to call paid APIs without managing wallets or signing payments yourself. The bridge handles it.

Install / use with Claude Desktop

// ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agenticpay": {
      "command": "npx",
      "args": ["-y", "@agenticpay/mcp-bridge"],
      "env": {
        "AGENTICPAY_BRIDGE_KEYPAIR": "[12,34,...your 64-byte keypair]",
        "AGENTICPAY_BRIDGE_NETWORK": "solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1",
        "AGENTICPAY_BRIDGE_RPC": "https://api.devnet.solana.com",
        "AGENTICPAY_BRIDGE_TOOLS": "[{\"name\":\"reverse_string\",\"description\":\"Reverse a string. Costs 0.001 USDC.\",\"url\":\"http://localhost:4021/tools/reverse\",\"inputSchema\":{\"text\":{\"type\":\"string\"}}}]"
      }
    }
  }
}

Restart Claude Desktop. The agenticpay tools (e.g. reverse_string) appear in the conversation. Claude calls them; the bridge pays, settles, returns the result.

Programmatic use

import { createBridge } from "@agenticpay/mcp-bridge";
import { z } from "zod";

await createBridge({
  keypairBytes: [12, 34, /* ... 64 bytes */],
  network: "solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1",
  rpcUrl: "https://api.devnet.solana.com",
  tools: [
    {
      name: "reverse_string",
      description: "Reverse a string. Costs 0.001 USDC.",
      url: "http://localhost:4021/tools/reverse",
      inputSchema: { text: z.string() },
      formatResult: (body) => (body as { result: string }).result,
    },
  ],
});

Funding the bridge wallet

The wallet pays USDC for every tool call. Devnet:

  • SOL: https://faucet.solana.com
  • USDC: https://faucet.circle.com (Solana Devnet)

The facilitator (e.g. our hosted devnet endpoint) covers SOL gas — the bridge wallet only needs USDC.

Status

Pre-alpha. Devnet-validated. Mainnet works once you fund the wallet with real USDC and point at a mainnet-capable facilitator.

MIT licensed. See agenticpay monorepo.