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

Tabularium

by SQLazyversion 0.5.5i★ –iComputer or cloud
Registry nameio.github.SQLazy/tabularium

Install

Overview

Description from the maker (original English)

Agent memory and a signed spending ledger: pay any x402 API, keep a provable receipt.

PopNx MCP’s three pillars

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

What you can do with it

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

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Accounting, finance & tax
  • You need to fill in: TABULARIUM_PRIVATE_KEY

Install

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

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: TABULARIUM_PRIVATE_KEY, TABULARIUM_MAX_SPEND_USD, TABULARIUM_URL, TABULARIUM_PAY_MAX_USD, TABULARIUM_PAY_NETWORKS, TABULARIUM_PUBKEY

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

You need

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

Which app do you use?

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

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://tabularium.matt-3e0.workers.dev/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "tabularium": {
      "command": "npx",
      "args": [
        "-y",
        "tabularium-mcp"
      ],
      "env": {
        "TABULARIUM_PRIVATE_KEY": "your-value",
        "TABULARIUM_MAX_SPEND_USD": "your-value",
        "TABULARIUM_URL": "your-value",
        "TABULARIUM_PAY_MAX_USD": "your-value",
        "TABULARIUM_PAY_NETWORKS": "your-value",
        "TABULARIUM_PUBKEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http tabularium https://tabularium.matt-3e0.workers.dev/mcp

Or run it on your computer

claude mcp add tabularium --env TABULARIUM_PRIVATE_KEY=your-value --env TABULARIUM_MAX_SPEND_USD=your-value --env TABULARIUM_URL=your-value --env TABULARIUM_PAY_MAX_USD=your-value --env TABULARIUM_PAY_NETWORKS=your-value --env TABULARIUM_PUBKEY=your-value -- npx -y tabularium-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "tabularium": {
      "url": "https://tabularium.matt-3e0.workers.dev/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "tabularium": {
      "command": "npx",
      "args": [
        "-y",
        "tabularium-mcp"
      ],
      "env": {
        "TABULARIUM_PRIVATE_KEY": "your-value",
        "TABULARIUM_MAX_SPEND_USD": "your-value",
        "TABULARIUM_URL": "your-value",
        "TABULARIUM_PAY_MAX_USD": "your-value",
        "TABULARIUM_PAY_NETWORKS": "your-value",
        "TABULARIUM_PUBKEY": "your-value"
      }
    }
  }
}

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

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "tabularium": {
      "type": "http",
      "url": "https://tabularium.matt-3e0.workers.dev/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "tabularium": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tabularium-mcp"
      ],
      "env": {
        "TABULARIUM_PRIVATE_KEY": "your-value",
        "TABULARIUM_MAX_SPEND_USD": "your-value",
        "TABULARIUM_URL": "your-value",
        "TABULARIUM_PAY_MAX_USD": "your-value",
        "TABULARIUM_PAY_NETWORKS": "your-value",
        "TABULARIUM_PUBKEY": "your-value"
      }
    }
  }
}

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

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://tabularium.matt-3e0.workers.dev/mcp

Menu names can differ slightly by plan and over time.

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

Values you fill in

  • TABULARIUM_PRIVATE_KEY secret required env
    0x-prefixed EVM private key of the wallet that pays (use a dedicated wallet with a small USDC balance)
  • TABULARIUM_MAX_SPEND_USD env
    Spend cap for this server process, in USD
  • TABULARIUM_URL env
    Service base URL (defaults to the public deployment)
  • TABULARIUM_PAY_MAX_USD env
    tabularium_pay: most one purchase may cost, in USD (ceiling 0.50)
  • TABULARIUM_PAY_NETWORKS env
    tabularium_pay: comma-separated networks it may pay on; default is the service's own network. eip155:8453 is mainnet (real money).
  • TABULARIUM_PUBKEY env
    Optional pinned Ed25519 signing key (hex) that exports must verify against

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

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

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

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Accounting, finance & taxi

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

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

Common questions

Is Tabularium safe?

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

What keys or codes does it need?

