Paywall MCP

Name: Paywall MCP
Author: llmops-pro

作者：llmops-pro版本 0.1.2i★ –i在你的电脑上运行

注册名称io.github.llmops-pro/paywall-mcp

安装

概览

作者提供的说明（英文原文）

Lightning-paywall sidecar: wraps any stdio MCP server, requires paid invoices before tool calls.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：PAYWALL_UPSTREAM_COMMAND, NWC_CONNECTION_STRING

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PAYWALL_UPSTREAM_COMMAND, PAYWALL_UPSTREAM_ARGS, NWC_CONNECTION_STRING, PAYWALL_DEFAULT_PRICE_SATS, PAYWALL_PRICE_MAP

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "paywall": {
      "command": "npx",
      "args": [
        "-y",
        "paywall-mcp"
      ],
      "env": {
        "PAYWALL_UPSTREAM_COMMAND": "your-value",
        "PAYWALL_UPSTREAM_ARGS": "your-value",
        "NWC_CONNECTION_STRING": "your-value",
        "PAYWALL_DEFAULT_PRICE_SATS": "your-value",
        "PAYWALL_PRICE_MAP": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add paywall --env PAYWALL_UPSTREAM_COMMAND=your-value --env PAYWALL_UPSTREAM_ARGS=your-value --env NWC_CONNECTION_STRING=your-value --env PAYWALL_DEFAULT_PRICE_SATS=your-value --env PAYWALL_PRICE_MAP=your-value -- npx -y paywall-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "paywall": {
      "command": "npx",
      "args": [
        "-y",
        "paywall-mcp"
      ],
      "env": {
        "PAYWALL_UPSTREAM_COMMAND": "your-value",
        "PAYWALL_UPSTREAM_ARGS": "your-value",
        "NWC_CONNECTION_STRING": "your-value",
        "PAYWALL_DEFAULT_PRICE_SATS": "your-value",
        "PAYWALL_PRICE_MAP": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "paywall": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "paywall-mcp"
      ],
      "env": {
        "PAYWALL_UPSTREAM_COMMAND": "your-value",
        "PAYWALL_UPSTREAM_ARGS": "your-value",
        "NWC_CONNECTION_STRING": "your-value",
        "PAYWALL_DEFAULT_PRICE_SATS": "your-value",
        "PAYWALL_PRICE_MAP": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PAYWALL_UPSTREAM_COMMAND 必填 env
Command to spawn the upstream MCP server (e.g. npx)
PAYWALL_UPSTREAM_ARGS env
JSON array of args for the upstream command
NWC_CONNECTION_STRING 机密必填 env
NWC connection string of the receiving wallet (receive-only recommended)
PAYWALL_DEFAULT_PRICE_SATS env
Default price in sats for tools not in PAYWALL_PRICE_MAP
PAYWALL_PRICE_MAP env
JSON map of tool name to price in sats

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 llmops-pro 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32683 个服务器的 0%
发布到注册中心的时间比此分类中其他 32683 个服务器的 12% 更新
基础检查结果等于或优于此分类中其他 32683 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Paywall MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：PAYWALL_UPSTREAM_COMMAND, NWC_CONNECTION_STRING

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.2）于5个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211前天更新

安装

MCP Server Autocad Lisp Helper

作者：radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

paywall-mcp

Paywall ANY stdio MCP server with Lightning, without modifying it. paywall-mcp is a generic sidecar: configure it with an upstream MCP server command and a per-tool price map, and it transparently:

Forwards tools/list from the upstream to the LLM client, with prices appended to each tool's description.
Intercepts tools/call: free tools pass through; priced tools require a paid Lightning invoice (via Nostr Wallet Connect / NIP-47) before the call is forwarded.

No code changes to the upstream server. Works with Anthropic's reference MCP servers, your own, or any third-party MCP server that speaks stdio.

v0.1 — proxy + payment gate complete. Spawns a stdio upstream as a child process; per-tool pricing via env; in-memory invoice cache + replay protection; audit log; read-only mode. Persistent cache + HTTP/SSE upstream transport deferred to v0.2.

Why this exists

Modern paid-API patterns (Lightning paywall, L402, micropayments) exist for HTTP but the MCP ecosystem has no standard for paid tool calls. Building it into each individual server is repetitive and error-prone. paywall-mcp is the missing sidecar: write your tools as a normal MCP server, then wrap it with paywall-mcp to charge sats per call.

How the dual-call pattern works

For any priced tool:

First call — LLM calls priced_tool({...args}) *without* payment_hash. paywall-mcp issues a bolt11 invoice through your NWC wallet and returns:

"error": "payment_required", "invoice": "lnbc...", "payment_hash": "abc123...", "amount_sats": 21, "expires_in_seconds": 600, "next_step": "Pay this bolt11 ..." }

2. **Payment** — the LLM (or its operator) pays the invoice. Easiest path: use [`nwc-mcp`](https://npmjs.com/package/nwc-mcp) — the same LLM can call `nwc_pay_invoice` to settle.

Second call — LLM calls priced_tool({...args, payment_hash: "abc123..."}). paywall-mcp verifies settlement via NWC lookup_invoice, strips payment_hash from the args, forwards the original call to the upstream, returns the upstream's result.

Replay protection: the same payment_hash cannot be redeemed twice. Buyers pay a fresh invoice for each call.

What you can build with it

Charge sats for premium tools in an MCP server you already have, by adding one wrapper process.
Per-tool pricing tiers — free_lookup: 0, premium_analysis: 100, rare_alpha_signal: 5000. Buyers see prices in tool descriptions.
Bundle-and-resell third-party MCP servers — wrap someone else's open-source MCP server with your paywall and offer it as a managed paid service.
A/B test pricing — adjust PAYWALL_PRICE_MAP in env, restart, you're at the new price.
Time-limited promotional pricing — start at 21 sats, raise to 100 sats once usage proves the value.

Requirements

Node 20+
An existing stdio MCP server to wrap (paywall-mcp doesn't host tools itself; it gates an upstream's tools).
A NIP-47 NWC connection string for the seller's receive wallet. make_invoice + lookup_invoice are the only permissions paywall-mcp needs. A receive-only NWC connection is perfectly fine and recommended — paywall-mcp never spends.

Install

# From npm

npx -y paywall-mcp

From source

git clone cd paywall-mcp corepack enable pnpm pnpm install pnpm build

Configure

cp .env.example .env

edit .env: set PAYWALL_UPSTREAM_COMMAND/ARGS, NWC_CONNECTION_STRING, prices

The server auto-loads .env from its own directory (next to dist/) — deliberately NOT from cwd, to avoid env collisions when running multiple MCP servers in the same Claude Code session.

Required

Var	Purpose
`PAYWALL_UPSTREAM_COMMAND`	Executable to spawn as the upstream MCP server (e.g., `node`).
`PAYWALL_UPSTREAM_ARGS`	JSON array of args passed to the upstream command (e.g., `["/path/to/upstream/dist/index.js"]`).

Required when any tool has a non-zero price

Var	Purpose
`NWC_CONNECTION_STRING`	NIP-47 NWC URI for the seller's RECEIVE wallet. `make_invoice` + `lookup_invoice` permissions sufficient. paywall-mcp never spends.

Pricing

Var	Default	Purpose
`PAYWALL_DEFAULT_PRICE_SATS`	`0`	Default price for any tool not in the price map. `0` = free passthrough.
`PAYWALL_PRICE_MAP`	`{}`	JSON object mapping tool names to sat prices. Per-tool 0 = free; missing = use default. Example: `{"premium_compliment":21,"rare_alpha_signal":5000}`.

Optional

Var	Default	Purpose
`PAYWALL_UPSTREAM_CWD`	(parent cwd)	Working directory for the upstream child process.
`PAYWALL_UPSTREAM_ENV`	(inherits)	JSON object of env-var overrides for the upstream.
`PAYWALL_READ_ONLY`	`false`	Disables all paid tool calls (`tools/list` still works). Useful for maintenance.
`PAYWALL_INVOICE_TTL_SECONDS`	`600`	Invoice TTL. Past this, `payment_hash` is forgotten from cache and the buyer must re-issue.
`PAYWALL_PRICE_LABEL_TEMPLATE`	`"(💰 {price} sats)"`	Label appended to each priced tool's description in `tools/list`. `{price}` is substituted with the sat amount.
`PAYWALL_LOG_PATH`	`./paywall-mcp.log`	Server log.
`PAYWALL_AUDIT_PATH`	`./paywall-mcp-audit.log`	NDJSON audit log (one line per call).

End-to-end example: paywall the bundled `paywall-mcp-test` server

The companion paywall-mcp-test package exposes a single tool — premium_compliment. It already implements its own paywall pattern internally, but it's also a convenient stand-in for "any upstream MCP server" to demonstrate paywall-mcp itself.

.env:

PAYWALL_UPSTREAM_COMMAND=node

PAYWALL_UPSTREAM_ARGS=["/abs/path/to/paywall-mcp-test/dist/index.js"]

NWC_CONNECTION_STRING=nostr+walletconnect://...

PAYWALL_DEFAULT_PRICE_SATS=21 PAYWALL_PRICE_MAP={"premium_compliment":21}

Wire paywall-mcp (not the upstream directly) into your MCP client:

"mcpServers": { "paywall": { "command": "npx", "args": ["-y", "paywall-mcp"], "env": {} } } }

Now from your agent:

1. tools/list  → premium_compliment ... (💰 21 sats) This tool requires ...

premium_compliment({}) → returns invoice + payment_hash
nwc_pay_invoice(invoice) → buyer pays
premium_compliment({ payment_hash: "..." }) → upstream's result returned

Safety model

tools/list      → upstream.listTools() → augment descriptions with prices → return

tools/call: if price == 0 → upstream.callTool(args) (passthrough) elif PAYWALL_READ_ONLY → refuse with paywall_read_only (block) elif no payment_hash → gate.issue() → return bolt11 + hash (issue) elif bad hash format → refuse with invalid_payment_hash (block) else (have hash): gate.verify() ──┬─ unknown_payment_hash → block ├─ payment_hash_already_redeemed → block (replay) ├─ payment_hash_tool_mismatch → block ├─ payment_not_settled → block └─ ok → strip hash → upstream.callTool() (paid passthrough)

Audit log entries (NDJSON, one per request):

`outcome: "ok"` — invoice issued, free passthrough, or paid passthrough completed
`outcome: "blocked"` — read-only refusal, invalid hash, replay, mismatch, not-settled
`outcome: "error"` — upstream call failed, NWC lookup_invoice failed, etc.

Tail the audit log for ground truth — independent of whatever the LLM tells you.

tail -f paywall-mcp-audit.log | jq .

Wire into Claude Desktop / Claude Code / Cursor