Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Inference MCP

by BSVKeyversion 1.3.6i★ –iComputer or cloud
Registry nameio.github.BSVKey/inference-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: BSVKEY_API_KEY, BSVKEY_WIF, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 6 things (tools) list_models, infer, channel_balance, open_channel …
  • You fill in yourself: BSVKEY_API_KEY, BSVKEY_BASE_URL, BSVKEY_WIF, BSVKEY_FUNDED_SATS, BSVKEY_RECEIPT_STATE, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
      }
    }
  }
}

Run this in your terminal

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

Or run it on your computer

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "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"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • BSVKEY_API_KEY secret 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 secret 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 secret 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…

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • list_models

    List the models this BSV inference gateway sells, with LIVE retail price (satoshis per 1,000 tokens) at the current BSV/USD rate. No key needed. Call first to choose a model.

  • infer

    Run one metered inference (OpenAI-compatible), paid per token in Bitcoin BSV from your prepaid channel. Returns the completion plus a receipt: satoshis charged, model routed to, remaining balance, and the broker-signed usage receipt. Needs a funded channel key: send the HTTP head

  • channel_balance

    Check a prepaid channel’s remaining Bitcoin BSV balance, spend, and request count. Uses the Authorization header or apiKey. On failure returns isError "error: ( ): ": no_channel_key, or invalid_channel (401/404: not found, bad secret, or closed).

  • open_channel

    Explains how to open + fund a prepaid channel. Funding is a real Bitcoin BSV payment signed by a wallet, so it is done once at the website; you then send the returned channel key as "Authorization: Bearer channelId:channelSecret" (or pass it as apiKey).

  • x402_infer

    Run one inference paid PER CALL in Bitcoin BSV via x402, no prepaid channel. Non-custodial, two steps: (1) call without payment to get the 402 quote (status payment_required, accepts[]); nothing is spent. (2) Build and sign a BSV payment for that quote in your own wallet (for exa

  • xrp_infer

    Run one inference paid PER CALL in XRP on the XRP Ledger via x402, no channel. Non-custodial, two steps: (1) call without payment to get the 402 quote (exact drops, destination, destination tag, signed quote; priced from the XRP Ledger's own XRP/RLUSD market); nothing is spent. (

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account BSVKey, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 175 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 6 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32568 servers in this category
  • Published to the registry more recently than 83% of the other 32568 servers in this category
  • Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Inference MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: BSVKEY_API_KEY, BSVKEY_WIF, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.6) reached the registry 7 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

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

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

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

Runs in the cloud★ 211Updated yesterday
Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@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.
Ask PopNx