原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Probarion

✓ 品牌同名 GitHub · github.com/probarion

作者:probarion版本 0.1.2i★ 1 (整个仓库的星标)i在你的电脑上运行官方网站 ↗
注册名称io.github.probarion/probarion

安装方法

能做什么

Let an AI agent pay in USDC on NEAR only inside owner-signed mandates, with a signed ledger.

作者提供的原文

  • 连接方式 在你的电脑上运行
  • 账号或密钥 需要 PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY · 需填写 1 项设置(PROBARION_VAULT_ID)
  • 分类 会计、财务与税务

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 Probarion。按照 https://mcp.popnx.com/i/probarion.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月15日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

让 AI 帮你安装

把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Claude 安装 MCP server Probarion,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "probarion": { "command": "npx", "args": [ "-y", "@probarion/mcp" ], "env": { "PROBARION_VAULT_ID": "your-value", "PROBARION_AGENT_KEY": "your-value", "PROBARION_LEDGER_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Probarion 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 注册并创建 Probarion 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Probarion 网站 ↗

  3. 填写 1 项设置

    这些是程序设置,不是密钥,无需注册。按开发者的说明填写。

    • PROBARION_VAULT_ID vault 账户,例如 acme.vaults.probarion.testnet。以 .near 结尾的名称位于主网,以 .testnet 结尾的名称位于测试网。
      查看英文原文The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnet

    说明为自动翻译,变量名保持原样;不确定时请查看原文。

  4. 打开电脑版 Claude 应用的设置文件

    SettingsDeveloperEdit Config

  5. 粘贴这些设置并保存文件

    {
      "mcpServers": {
        "probarion": {
          "command": "npx",
          "args": [
            "-y",
            "@probarion/mcp"
          ],
          "env": {
            "PROBARION_VAULT_ID": "your-value",
            "PROBARION_AGENT_KEY": "your-value",
            "PROBARION_LEDGER_KEY": "your-value"
          }
        }
      }
    }

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  6. 退出 Claude 再重新打开

  7. 试一试

    用 Probarion 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Probarion,或回答中出现 Probarion 的工具名称,就表示连接成功

5 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • NEAR_NETWORK mainnet 或 testnet。仅当 vault ID 不以 .near 或 .testnet 结尾时才需要;若设置此项,vault ID 的结尾必须与之一致。
    查看英文原文mainnet or testnet. Needed only when the vault id ends in neither .near nor .testnet; when set, the vault id's ending must agree with it
  • PROBARION_KEYS_FILE Absolute path of the keys file that probarion-mcp init wrote, which must exist. Default ~/.probarion/ /keys.json, used when it exists. With no keys the server is read-only
  • NEAR_RPC_URLS Comma-separated https:// NEAR RPC URLs in failover order, with no user name or password (http:// only for a node on this machine). Default: the public RPCs @probarion/core lists for the network
  • NEAR_ARCHIVAL_RPC_URLS 以逗号分隔的归档 RPC URL,用于验证对旧交易的读取,规则与 NEAR_RPC_URLS 相同。默认值:FastNEAR 的归档节点。
    查看英文原文Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival node
  • PROBARION_LEDGER_PATH 账本文件的绝对路径:相对路径将以客户端启动服务器时所在的文件夹为基准。默认值为 /.probarion/ /ledger.jsonl
    查看英文原文Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonl

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Probarion

Probarion 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Probarion 的应用

  • 需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
  • 需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次)
  • 需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次)
  • 需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次)

B · 会计、财务与税务 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code,但需要先准备

