# Journalize MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.journalize%2Fjournalize
Registry id: `mcp-registry/dev.journalize/journalize`
Status: live (checked 2026-10-27T03:38:12.027Z)

## Measurements (30 days)

- Uptime: 99.95%
- Checks: 4948
- Outages (90 days): 5

## Install

```json
{
  "mcpServers": {
    "journalize-mcp-server": {
      "type": "http",
      "url": "https://journalize.dev/mcp"
    }
  }
}
```

Claude Code:

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

## Tools (11)

- `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_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
- `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
- `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
- `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 w
- `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 separat
- `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). Yo
- `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 
- `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
- `submit_directive`: Submit one Beancount directive (open, transaction, close, balance, price, note, document — any type). Paid, except your first 20 accepted writes per registered 
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.