dev.journalize/journalize
REMOTE · JOURNALIZE.DEV · SCANNED AUG 3
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 →
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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability44
- AI-judged instruction clarity (fair).Partial
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · journalize.dev
claude mcp add --transport http dev-journalize-journalize 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 48
First indexed and scored.
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 3 Aug 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 | 2 Jul 2026 | 30 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | ba0cd58c47adaf2c13f02d92ecaceef9 |
| 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 |
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 |
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.
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.