需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Claude Code 安装 MCP server Probarion,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user probarion --env PROBARION_VAULT_ID=your-value --env PROBARION_AGENT_KEY=your-value --env PROBARION_LEDGER_KEY=your-value -- npx -y @probarion/mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Probarion 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 注册并创建 Probarion 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Probarion 网站 ↗

  3. 填写 1 项设置

    这些是程序设置,不是密钥,无需注册。按开发者的说明填写。

    • PROBARION_VAULT_ID vault 账户,例如 acme.vaults.probarion.testnet。以 .near 结尾的名称位于主网,以 .testnet 结尾的名称位于测试网。
      查看英文原文The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnet

    说明为自动翻译,变量名保持原样;不确定时请查看原文。

  4. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  5. 粘贴这条命令并按 Enter

    claude mcp add --scope user probarion --env PROBARION_VAULT_ID=your-value --env PROBARION_AGENT_KEY=your-value --env PROBARION_LEDGER_KEY=your-value -- npx -y @probarion/mcp

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  6. 在 Claude Code 中输入 /mcp

    应能看到 Probarion 在列表中并显示已连接

  7. 试一试

    用 Probarion 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Probarion,或回答中出现 Probarion 的工具名称,就表示连接成功

5 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • NEAR_NETWORK mainnet 或 testnet。仅当 vault ID 不以 .near 或 .testnet 结尾时才需要;若设置此项,vault ID 的结尾必须与之一致。
    查看英文原文mainnet or testnet. Needed only when the vault id ends in neither .near nor .testnet; when set, the vault id's ending must agree with it
  • PROBARION_KEYS_FILE Absolute path of the keys file that probarion-mcp init wrote, which must exist. Default ~/.probarion/ /keys.json, used when it exists. With no keys the server is read-only
  • NEAR_RPC_URLS Comma-separated https:// NEAR RPC URLs in failover order, with no user name or password (http:// only for a node on this machine). Default: the public RPCs @probarion/core lists for the network
  • NEAR_ARCHIVAL_RPC_URLS 以逗号分隔的归档 RPC URL,用于验证对旧交易的读取,规则与 NEAR_RPC_URLS 相同。默认值:FastNEAR 的归档节点。
    查看英文原文Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival node
  • PROBARION_LEDGER_PATH 账本文件的绝对路径:相对路径将以客户端启动服务器时所在的文件夹为基准。默认值为 /.probarion/ /ledger.jsonl
    查看英文原文Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonl

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor,但需要先准备

