
Journalize MCP server
Which servers in the official MCP registry are Journalize's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry namedev.journalize/journalizeverified in the MCP registry
The registry name sits under journalize.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools11
- Server calls itselfagent-native-ledger
- Server version1.28.1
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 37 ms.
- Its tools do every use case we checked: track agent spending in a persistent double-entry ledger; generate balance sheets and income statements on demand.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- For "track agent spending in a persistent double-entry ledger", the likely first call is register.
- For "generate balance sheets and income statements on demand", the likely first call is get_balance_sheet.
- Parameters are untyped or undescribed in 10 of 11 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- What an agent can do with it2 of 2 use cases
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer84 ms
- Space in an agent's context≈ 2,390 tokensthe definitions of all its tools (11), which an agent carries on every turn
- Tool definitionsC · 68 of 100
- Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 10 of 11
- Not saying whether it only reads or can destroy: 11 of 11
What an agent can do with it
- can do · track agent spending in a persistent double-entry ledger
- not sure · split bills and reconcile invoices for an agent
- can do · generate balance sheets and income statements on demand
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
submit_directiveSubmit 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…
validate_directiveFree 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).
submit_batchSubmit 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…
list_directivesList 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…
list_accountsList 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).
get_account_balanceBalance 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…
export_ledgerExport 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…
get_balance_sheetFull 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…
get_income_statementIncome 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…
get_trial_balanceTrial 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…
registerGenerate 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"journalize": {
"type": "http",
"url": "https://journalize.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http journalize https://journalize.dev/mcpclaude.ai, ChatGPT and other clients: add https://journalize.dev/mcp as a custom connector in the settings.
OpenAPI spec
20 paths, read 2026-10-26. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.