SolidInvoice
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Let an AI agent pay in USDC on NEAR only inside owner-signed mandates, with a signed ledger.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Probarion. Follow https://mcp.popnx.com/i/probarion.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 15, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Probarion key (create it on the maker’s site) · 1 setting(s) to fill in (PROBARION_VAULT_ID) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Probarion for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Probarion tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
PROBARION_VAULT_ID The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnetDescriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"probarion": {
"command": "npx",
"args": [
"-y",
"@probarion/mcp"
],
"env": {
"PROBARION_VAULT_ID": "your-value",
"PROBARION_AGENT_KEY": "your-value",
"PROBARION_LEDGER_KEY": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Probarion and tell me what you can do for me, then show me one thing✓ If Claude says it is using Probarion or shows a Probarion tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NEAR_NETWORK 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 itPROBARION_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-onlyNEAR_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 networkNEAR_ARCHIVAL_RPC_URLS Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival nodePROBARION_LEDGER_PATH Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonlDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Probarion yet
Probarion runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Probarion
B · Others in Accounting, finance & tax that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Probarion key (create it on the maker’s site) · 1 setting(s) to fill in (PROBARION_VAULT_ID) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Probarion for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Probarion tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
PROBARION_VAULT_ID The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnetDescriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
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/mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Probarion listed as connected
Use Probarion and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Probarion or shows a Probarion tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NEAR_NETWORK 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 itPROBARION_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-onlyNEAR_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 networkNEAR_ARCHIVAL_RPC_URLS Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival nodePROBARION_LEDGER_PATH Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonlDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Probarion key (create it on the maker’s site) · 1 setting(s) to fill in (PROBARION_VAULT_ID) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Probarion for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Probarion tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
PROBARION_VAULT_ID The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnetDescriptions are as written by the maker.
In the Probarion settings, PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Probarion and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Probarion or shows a Probarion tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NEAR_NETWORK 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 itPROBARION_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-onlyNEAR_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 networkNEAR_ARCHIVAL_RPC_URLS Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival nodePROBARION_LEDGER_PATH Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonlDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Probarion key (create it on the maker’s site) · 1 setting(s) to fill in (PROBARION_VAULT_ID) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Probarion for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by 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) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Probarion tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
PROBARION_VAULT_ID The vault account, for example acme.vaults.probarion.testnet. A name ending in .near is on mainnet, one ending in .testnet on testnetDescriptions are as written by the maker.
In the Probarion settings, PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY, PROBARION_VAULT_ID is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Probarion and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Probarion or shows a Probarion tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
NEAR_NETWORK 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 itPROBARION_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-onlyNEAR_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 networkNEAR_ARCHIVAL_RPC_URLS Comma-separated archival RPC URLs that verify reads old transactions from, with the same rules as NEAR_RPC_URLS. Default: FastNEAR's archival nodePROBARION_LEDGER_PATH Absolute path of the ledger file: a relative one is taken from the folder the client starts the server in. Default ~/.probarion/ /ledger.jsonlDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
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/mcpClaude 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 required envNEAR_NETWORK envPROBARION_KEYS_FILE envPROBARION_AGENT_KEY secret required envPROBARION_LEDGER_KEY secret required envNEAR_RPC_URLS envNEAR_ARCHIVAL_RPC_URLS envPROBARION_LEDGER_PATH envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @probarion/mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 20, 2026
The registry name was verified with the GitHub account probarion, which owns the repo
Code last changed 3 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @probarion/mcp@0.1.2
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/probarion)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: PROBARION_AGENT_KEY, PROBARION_LEDGER_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 days ago, and the latest version (0.1.2) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: SolidInvoice, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP, Twelve Data
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
48 tools for ~8,000 NSE & BSE stocks: quotes, screener, financials, filings, FII/DII, options
Real-time and historical market data: stocks, forex, crypto, ETFs, fundamentals and 60+ indicators.
| This one Probarion | SolidInvoice | Journalit | Beancount.io | Tapetide - Indian Stock Market MCP | Twelve Data | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | Yes | No |
| Add with + in Claude | No | No | No | No | No | Yes |
| Basic checks | 3/3 | 4/6 | 4/4 | 4/4 | 5/5 | 4/4 |
| License | MIT | MIT | NOASSERTION | MIT | MIT | – |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
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.
| Tool | What it does | Sends a transaction |
|---|---|---|
list_mandates | The 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 own | No |
check_spend | Asks the vault contract (check_spend, a free view) whether it would pay this amount under this mandate | No |
request_spend | Pays 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_spend | Yes, spend with the agent key |
get_spend_status | Reads 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 again | No |
verify | Runs 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, code | No |
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.
The server holds two function-call keys of the vault and no owner key:
spend and nothing else, with no deposit.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.
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.
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.
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.
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.
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.
The server and status read these from their environment:
| Variable | Required | Meaning |
|---|---|---|
PROBARION_VAULT_ID | Yes | The vault account, e.g. acme.vaults.probarion.testnet |
NEAR_NETWORK | When the vault's name ends in neither .near nor .testnet | mainnet or testnet |
PROBARION_KEYS_FILE | No | The keys file init --keys-file wrote, as an absolute path. It must exist. Default ~/.probarion/ /keys.json, used when it exists |
PROBARION_AGENT_KEY | With PROBARION_LEDGER_KEY, or neither | ed25519:..., the vault's spend-only key, in place of a keys file (see the fallback below) |
PROBARION_LEDGER_KEY | With PROBARION_AGENT_KEY, or neither | ed25519:..., the vault's anchor-only key, in place of a keys file |
NEAR_RPC_URLS | No | Comma-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_URLS | No | The archival RPC URLs verify reads old transactions from, with the same rules |
PROBARION_LEDGER_PATH | No | The 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.
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:
tools/list: the five tools, and that no input field names a recipient.list_mandates: the mandate's payee, caps, uses and expiry, read live from the vault contract.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.request_spend with an injected "to" field, refused by the input schema before the tool runs.get_spend_status on a paid spend.verify on the vault's signed ledger, downloaded from its public proof page. When the d