需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 Cursor 安装 MCP server Probarion,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "probarion": { "command": "npx", "args": [ "-y", "@probarion/mcp" ], "env": { "PROBARION_VAULT_ID": "your-value", "PROBARION_AGENT_KEY": "your-value", "PROBARION_LEDGER_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Probarion 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 注册并创建 Probarion 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Probarion 网站 ↗

  3. 填写 1 项设置

    这些是程序设置,不是密钥,无需注册。按开发者的说明填写。

    • PROBARION_VAULT_ID vault 账户,例如 acme.vaults.probarion.testnet。以 .near 结尾的名称位于主网,以 .testnet 结尾的名称位于测试网。
      查看英文原文The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnet

    说明为自动翻译,变量名保持原样;不确定时请查看原文。

  4. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  5. 填写你的密钥

    在 Probarion 的设置中,PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  6. 在 Cursor 中以 Agent 模式打开 AI 聊天

  7. 试一试

    用 Probarion 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Probarion,或回答中出现 Probarion 的工具名称,就表示连接成功

5 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • NEAR_NETWORK mainnet 或 testnet。仅当 vault ID 不以 .near 或 .testnet 结尾时才需要;若设置此项,vault ID 的结尾必须与之一致。
    查看英文原文mainnet or testnet. Needed only when the vault id ends in neither .near nor .testnet; when set, the vault id's ending must agree with it
  • PROBARION_KEYS_FILE Absolute path of the keys file that probarion-mcp init wrote, which must exist. Default ~/.probarion/ /keys.json, used when it exists. With no keys the server is read-only
  • NEAR_RPC_URLS Comma-separated https:// NEAR RPC URLs in failover order, with no user name or password (http:// only for a node on this machine). Default: the public RPCs @probarion/core lists for the network
  • NEAR_ARCHIVAL_RPC_URLS 以逗号分隔的归档 RPC URL,用于验证对旧交易的读取,规则与 NEAR_RPC_URLS 相同。默认值:FastNEAR 的归档节点。
    查看英文原文Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival node
  • PROBARION_LEDGER_PATH 账本文件的绝对路径:相对路径将以客户端启动服务器时所在的文件夹为基准。默认值为 /.probarion/ /ledger.jsonl
    查看英文原文Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonl

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code,但需要先准备

需要 Probarion 的密钥(在开发者网站创建) · 需要填写 1 项设置(PROBARION_VAULT_ID) · 需要先在电脑上安装 Node.js(只需一次)

让 AI 帮你安装

把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。

请在这台电脑上为 VS Code 安装 MCP server Probarion,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "probarion": { "type": "stdio", "command": "npx", "args": [ "-y", "@probarion/mcp" ], "env": { "PROBARION_VAULT_ID": "your-value", "PROBARION_AGENT_KEY": "your-value", "PROBARION_LEDGER_KEY": "your-value" } } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID 先保留 "your-value",请我自己把真实值粘贴到文件或应用的输入框里。不要让我在对话里输入密钥。5) 按约定执行,然后确认 Probarion 的工具真的出现了。

这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。

  1. 安装 Node.js(如果还没有)

    已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter

    node -v
    • 显示版本号(例如 v26.13.1)= 已安装,可跳过这一步
    • 显示 "command not found"(Windows 显示 "is not recognized")= 还没安装,或刚装好但需要关掉终端再重新打开
    怎么打开终端

    Mac:按 ⌘ + Space,输入 Terminal 后按 Enter

    Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”

    还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令

    打开 Node.js 下载页 ↗

    装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v

    安装一次,所有需要 Node.js 的工具都能用

  2. 注册并创建 Probarion 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Probarion 网站 ↗

  3. 填写 1 项设置

    这些是程序设置,不是密钥,无需注册。按开发者的说明填写。

    • PROBARION_VAULT_ID vault 账户,例如 acme.vaults.probarion.testnet。以 .near 结尾的名称位于主网,以 .testnet 结尾的名称位于测试网。
      查看英文原文The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnet

    说明为自动翻译,变量名保持原样;不确定时请查看原文。

  4. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  5. 填写你的密钥

    在 Probarion 的设置中,PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  6. 在 VS Code 中以 Agent 模式打开 AI 聊天

  7. 试一试

    用 Probarion 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Probarion,或回答中出现 Probarion 的工具名称,就表示连接成功

5 项可选设置(不填也能用)

上面的命令不填这些也能用。想调整时再按开发者的说明添加。

  • NEAR_NETWORK mainnet 或 testnet。仅当 vault ID 不以 .near 或 .testnet 结尾时才需要;若设置此项,vault ID 的结尾必须与之一致。
    查看英文原文mainnet or testnet. Needed only when the vault id ends in neither .near nor .testnet; when set, the vault id's ending must agree with it
  • PROBARION_KEYS_FILE Absolute path of the keys file that probarion-mcp init wrote, which must exist. Default ~/.probarion/ /keys.json, used when it exists. With no keys the server is read-only
  • NEAR_RPC_URLS Comma-separated https:// NEAR RPC URLs in failover order, with no user name or password (http:// only for a node on this machine). Default: the public RPCs @probarion/core lists for the network
  • NEAR_ARCHIVAL_RPC_URLS 以逗号分隔的归档 RPC URL,用于验证对旧交易的读取,规则与 NEAR_RPC_URLS 相同。默认值:FastNEAR 的归档节点。
    查看英文原文Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival node
  • PROBARION_LEDGER_PATH 账本文件的绝对路径:相对路径将以客户端启动服务器时所在的文件夹为基准。默认值为 /.probarion/ /ledger.jsonl
    查看英文原文Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonl

说明为自动翻译,变量名保持原样;不确定时请查看原文。

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Probarion 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

安装在电脑上

Claude Code

claude mcp add --scope user probarion --env PROBARION_VAULT_ID=your-value --env PROBARION_AGENT_KEY=your-value --env PROBARION_LEDGER_KEY=your-value -- npx -y @probarion/mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "probarion": {
      "command": "npx",
      "args": [
        "-y",
        "@probarion/mcp"
      ],
      "env": {
        "PROBARION_VAULT_ID": "your-value",
        "PROBARION_AGENT_KEY": "your-value",
        "PROBARION_LEDGER_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "probarion": {
      "command": "npx",
      "args": [
        "-y",
        "@probarion/mcp"
      ],
      "env": {
        "PROBARION_VAULT_ID": "your-value",
        "PROBARION_AGENT_KEY": "your-value",
        "PROBARION_LEDGER_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "probarion": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@probarion/mcp"
      ],
      "env": {
        "PROBARION_VAULT_ID": "your-value",
        "PROBARION_AGENT_KEY": "your-value",
        "PROBARION_LEDGER_KEY": "your-value"
      }
    }
  }
}