You need to fill in: TABULARIUM_PRIVATE_KEY

Does it run on my computer or in the cloud?

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

Is it still maintained?

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

Which apps can use it?

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

What can I use instead?

In the same category: Finance Toolkit, SolidInvoice, Korea Tax Calculator

Alternatives

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

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

Finance Toolkit

by JerBouma

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

Computer or cloud★ 5,496MITUpdated yesterday
Install

SolidInvoice

by SolidInvoice

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

Runs in the cloud★ 981MITUpdated 7 days ago
Install

Korean tax calculation and tax-audit judgment MCP: 95 tools with statutory citations.

Runs on your computer★ 97MITUpdated today
Install

README from the maker

Open the README

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

tabularium-mcp

MCP server for Tabularium: a paid, persistent, hash-chained workspace for AI agents. Your agent's EVM wallet pays each call in USDC over x402, and that wallet is the account. There is no sign-up and no API key.

Tools

ToolCostWhat
tabularium_menufreePrices, policy, network, public signing key.
tabularium_write$0.003Append {key, value}. Retries reuse one idempotency key, so a retry never writes twice.
tabularium_read$0.002Latest value for a key, with its chain entry.
tabularium_renew$0.25Extend the workspace 30 days.
tabularium_export$0.01Full signed history, verified offline before it is returned. save_to writes it to a file.
tabularium_headfreeSigned head (seq + hash, no values) for any wallet; defaults to yours.
tabularium_verifyfree, localRe-verify a saved export without trusting the server.
tabularium_paythe endpoint's price + one writePay any x402 v2 endpoint in USDC and write a signed receipt (reason, the full accepted terms, amount, payee, network, transaction, response hash, and an intent the wallet signed before paying) to ledger/ /.... purchase_id makes retries safe: the same id never pays twice.
tabularium_ledgerone exportVerify the workspace and total the receipts: spend by service and by day, latest receipts; checks every payer-signed intent against its receipt.
tabularium_reconcileone exportCompare receipts with the USDC payments the wallet actually settled on-chain (last 1-30 days): purchases with no receipt, receipts with no settlement, and receipts that differ from the chain.

Failed calls (4xx/5xx) are never charged.

More Tabularium services

Tabularium is a platform: the same wallet pays for every service it offers, and memory is the first. When the server starts, it reads the live menu and turns each paid call of every other service into its own tool, named tabularium_ _ , with the input fields and price the menu lists. A new service therefore shows up the next time your MCP client starts, without a new version of this package. These tools follow the same rules as the memory tools: the payee must be the menu's, the price at most the menu price (and never above $0.50), the session spend cap applies, and redirects are never followed. A call that settles after it runs is not retried after a failed payment, because it may already have run. Menu entries that do not fit these rules are skipped, not guessed at.

Prompts

Ready-made starting points your MCP client lists (in Claude Code, type / to see them):

PromptWhat
load_memoryStart a session from what was stored before: read an index key (default index), then the entries it lists.
spending_reportWhat has my agent spent? Totals by service and day, and the largest purchases with their reasons.

The server also tells the model, when it connects, which tools are free and which cost money, plus a simple memory pattern: keep an index key, read it at the start, write decisions as they happen.

The spending ledger

tabularium_pay answers the question every operator asks: *what did my agent buy, from whom, for how much, and why?* Each settled purchase becomes one entry in the agent's hash-chained, server-signed workspace, so the record can be exported and verified offline, with the on-chain transaction hash alongside. Safety rules: USDC via EIP-3009 only, allowed networks only, a per-purchase maximum, and the session spend cap is checked against the real price plus the receipt before anything is signed. A receipt's idempotency key is its payment nonce, so a retry never records twice; if a receipt write fails after a purchase settled, the tool still returns the purchase and the receipt to re-record. Paid requests never follow redirects (payment and receipt stay with the URL asked for), and a signed authorization is valid for at most 10 minutes whatever the seller asks.

