Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Inference MCP

de BSVKeyversión 1.3.6i★ –iComputadora o nube
Nombre en el registroio.github.BSVKey/inference-mcp

Instalar

Resumen

Descripción del creador (original en inglés)

Pay-per-token Claude & Grok inference, settled in Bitcoin BSV. npm package or hosted remote.

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Computadora o nube
  • Transporte: stdio, Streamable HTTP
  • Categoría: Otros
  • Debes completar: BSVKEY_API_KEY, BSVKEY_WIF, Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
  • Debes completar tú: BSVKEY_API_KEY, BSVKEY_BASE_URL, BSVKEY_WIF, BSVKEY_FUNDED_SATS, BSVKEY_RECEIPT_STATE, Authorization

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

O ejecútalo en tu computadora

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "inference": {
      "command": "npx",
      "args": [
        "-y",
        "@bsvkey/inference-mcp"
      ],
      "env": {
        "BSVKEY_API_KEY": "your-value",
        "BSVKEY_BASE_URL": "your-value",
        "BSVKEY_WIF": "your-value",
        "BSVKEY_FUNDED_SATS": "your-value",
        "BSVKEY_RECEIPT_STATE": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add --transport http inference https://inference.bsvkey.com/mcp --header 'Authorization: your-value'

O ejecútalo en tu computadora

claude mcp add inference --env BSVKEY_API_KEY=your-value --env BSVKEY_BASE_URL=your-value --env BSVKEY_WIF=your-value --env BSVKEY_FUNDED_SATS=your-value --env BSVKEY_RECEIPT_STATE=your-value -- npx -y @bsvkey/inference-mcp

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "inference": {
      "url": "https://inference.bsvkey.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

O ejecútalo en tu computadora

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

{
  "mcpServers": {
    "inference": {
      "command": "npx",
      "args": [
        "-y",
        "@bsvkey/inference-mcp"
      ],
      "env": {
        "BSVKEY_API_KEY": "your-value",
        "BSVKEY_BASE_URL": "your-value",
        "BSVKEY_WIF": "your-value",
        "BSVKEY_FUNDED_SATS": "your-value",
        "BSVKEY_RECEIPT_STATE": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "inference": {
      "type": "http",
      "url": "https://inference.bsvkey.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

O ejecútalo en tu computadora

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

{
  "servers": {
    "inference": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@bsvkey/inference-mcp"
      ],
      "env": {
        "BSVKEY_API_KEY": "your-value",
        "BSVKEY_BASE_URL": "your-value",
        "BSVKEY_WIF": "your-value",
        "BSVKEY_FUNDED_SATS": "your-value",
        "BSVKEY_RECEIPT_STATE": "your-value"
      }
    }
  }
}

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • BSVKEY_API_KEY secreto env
    A funded channel key in the form channelId:channelSecret. Open + fund a channel once at https://inference.bsvkey.com. Optional (can be passed per call).
  • BSVKEY_BASE_URL env
    Gateway base URL. Defaults to https://inference.bsvkey.com/v1; override to point at a self-hosted deployment.
  • BSVKEY_WIF secreto env
    A funded BSV private key (WIF) used by the x402_infer tool to pay per call in BSV (no channel). Signing is local; the key never leaves the process. Optional (can be passed per call).
  • BSVKEY_FUNDED_SATS env
    The amount you funded your channel with on-chain. When set, usage receipts are verified against this instead of the broker-signed fundedSats. Optional (can be passed per call as fundedSats).
  • BSVKEY_RECEIPT_STATE env
    Path to a JSON file where per-channel receipt continuity (seq + running totals) is persisted, so replays are caught across restarts. Optional; in-memory only if unset.
  • Authorization secreto HTTP header
    Optional. "Bearer channelId:channelSecret" for a prepaid channel funded at https://inference.bsvkey.com. Needed only for infer and channel_balance; x402_infer and xrp_infer take a wallet-signed payme…

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub BSVKey, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    El endpoint responde

    Aún sin revisar; revisamos los endpoints por turnos

  • … Aún sin revisar

    Inicio de sesión con OAuth

    Aún sin revisar; revisamos los endpoints por turnos

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 32509 servidores de esta categoría
  • Publicado en el registro más recientemente que el 83% de los otros 32509 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 32509 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Inference MCP?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: BSVKEY_API_KEY, BSVKEY_WIF, Authorization

¿Se ejecuta en mi computadora o en la nube?

Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (1.3.6) llegó al registro hace 7 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Fomu MCP

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar

Remote Desktop Commander

de desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Se ejecuta en la nube★ 211Actualizado ayer
Instalar

Fomu MCP

de gabrielmahia

Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.

Se ejecuta en tu computadoraActualizado hoy
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

@bsvkey/inference-mcp

An MCP server that lets any agent buy Claude & Grok inference metered per token, settled in BSV, through the hosted gateway at inference.bsvkey.com. Zero dependencies (Node ≥ 18, uses global fetch). It's a thin HTTP client — it never holds your keys or runs models; every call is billed through the gateway.

Tools: list_models, infer, channel_balance, open_channel, x402_infer, xrp_infer.

Two ways to pay: a prepaid channel (infer, fund once, draw down per token) or per call via x402 (x402_infer — no channel; the agent pays each request in BSV with its own key). x402_infer needs a funded WIF (wif arg or BSVKEY_WIF) and the optional @bsvkey/x402-bsv-client + @bsv/sdk packages (installed with this one).

Pay per call in XRP with xrp_infer: the tool gets a quote in XRP (priced from the XRP Ledger's own XRP/RLUSD market), signs one XRP Payment for exactly that locally, and the gateway checks it before broadcasting, waits for validation (a few seconds), and returns the answer, the settlement tx, and a signed receipt. It needs a funded XRP seed (xrpSeed arg or BSVKEY_XRP_SEED; create one at xrp.bsvkey.com/wallet) and the optional xrpl package (installed with this one; it needs Node 20.19+ or 22.12+). The account keeps a 1 XRP reserve that can't be spent.

Verifiable metering. Each infer call returns a signed usage receipt, and the tool auto-verifies it offline (with the optional packages installed): the result includes receiptVerified and meterVerified (true, false + receiptCheck, or null). It recovers the broker key (pinned from GET /v1/receipt-key); binds the receipt to the channel you called (from your API key, not the receipt's self-report); checks a monotonic sequence (no replay/gap) and running totals within the funded amount; recomputes the charge from the published rate (you can never be overcharged); and recomputes the token count from the exact bytes of your messages and the completion, under the pinned bsvkey-meter/1 tokenizer. So the channel payment is on-chain and both the meter and the charge are auditable, without trusting the broker's word.

Four things an unattended client should know:

  • Fails closed. If the pinned-key endpoint is unreachable, receiptVerified is null (unknown), never true — a down pin weakens the check to *unknown*, not to *trusted*.
  • Supply your funded amount. Set BSVKEY_FUNDED_SATS (or pass fundedSats) to the amount you funded on-chain. The receipt's own fundedSats is the broker's assertion; when you supply yours, a receipt claiming a different amount is rejected and totals are checked against what you actually paid.
  • Persist across restarts. Sequence continuity is in-memory by default (a replay before the first receipt this process sees would be invisible). Set BSVKEY_RECEIPT_STATE to a file path to persist per-channel seq/totals so replays are caught across restarts.
  • The receipt is the ledger. The GET /v1/channels/:id balance endpoint can lag the signed receipt by ~20s; trust the receipt, treat the endpoint as a cache.

Spec: https://inference.bsvkey.com/usage-receipts.md

Quick start

  1. Fund a channel once at https://inference.bsvkey.com (BRC-100 wallet, or load a key in-page). Copy the key it returns: channelId:channelSecret.
  2. Add the MCP server to your agent host (below), with that key in BSVKEY_API_KEY.
  3. Ask your agent to run inference — it calls infer and pays per token.

list_models and open_channel work with no key; infer and channel_balance need a funded channel key.

Install

Published on npm as [@bsvkey/inference-mcp](https://www.npmjs.com/package/@bsvkey/inference-mcp).

Claude Code
claude mcp add bsvkey-inference \

--env BSVKEY_API_KEY=channelId:channelSecret \ -- npx -y @bsvkey/inference-mcp

Claude Desktop / Codex / any MCP host (JSON config)
{

"mcpServers": { "bsvkey-inference": { "command": "npx", "args": ["-y", "@bsvkey/inference-mcp"], "env": { "BSVKEY_API_KEY": "channelId:channelSecret" } } } }

No npm? Grab the single-file server directly (`https://inference.bsvkey.com/mcp/server.js`) and use `"command": "node", "args": ["server.js"]`.
Hosted (no install)

Any MCP host that supports remote servers can connect to `https://inference.bsvkey.com/mcp` (Streamable HTTP). Same six tools, nothing to install.

claude mcp add --transport http bsvkey-inference https://inference.bsvkey.com/mcp \

--header "Authorization: Bearer channelId:channelSecret"

{

"mcpServers": { "bsvkey-inference": { "type": "http", "url": "https://inference.bsvkey.com/mcp", "headers": { "Authorization": "Bearer channelId:channelSecret" } } } }

  • list_models and open_channel need no header.
  • infer and channel_balance use the prepaid channel key in the Authorization header (or apiKey per call).
  • The hosted server never takes a private key. x402_infer (Bitcoin BSV) and xrp_infer (XRP) are two steps there: call without payment to get the quote, sign it in your own wallet, then call again with payment (the base64 X-PAYMENT value). A wif or xrpSeed argument is refused.
  • The hosted server returns the signed usage receipt but does not verify it for you; verify it offline with @bsvkey/x402-bsv-client. To sign payments and verify receipts locally from a key, use the npm package above.

Configuration (env)

VarDefaultMeaning
BSVKEY_BASE_URLhttps://inference.bsvkey.com/v1Gateway base URL (set to a self-hosted deployment if you run your own).
BSVKEY_API_KEY—channelId:channelSecret for a funded channel. Optional; can also be passed per call as apiKey.
BSVKEY_FUNDED_SATS—The amount you funded your channel with on-chain. When set, receipts are verified against it instead of the broker-signed fundedSats. Optional; per-call fundedSats.
BSVKEY_XRP_SEEDnoneAn XRP wallet seed for xrp_infer. Optional; can also be passed per call as xrpSeed. Never leaves this process.
BSVKEY_RECEIPT_STATE—Path to a JSON file for persisting per-channel receipt continuity (seq + totals) across restarts. Optional; in-memory only if unset.

Errors

A failed tool call returns isError: true with text in one fixed shape, so an agent can branch on the code without parsing prose:

error: <code> (<http status>): <message> [extra=value, ...]
CodeStatusToolWhat it meansWhat to do
no_channel_keyinfer, channel_balanceNo apiKey and no BSVKEY_API_KEYOpen a channel at the site (see open_channel)
invalid_channel401 / 404infer, channel_balanceChannel not found, wrong secret, or closedOpen a new channel
insufficient_balance402inferThe channel can't cover the worst case for this call; extras give requiredSats and balanceSatsTop up at the site, or lower maxTokens / turn off webSearch
invalid_request400infer, x402_inferUnknown model or policy, a model whose provider isn't enabled, or bad inputCall list_models
upstream_failed502inferThe model provider failedNothing is charged; retry or pick another model
no_wifx402_inferNo wif and no BSVKEY_WIFPass a funded key
verifier_missingx402_infer@bsvkey/x402-bsv-client / @bsv/sdk not installednpm i @bsvkey/x402-bsv-client @bsv/sdk
payment_failed402x402_inferThe payment didn't settle (e.g. the key's address is unfunded); extras give the reasonFund the address; nothing was spent
upstream_failed502x402_inferThe payment settled but the provider then failed; extras give settlementTxidNo automatic refund: email embryospace@gmail.com with the txid
no_xrp_seedxrp_inferNo xrpSeed and no BSVKEY_XRP_SEEDPass a funded XRP seed
xrpl_missingxrp_inferThe xrpl package isn't installednpm i xrpl
node_too_oldxrp_inferNode is older than 20.19 / 22.12, which the xrpl package needsUpgrade Node (the other tools run on Node 18+)
insufficient_xrpxrp_inferThe wallet isn't activated, or can't cover the quote above its 1 XRP reserveFund it; nothing was spent
payment_failed402xrp_inferThe payment was refused before broadcast, or didn't settle; extras give the reasonNothing was spent unless a settlement tx is included
upstream_failed502xrp_inferThe payment settled but the provider then failed; extras give the settlement txNo automatic refund: email embryospace@gmail.com with the tx

On a prepaid channel nothing is charged on any error. A successful infer can still report receiptVerified: false (the signed receipt didn't check out; see receiptCheck) or null (couldn't check: verifier missing, or the receipt-key endpoint was down).

Thinking models (claude-sonnet-5, claude-opus-5, claude-opus-5-5, claude-fable-5-1) bill their hidden reasoning as output, and maxTokens is raised to at least 1024 for them.

Verify it's wired (no key needed)

printf '%s\n' \

'{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' \ '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \ '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_models","arguments":{}}}' \ | node server.js

Marketplace listing blurb

BSV Inference — Pay-per-token Claude & Grok, settled in BSV. Prepay a channel

once, then meter every token with no subscription, account, or card. OpenAI-

compatible, optional live web search, on-chain settlement. MCP + portable SKILL.md.

Publishing (operator)

  • Live on npm under the @bsvkey org (owner: interence). First publish: v1.0.0.
  • To ship an update: bump version in package.json, then npm publish --access public (2FA/security-key prompt applies).
  • Canonical source: https://github.com/BSVKey/inference-mcp
  • To list on a skills marketplace (e.g. bopen.ai), submit SKILL.md + this README.
Pregunta a PopNx