dev.journalize/journalize
REMOTE · JOURNALIZE.DEV · SCANNED SEP 28
Agent-native double-entry accounting ledger with x402 micropayments
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1403 tokens (~127/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dev.journalize/journalize MCP server?
dev.journalize/journalize is a hosted endpoint at https://journalize.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · journalize.dev
claude mcp add --transport http dev-journalize-journalize 'https://journalize.dev/mcp'
{
"mcpServers": {
"dev-journalize-journalize": {
"url": "https://journalize.dev/mcp"
}
}
} {
"servers": {
"dev-journalize-journalize": {
"type": "http",
"url": "https://journalize.dev/mcp"
}
}
} [mcp_servers.dev-journalize-journalize] url = "https://journalize.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-journalize-journalize": {
"type": "remote",
"url": "https://journalize.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-journalize-journalize --url 'https://journalize.dev/mcp' --transport streamable-http
mcp_servers:
dev-journalize-journalize:
url: "https://journalize.dev/mcp" {
"McpServers": {
"dev-journalize-journalize": {
"Transport": "http",
"Url": "https://journalize.dev/mcp"
}
}
} assistant mcp add dev-journalize-journalize -t streamable-http -u 'https://journalize.dev/mcp'
{
"mcpServers": {
"dev-journalize-journalize": {
"type": "http",
"url": "https://journalize.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 +28
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 18 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://journalize.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=journalize.dev | CN=WE1,O=Google Trust Services,C=US | 30 Aug 2026 | 28 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 33ff7a25008331bb1353e91a9bbfa93a |
| SANs: journalize.dev, *.journalize.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of journalize.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| journalize.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://journalize.dev/mcp | Verified | 200 | |
| http (plaintext) | http://journalize.dev/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_ledger ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
get_account_balance ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
get_balance_sheet ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
get_income_statement ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| since | – | – | – |
| timestamp | string | yes | – |
| until | – | – | – |
No output schema declared.
No examples provided.
get_trial_balance ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| since | – | – | – |
| timestamp | string | yes | – |
| until | – | – | – |
No output schema declared.
No examples provided.
list_accounts ~94
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).
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
list_directives ~138
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).
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | – |
| limit | integer | – | – |
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| since | – | – | – |
| timestamp | string | yes | – |
| until | – | – | – |
No output schema declared.
No examples provided.
register ~81
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_batch ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| directives | array | yes | – |
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
submit_directive ~180
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).
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| payment_header | – | – | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| text | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
validate_directive ~84
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).
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | – |
| public_key | string | yes | – |
| signature | string | yes | – |
| text | string | yes | – |
| timestamp | string | yes | – |
No output schema declared.
No examples provided.
What is the dev.journalize/journalize MCP server?
dev.journalize/journalize is an MCP server listed in the public MCP registry as dev.journalize/journalize. Agent-native double-entry accounting ledger with x402 micropayments. This page covers its hosted endpoint (https://journalize.dev/mcp).
Is the dev.journalize/journalize MCP server safe to use?
dev.journalize/journalize scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.journalize/journalize MCP server expose?
dev.journalize/journalize exposes 11 tools: submit_directive, validate_directive, submit_batch, list_directives, list_accounts, and 6 more. Their descriptions and schemas cost roughly 1,357 tokens of context every time the server is loaded.
Does the dev.journalize/journalize MCP server require authentication?
No. We connected to dev.journalize/journalize without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.journalize/journalize MCP server still maintained?
dev.journalize/journalize is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.