Since 0.5 (from review on Moltbook's m/agentfinance):

  • The reason is a commitment, not a note. Before the payment is signed, the wallet signs (EIP-191) an intent: the request, the exact terms accepted, the payment nonce, and the reason. The receipt keeps it, so the payer cannot later edit the reason and the server cannot invent one. It is still a claim, and the receipt says so (reasonStatus). Check one with any EIP-191 verifier, or let tabularium_ledger check them all.
  • The promise is in the record. The receipt holds the full accepts[] entry the payer accepted and its hash, next to the payment (transaction) and the delivery (response hash).
  • Retries cannot pay twice. With purchase_id, the signed authorization is kept (in TABULARIUM_STATE_DIR) until the purchase is known to have settled. Calling again sends that same authorization, which can settle at most once; a purchase that settled while its response was lost is found on-chain and recorded once.
  • Completeness is checkable. A hash chain shows rows were not edited, not that none are missing. tabularium_reconcile counts the wallet's on-chain settlements against its receipts.
Remote endpoint (no install)

Clients that pay x402 over MCP themselves (Coinbase's wrapMCPClientWithPayment, Cloudflare's withX402Client) can skip this package and connect to https://tabularium.matt-3e0.workers.dev/mcp (Streamable HTTP). It offers the memory and snapshot calls as tools at the same prices. An unpaid call returns PaymentRequired; the retry carries the payment in params._meta["x402/payment"]. tabularium_pay, the ledger and verification stay in this package, because they need your wallet and should not trust the server.

Configure

EnvRequiredMeaning
TABULARIUM_PRIVATE_KEYfor paid tools0x-prefixed EVM private key that pays. Use a dedicated wallet with a small balance.
TABULARIUM_URLnoService URL. Default: the public deployment (Base mainnet).
TABULARIUM_PUBKEYnoPin the server's Ed25519 key (hex). Exports are verified against it, and a mismatch with the published key is reported.
TABULARIUM_MAX_SPEND_USDnoSpend cap for this server process, across all tools. Default 1.
TABULARIUM_PAY_MAX_USDnotabularium_pay: most one purchase may cost. Default 0.10, ceiling 0.50.
TABULARIUM_TESTnoMarks this process's requests to the service as test traffic, kept out of its public demand stats. For the service's own test runs.
TABULARIUM_RPC_URLnoJSON-RPC for the service's network, used by tabularium_reconcile and to check whether an unconfirmed payment settled. Default: a public Base node.
TABULARIUM_STATE_DIRnoWhere purchase_id records are kept. Default ~/.tabularium-mcp.
TABULARIUM_PAY_NETWORKSnotabularium_pay: networks it may pay on (comma-separated CAIP-2). Default: the service's own network, which for the public service is Base mainnet (eip155:8453): purchases spend real USDC, within TABULARIUM_PAY_MAX_USD and the spend cap. Set eip155:84532 to keep purchases on testnet.

The public service runs on Base mainnet: the paying wallet needs real USDC on Base. It needs no ETH, because the facilitator pays the transaction fees. Use a dedicated wallet holding only a few dollars.

Claude Code:

claude mcp add tabularium --env TABULARIUM_PRIVATE_KEY=0x... -- npx -y tabularium-mcp

Claude Desktop / other clients (mcpServers JSON):

{

"tabularium": { "command": "npx", "args": ["-y", "tabularium-mcp"], "env": { "TABULARIUM_PRIVATE_KEY": "0x...", "TABULARIUM_MAX_SPEND_USD": "0.50" } } }

Speaks x402 v2. Three dependencies (MCP SDK, viem, zod). Payments are signed locally (EIP-3009 USDC authorization); the server refuses to sign anything other than USDC to the payee and price the service's own menu lists. Versions before 0.2.0 spoke x402 v1 and no longer work against the service.

Develop

npm install cp ../verifier/verify.mjs verify.mjs # also runs on prepack; a root test fails if the copy drifts npm test # offline: payment guards (wrong asset/payee/price/network refused), service tools node smoke.mjs # 30 checks over stdio against the live service (PAYER_FILE picks the wallet) node smoke.mjs --npx tabularium-mcp@X # same checks against a published version

Ask PopNx