Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Pay-per-token Claude & Grok inference, settled in Bitcoin BSV. npm package or hosted remote.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
BSVKEY_API_KEY, BSVKEY_BASE_URL, BSVKEY_WIF, BSVKEY_FUNDED_SATS, BSVKEY_RECEIPT_STATE, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http inference https://inference.bsvkey.com/mcp --header 'Authorization: your-value'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运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"inference": {
"url": "https://inference.bsvkey.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"inference": {
"type": "http",
"url": "https://inference.bsvkey.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
BSVKEY_BASE_URL envBSVKEY_FUNDED_SATS envBSVKEY_RECEIPT_STATE envAuthorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
list_modelsList 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.
inferRun 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_balanceCheck 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_channelExplains 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_inferRun 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_inferRun 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. (
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 BSVKey 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 175 毫秒内响应(HTTP 200)
无需登录
已读取 6 个工具描述,未发现针对 AI 的隐藏指令
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:BSVKEY_API_KEY, BSVKEY_WIF, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.3.6)于7天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AvaHR
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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:
receiptVerified is null (unknown), never true — a down pin weakens the check to *unknown*, not to *trusted*.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.BSVKEY_RECEIPT_STATE to a file path to persist per-channel seq/totals so replays are caught across restarts.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
channelId:channelSecret.BSVKEY_API_KEY.infer and pays per token.list_models and open_channel work with no key; infer and channel_balance need a funded channel key.
Published on npm as [@bsvkey/inference-mcp](https://www.npmjs.com/package/@bsvkey/inference-mcp).
claude mcp add bsvkey-inference \
--env BSVKEY_API_KEY=channelId:channelSecret \ -- npx -y @bsvkey/inference-mcp
{
"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"]`.
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).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.@bsvkey/x402-bsv-client. To sign payments and verify receipts locally from a key, use the npm package above.| Var | Default | Meaning |
|---|---|---|
BSVKEY_BASE_URL | https://inference.bsvkey.com/v1 | Gateway 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_SEED | none | An 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. |
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, ...]
| Code | Status | Tool | What it means | What to do |
|---|---|---|---|---|
no_channel_key | infer, channel_balance | No apiKey and no BSVKEY_API_KEY | Open a channel at the site (see open_channel) | |
invalid_channel | 401 / 404 | infer, channel_balance | Channel not found, wrong secret, or closed | Open a new channel |
insufficient_balance | 402 | infer | The channel can't cover the worst case for this call; extras give requiredSats and balanceSats | Top up at the site, or lower maxTokens / turn off webSearch |
invalid_request | 400 | infer, x402_infer | Unknown model or policy, a model whose provider isn't enabled, or bad input | Call list_models |
upstream_failed | 502 | infer | The model provider failed | Nothing is charged; retry or pick another model |
no_wif | x402_infer | No wif and no BSVKEY_WIF | Pass a funded key | |
verifier_missing | x402_infer | @bsvkey/x402-bsv-client / @bsv/sdk not installed | npm i @bsvkey/x402-bsv-client @bsv/sdk | |
payment_failed | 402 | x402_infer | The payment didn't settle (e.g. the key's address is unfunded); extras give the reason | Fund the address; nothing was spent |
upstream_failed | 502 | x402_infer | The payment settled but the provider then failed; extras give settlementTxid | No automatic refund: email embryospace@gmail.com with the txid |
no_xrp_seed | xrp_infer | No xrpSeed and no BSVKEY_XRP_SEED | Pass a funded XRP seed | |
xrpl_missing | xrp_infer | The xrpl package isn't installed | npm i xrpl | |
node_too_old | xrp_infer | Node is older than 20.19 / 22.12, which the xrpl package needs | Upgrade Node (the other tools run on Node 18+) | |
insufficient_xrp | xrp_infer | The wallet isn't activated, or can't cover the quote above its 1 XRP reserve | Fund it; nothing was spent | |
payment_failed | 402 | xrp_infer | The payment was refused before broadcast, or didn't settle; extras give the reason | Nothing was spent unless a settlement tx is included |
upstream_failed | 502 | xrp_infer | The payment settled but the provider then failed; extras give the settlement tx | No 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.
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
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.
@bsvkey org (owner: interence). First publish: v1.0.0.version in package.json, then npm publish --access public (2FA/security-key prompt applies).SKILL.md + this README.