需要你填写的值

  • PROBARION_VAULT_ID 必填 env
    vault 账户,例如 acme.vaults.probarion.testnet。以 .near 结尾的名称位于主网,以 .testnet 结尾的名称位于测试网。
    查看英文原文The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnet
  • NEAR_NETWORK env
    mainnet 或 testnet。仅当 vault ID 不以 .near 或 .testnet 结尾时才需要;若设置此项,vault ID 的结尾必须与之一致。
    查看英文原文mainnet or testnet. Needed only when the vault id ends in neither .near nor .testnet; when set, the vault id's ending must agree with it
  • PROBARION_KEYS_FILE env
    Absolute path of the keys file that probarion-mcp init wrote, which must exist. Default ~/.probarion/ /keys.json, used when it exists. With no keys the server is read-only
  • PROBARION_AGENT_KEY 机密 必填 env
    代理密钥的机密部分(ed25519:...),即保险库中只能调用 spend 的密钥,可代替密钥文件使用。使用 PROBARION_LEDGER_KEY 设置,或两者都不设置
    查看英文原文The agent key's secret (ed25519:...), the vault's key that can only call spend, in place of a keys file. Set it with PROBARION_LEDGER_KEY, or neither
  • PROBARION_LEDGER_KEY 机密 必填 env
    ledger 密钥的私密部分(ed25519:...),即 vault 中只能调用 anchor 的密钥,可代替密钥文件使用。通过 PROBARION_AGENT_KEY 设置,或两者都不设置
    查看英文原文The ledger key's secret (ed25519:...), the vault's key that can only call anchor, in place of a keys file. Set it with PROBARION_AGENT_KEY, or neither
  • NEAR_RPC_URLS env
    Comma-separated https:// NEAR RPC URLs in failover order, with no user name or password (http:// only for a node on this machine). Default: the public RPCs @probarion/core lists for the network
  • NEAR_ARCHIVAL_RPC_URLS env
    以逗号分隔的归档 RPC URL,用于验证对旧交易的读取,规则与 NEAR_RPC_URLS 相同。默认值:FastNEAR 的归档节点。
    查看英文原文Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival node
  • PROBARION_LEDGER_PATH env
    账本文件的绝对路径:相对路径将以客户端启动服务器时所在的文件夹为基准。默认值为 /.probarion/ /ledger.jsonl
    查看英文原文Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonl

说明为自动翻译,变量名保持原样;不确定时请查看原文。

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

一览

GitHub 星标i
1 (整个仓库的星标)
该仓库包含多个 MCP 条目,星标在排名中只计算一次
每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.1.2
发布到注册中心i
2026年11月15日
代码最后更新i
2026年11月17日
作者
probarion
软件包
npm: @probarion/mcp
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 probarion 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于3天前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

