mcpbeat

Journalize MCP Server

dev.journalize/journalize
answering

Journalize is answering right now. Last checked 8 min ago. It exposes 11 tools.

Agent-native double-entry accounting ledger with x402 micropayments

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
283 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add journalize --transport http https://journalize.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "journalize": {
      "url": "https://journalize.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.journalize]
url = "https://journalize.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "journalize": {
      "url": "https://journalize.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "journalize": {
      "url": "https://journalize.dev/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

submit
submit_batch
Submit up to 1000 directives atomically — all persist together or none do. Priced 10x a single write, regardless of batch size within the cap. Always paid — the free-trial allowance (see submit_directive) applies to single writes only, never to batches, even if you haven't used any free writes yet. Paid.
submit_directive
Submit one Beancount directive (open, transaction, close, balance, price, note, document — any type). Paid, except your first 20 accepted writes per registered key, which are free (this specific tool only — submit_batch is always paid, even for your first call). Call with no payment_header first: if free writes remain, this succeeds immediately; otherwise you'll get price/asset/recipient back, so you can retry with payment_header set to your signed X-PAYMENT-equivalent payload (fresh nonce required on the retry — each call is independently signed).
account
get_account_balance
Balance of a single account. Settles at the same fixed price whether the account exists or not — an "unknown account" answer is still a valid, billable response (no per-error pricing discount). No free-trial allowance for this specific tool, unlike list_directives (same price, but list_directives has 2 free calls and this doesn't) — the free tier applies to browsing (list_directives, list_accounts) and the report tier, not per-account lookups.
accounts
list_accounts
List all opened accounts with their currency constraints and booking method. No booking pass involved. Your first 2 calls per registered key are free (a separate allowance from list_directives' and the report tier's — see those tools).
balance
get_balance_sheet
Full realize() balance sheet — often served from cache. Settles at the same fixed price regardless of cache hit/miss. Shares a combined free allowance of 2 with export_ledger, get_income_statement, and get_trial_balance (the "report tier") — not 2 free calls each.
directives
list_directives
List raw directives (optionally filtered by account/date range). No booking involved — cheapest paid tool. `since`/`until` are ISO date strings (YYYY-MM-DD). Your first 2 calls per registered key are free (independent of the write/accounts/report allowances — see list_accounts, get_balance_sheet).
export
export_ledger
Export the full ledger as literal Beancount text — a portable snapshot for fava/bean-report/etc., not the live store. Shares a combined free allowance of 2 with get_balance_sheet, get_income_statement, and get_trial_balance (the "report tier") — not 2 free calls for each of those four separately.
income
get_income_statement
Income statement, period-scoped by since/until (ISO date strings, both optional — omitted means whole history). Always books full history first, then clamps the output to the requested period (never filters input dates — see reports.py for why). Shares a combined free allowance of 2 with export_ledger, get_balance_sheet, and get_trial_balance (the "report tier") — not 2 free calls each.
register
register
Generate a new Ed25519 keypair for ledger identity. Returns the private key exactly once — it is never stored server-side and cannot be recovered if lost. This is a SEPARATE keypair from whatever wallet you use to authorize x402 payments (payment auth and ledger identity are two independent signing domains — see payments.py).
trial
get_trial_balance
Trial balance, period-scoped same as income statement — same underlying compute, priced and audited as its own resource. Shares a combined free allowance of 2 with export_ledger, get_balance_sheet, and get_income_statement (the "report tier") — not 2 free calls each.
validate
validate_directive
Free dry-run: parse+book text against your full history without persisting or charging anything. Still requires a valid signature (identity/replay protection is not a billing concern).

Endpoints

URLTransportStateLatencyChecked
https://journalize.dev/mcp streamable-http answering 304 ms 8 min ago

Journalize — questions

Answers built from our own checks of this server.

What can Journalize do?
It exposes 11 tools, read directly from the server on our last check. Among them: export_ledger, get_account_balance, get_balance_sheet, get_income_statement, get_trial_balance, list_accounts and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Journalize working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 283 ms. The bar chart above shows every period we have measured.
How do I connect Journalize?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Journalize need an API key?
No. Journalize completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Journalize?
It answers our handshake in 283 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.