Skip to content

dev.journalize/journalize

by journalize.dev · remote · no sign-in to list tools · v1.0.0 · published by dev.journalize

Agent-native double-entry accounting ledger with x402 micropayments

Final · 1Changes · 3

11 tools: 1 do something that can't be undone, 3 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http journalize https://journalize.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Can't be undone 1Claude Code: ask
  • registerGenerate a new Ed25519 keypair for ledger identity.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The description says "cannot be recovered".
    Description, as the server wrote it
    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).
Changes things 3Claude Code: ask
  • export_ledgerExport the full ledger as literal Beancount text — a portable snapshot for fava/bean-report/etc., not the live store.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • submit_batchSubmit up to 1000 directives atomically — all persist together or none do.No findings

    Why it is in this group

    • The name "submit_batch" says "submit": a word for a change.
    Description, as the server wrote it
    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_directiveSubmit one Beancount directive (open, transaction, close, balance, price, note, document — any type).No findings

    Why it is in this group

    • The name "submit_directive" says "submit": a word for a change.
    Description, as the server wrote it
    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).
Only reads 7Claude Code: allow
  • get_account_balanceBalance of a single account.No findings

    Why it is in this group

    • The name "get_account_balance" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_balance_sheetFull realize() balance sheet — often served from cache.No findings

    Why it is in this group

    • The name "get_balance_sheet" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_income_statementIncome statement, period-scoped by since/until (ISO date strings, both optional — omitted means whole history).No findings

    Why it is in this group

    • The name "get_income_statement" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_trial_balanceTrial balance, period-scoped same as income statement — same underlying compute, priced and audited as its own resource.No findings

    Why it is in this group

    • The name "get_trial_balance" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_accountsList all opened accounts with their currency constraints and booking method.No findings

    Why it is in this group

    • The name "list_accounts" says "list": a word for reading.
    Description, as the server wrote it
    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).
  • list_directivesList raw directives (optionally filtered by account/date range).No findings

    Why it is in this group

    • The name "list_directives" says "list": a word for reading.
    Description, as the server wrote it
    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).
  • validate_directiveFree dry-run: parse+book text against your full history without persisting or charging anything.No findings

    Why it is in this group

    • The name "validate_directive" says "validate": a word for reading.
    Description, as the server wrote it
    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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http journalize https://journalize.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__journalize__validate_directive",
      "mcp__journalize__list_directives",
      "mcp__journalize__list_accounts",
      "mcp__journalize__get_account_balance",
      "mcp__journalize__get_balance_sheet",
      "mcp__journalize__get_income_statement",
      "mcp__journalize__get_trial_balance"
    ],
    "ask": [
      "mcp__journalize__submit_directive",
      "mcp__journalize__submit_batch",
      "mcp__journalize__export_ledger",
      "mcp__journalize__register"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as journalize. Review it before you use it.