OSV.dev 中没有 @probarion/mcp@0.1.2 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/probarion.svg)](https://mcp.popnx.com/en/servers/probarion)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“会计、财务与税务”中的其他服务器比较i

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

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

常见问题

Probarion 安全吗?

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

它需要哪些密钥或代码?

你需要填写:PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY

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

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

它还在维护吗?

GitHub 仓库最后更新于3天前,最新版本(0.1.2)于5天前进入注册中心。

哪些应用可以使用它?

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

有什么可以替代它?

同一分类中有:SolidInvoice, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP, Twelve Data

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

作者:SolidInvoice正在增长★ 99011天前更新

在云端运行✓ 服务方 · solidinvoice.co

Journalit

Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.

作者:Cursivez正在增长★ 26512天前更新

在云端运行✓ 服务方 · journalit.co

Beancount.io

Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.

作者:bex-co正在增长★ 707 整个仓库的星标上个月更新

在云端运行✓ 服务方 · beancount.io

Twelve Data

Real-time and historical market data: stocks, forex, crypto, ETFs, fundamentals and 60+ indicators.

作者:twelvedata正在增长★ 8716天前更新

在云端运行✓ 服务方 · twelvedata.com
与相似项目对比
本项
Probarion
SolidInvoiceJournalitBeancount.ioTapetide - Indian Stock Market MCPTwelve Data
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装
需要密钥是否否否是否
可在 Claude 中按 + 添加否否否否否是
基础检查3/34/64/44/45/54/4
许可证MITMITNOASSERTIONMITMIT–
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

@probarion/mcp

An MCP server that gives an AI agent a Probarion vault to pay from. The agent can see its mandates, dry-run a payment, pay under a mandate and read a payment's status. It can pay only the payee of a mandate the owner signed for its key: no tool takes an address, and the vault contract pays the mandate's payee.

Unaudited beta. Testnet first; use small amounts. MIT licensed.

On npm since release 0.1.1, published on 2026-11-11. npx -y @probarion/mcp@0.1.2 runs it with no clone, and the official MCP registry lists it as io.github.probarion/probarion. A clone of the repository builds the same server, as Set it up below shows, and the lines below give both forms: from npm and from a clone.

The five tools

ToolWhat it doesSends a transaction
list_mandatesThe vault's mandates: payee, cap per payment, total cap and what is left, uses left, approval threshold, expiry and the agent key each is bound to, beside this server's ownNo
check_spendAsks the vault contract (check_spend, a free view) whether it would pay this amount under this mandateNo
request_spendPays under a mandate: Probarion's rules (decide() in @probarion/core) decide, the contract's spend checks again and pays the mandate's payee, and the decision goes into the vault's signed ledger. A second request with the same ref pays nothing: it is refused, and names the vault's spend under that ref as earlier_spendYes, spend with the agent key
get_spend_statusReads a spend by id: held, pending, paid, burned, failed, rejected or expired. burned is final for the vault: Probarion does not watch the release on the other chain yet (on testnet nothing leaves NEAR), so do not poll a burned spend or send it againNo
verifyRuns Probarion's verifier on the vault and the ledger file at PROBARION_LEDGER_PATH: ledger signatures, hash links, anchors, a decision behind every spend, keys, codeNo

Amounts go in as USDC decimal strings ("0.01", "25.50"). Every input rejects fields it does not know, so a prompt-injected "to": "0xBAD" is refused before anything runs. No tool creates, changes or removes a mandate, a key or the vault's settings: those are the owner's, signed in the owner's wallet.

When a client connects, the server also gives it instructions for the model (the MCP instructions field; each client decides whether its model sees them), under 1,200 characters. Where a tool description or an answer's note already states a rule, the instructions use the same sentence, and a few words of their own orient the model: only the payee of an active mandate bound to this server's key can be paid; check_spend first when unsure, since it sends no transaction; each ref and each invoice hash pays at most once; a held spend is polled with get_spend_status until it leaves held or its held_until passes (the contract approves no hold after that), not sent again; an unconfirmed spend may have paid, so it is not sent again under a new ref; a refusal is final for that request; and burned is final for the vault, in the words for the server's network. A server with no keys adds that request_spend is off.

What the agent's keys can do

The server holds two function-call keys of the vault and no owner key:

  • The agent key can call spend and nothing else, with no deposit.
  • The ledger key can call anchor and nothing else. It also signs each ledger entry.

Both stay on the machine that runs the server, in a keys file that probarion-mcp init writes. With no keys the server runs read-only: request_spend is off, the other four tools work. verify then needs PROBARION_LEDGER_PATH set to a copy of the vault's ledger; on an empty ledger, the checks that read it fail, and the answer says so.

Set it up

Node 24 or newer. Run it from npm with npx -y @probarion/mcp@0.1.2, or build it from a clone of the repository:

git clone https://github.com/probarion/probarion.git

cd probarion pnpm install --frozen-lockfile pnpm --filter "@probarion/mcp..." run build

The last line builds the server and the two packages it needs, @probarion/core and @probarion/sdk. The server is then node packages/mcp/dist/bin.js in that folder; the steps below write probarion-mcp for it. From npm, npx -y @probarion/mcp@0.1.2 runs the same commands with no clone. init and status print their own commands the way you started them, so from a clone the commands they print begin with node and the full path of bin.js.

Testnet first. Mainnet works the same way: the vault's name says its network (.near is mainnet, .testnet is testnet). The console does not serve mainnet yet, so on mainnet init and status give the probarion CLI's owner transactions and no console link.

1. Make the keys on your machine
node packages/mcp/dist/bin.js init --vault acme.vaults.probarion.testnet

init makes the agent key and the ledger key and writes both to ~/.probarion/ /keys.json, a file only you can read (mode 0600; on Windows the file gets its folder's permissions, and init warns about that, and about a file inside a git repository). It prints only the two public keys, the file's path and the next steps. Run it again and it changes nothing: it checks the file and prints the same public keys. --keys-file puts the file somewhere else.

Back up that folder: ledger.jsonl there is the only copy of the agent's signed record once the server writes it. The folder also holds keys.json, so the backup holds the two secret keys: keep it as private as the file itself, and out of any shared or synced folder in the clear. A backup restored from a zip or a cloud folder may come back readable by others; status fails a keys file that other users can read (outside Windows) and names the chmod 600 that fixes it. The ledger file is the part that cannot be made again: new keys can, and the owner then adds them.

Mode 0600 keeps out other users, not your own programs. An agent host that runs shell commands as you can read keys.json, and with both keys it can sign its own allowing decisions and spends without the server's decide(). The money still goes only to a mandate's payee, within its caps, but the ledger then records decisions the code did not make, and verify cannot tell. When the agent host has a shell tool, run the server as another OS user, or in a container the agent cannot read. The same holds for keys given in PROBARION_AGENT_KEY and PROBARION_LEDGER_KEY: keep them out of a client config the agent can read.

2. The owner adds the two public keys to the vault

The vault's owner signs two transactions, add_agent and set_ledger_key, which the CLI printers of the probarion CLI print:

probarion agent add --vault acme.vaults.probarion.testnet --pk <agent public key>

probarion ledger set-key --vault acme.vaults.probarion.testnet --pk

Each command prints the transaction for the owner's wallet to sign; init prints both with the keys filled in. On testnet the owner can paste the two public keys on the console's Agent (MCP) tab instead (https://probarion.xyz/console/ /agent), which init and status link to; the console does not serve mainnet yet. The owner also signs a mandate for the agent key (the console's Mandates tab, or probarion mandate create) and puts USDC in the vault.

3. Check that the vault is ready
PROBARION_VAULT_ID=acme.vaults.probarion.testnet node packages/mcp/dist/bin.js status

In PowerShell, set the variable first: $env:PROBARION_VAULT_ID = "acme.vaults.probarion.testnet". status reads the same settings as the server and prints one line per check, each ok, not yet or fail: the keys were found, in a keys file only you can read; the agent key is one of the vault's agent keys, a function-call key limited to spend with allowance left; the vault's ledger key is this ledger key, limited to anchor; the vault is not frozen; an active mandate is bound to the agent key; the vault's USDC; and the local ledger file against the vault's latest anchor (the server's single-writer check, run dry: the anchored entries are this file's, and this server's ledger key signed every entry after them). When the vault is not ready it ends with one next step: the first fail that has one, else the first not yet. It only reads: nothing is signed or sent. Exit code 0 when ready, 1 when not, 2 for a configuration error.

4. Give the MCP client the vault id

The client's config carries only PROBARION_VAULT_ID, and PROBARION_KEYS_FILE when the keys file is not in its default place. The server finds the keys in the keys file. The client lines are below.

Settings

The server and status read these from their environment:

VariableRequiredMeaning
PROBARION_VAULT_IDYesThe vault account, e.g. acme.vaults.probarion.testnet
NEAR_NETWORKWhen the vault's name ends in neither .near nor .testnetmainnet or testnet
PROBARION_KEYS_FILENoThe keys file init --keys-file wrote, as an absolute path. It must exist. Default ~/.probarion/ /keys.json, used when it exists
PROBARION_AGENT_KEYWith PROBARION_LEDGER_KEY, or neithered25519:..., the vault's spend-only key, in place of a keys file (see the fallback below)
PROBARION_LEDGER_KEYWith PROBARION_AGENT_KEY, or neithered25519:..., the vault's anchor-only key, in place of a keys file
NEAR_RPC_URLSNoComma-separated https:// RPC URLs in failover order, with no user name or password in a URL (http:// only for a node on this machine)
NEAR_ARCHIVAL_RPC_URLSNoThe archival RPC URLs verify reads old transactions from, with the same rules
PROBARION_LEDGER_PATHNoThe ledger file, as an absolute path: a relative one is taken from the folder the MCP client starts the server in. Default ~/.probarion/ /ledger.jsonl

The keys come from the first of these that is set: both PROBARION_AGENT_KEY and PROBARION_LEDGER_KEY; the file PROBARION_KEYS_FILE names; ~/.probarion/ /keys.json. With none, the server is read-only. One key from the environment and the other from a file is refused. A keys file must be for this vault and its network, and each secret key in it must match the public key beside it; a problem is named by the file and the field, with no value from the file. The server's first line on stderr says where its keys came from, and no key.

node packages/mcp/dist/bin.js --help lists the commands and --version prints the version. With no argument, the binary is the MCP server and writes only JSON-RPC to stdout.

Try it: the read-only demo

One command, with no key and no wallet, run in the clone's folder once it is built:

node packages/mcp/dist/bin.js demo

From npm, with no clone: npx -y @probarion/mcp@0.1.2 demo.

The demo starts the MCP server over stdio with no key in its environment, against the public testnet vault demo.vaults.probarion.testnet (--vault picks another testnet vault). Each step prints what it expects and what came back:

  1. tools/list: the five tools, and that no input field names a recipient.
  2. list_mandates: the mandate's payee, caps, uses and expiry, read live from the vault contract.
  3. check_spend, the contract's free dry run, at three amounts taken from those caps: one it pays, one it holds for an approver, and one over the per-payment cap that it refuses with OverPerPayment.
  4. request_spend with an injected "to" field, refused by the input schema before the tool runs.
  5. get_spend_status on a paid spend.
  6. verify on the vault's signed ledger, downloaded from its public proof page. When the d

只显示了开头部分;其余内容请在仓库中阅读