Skip to main content
ClaudeWave
dev55acc-ai avatar
dev55acc-ai

paid-mcp-metering

Ver en GitHub

Metered MCP tools. Free discovery over MCP; execution priced per call and settled in USDC via x402 v2.

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptMITActualizado today
ClaudeWave Trust Score
87/100
Trusted
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Documented (README)
Last scanned: 8/24/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/dev55acc-ai/paid-mcp-metering
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "paid-mcp-metering": {
      "command": "node",
      "args": ["/path/to/paid-mcp-metering/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/dev55acc-ai/paid-mcp-metering and follow its README for install instructions.
Casos de uso

Resumen de MCP Servers

# paid-mcp-metering

Metered MCP tools, priced per call.

Discovery is free: `POST /mcp` speaks JSON-RPC 2.0 per the Model Context Protocol (`initialize`, `tools/list`, `ping`). Execution is metered: `POST /v1/t/{tool}` sits behind an x402 v2 paywall. An unpaid request gets HTTP `402` with payment requirements; a paid request carries a `PAYMENT-SIGNATURE` header and settles USDC through the facilitator before the tool runs.

## Live deployment

Base URL: `https://paid-mcp-metering.vercel.app`

- `GET /health` — free, public
- `POST /mcp` — free discovery
- `POST /v1/t/{tool}` — metered; currently answers `503 settlement_not_configured` because `X402_PAY_TO` is unset on the deployment (`settlementConfigured:false` in `/health` is the honest switch). No payment can be accepted until a receiving address is configured.

`server.json` declares this URL as the registry remote.

## Tools

| Tool | Price | What it returns |
|------|-------|-----------------|
| `web_search` | $0.001/call | Ranked live web results with source URLs |
| `deep_research` | $0.01/call | Multi-source research pass with a synthesized answer plus cited sources |

Upstreams are Exa (primary) and Tavily (fallback). Every handler returns live upstream output or throws — there is no canned response.

## Rails

x402 v2, USDC, EIP-155 network selected by `X402_NETWORK` (default Base Sepolia testnet, CAIP-2 `eip155:84532`). Facilitator defaults to `https://x402.org/facilitator`.

| Env var | Purpose |
|---------|---------|
| `X402_PAY_TO` | Receiving address. Required for settlement; unset serves 402 requirements only |
| `X402_NETWORK` | CAIP-2 network id (default `eip155:84532`) |
| `X402_FACILITATOR_URL` | x402 facilitator endpoint |
| `EXA_API_KEY` / `TAVILY_API_KEY` | Search upstream credentials |

## Run

```bash
npm install
npm run build
npm start          # node dist/x402-server.js
npm test           # build + node --test dist/test-x402.js
```

Free discovery:

```bash
curl -s localhost:4021/mcp -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

Paid execution:

```bash
curl -s localhost:4021/v1/t/web_search -H 'Content-Type: application/json' \
  -d '{"query":"x402 protocol","max_results":3}'
# -> 402 with payment requirements; pay via an x402 client and retry with PAYMENT-SIGNATURE
```

## Registry

`server.json` targets the official MCP Registry as `io.github.dev55acc-ai/paid-mcp-metering`. Tagging `v*` runs `.github/workflows/publish-mcp.yml`: tests, build, npm publish (when `NPM_TOKEN` is set), then registry publish authenticated by GitHub OIDC — no stored registry credential.

## License

MIT

Lo que la gente pregunta sobre paid-mcp-metering

¿Qué es dev55acc-ai/paid-mcp-metering?

+

dev55acc-ai/paid-mcp-metering es mcp servers para el ecosistema de Claude AI. Metered MCP tools. Free discovery over MCP; execution priced per call and settled in USDC via x402 v2. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-08-24.

¿Cómo se instala paid-mcp-metering?

+

Puedes instalar paid-mcp-metering clonando el repositorio (https://github.com/dev55acc-ai/paid-mcp-metering) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar dev55acc-ai/paid-mcp-metering?

+

Nuestro agente de seguridad ha analizado dev55acc-ai/paid-mcp-metering y le ha asignado un Trust Score de 87/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene dev55acc-ai/paid-mcp-metering?

+

dev55acc-ai/paid-mcp-metering es mantenido por dev55acc-ai. La última actividad registrada en GitHub es del 2026-08-24, con 0 issues abiertos.

¿Hay alternativas a paid-mcp-metering?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega paid-mcp-metering en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: dev55acc-ai/paid-mcp-metering
[![Featured on ClaudeWave](https://claudewave.com/api/badge/dev55acc-ai-paid-mcp-metering)](https://claudewave.com/repo/dev55acc-ai-paid-mcp-metering)
<a href="https://claudewave.com/repo/dev55acc-ai-paid-mcp-metering"><img src="https://claudewave.com/api/badge/dev55acc-ai-paid-mcp-metering" alt="Featured on ClaudeWave: dev55acc-ai/paid-mcp-metering" width="320" height="64" /></a>

Más MCP Servers

Alternativas a paid-mcp-metering