Is the Journalize MCP server down?

mcp-registry/dev.journalize/journalize · v1.28.1

healthy
Last checked 2026-10-27 01:56 UTC · handshake 95ms

As of 2026-10-27 01:56 UTC, the Journalize MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
4,935
outages (90d)
5
tools
11

Agent-native double-entry accounting ledger with x402 micropayments

Point your MCP client at this streamable-http endpoint: https://journalize.dev/mcp

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 3 warning(s) across 11 tool(s); ~2,629 tokens of tool definitions.
Scores higher than 1% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~2,629 tokens per session — more than 50% of servers.
66 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints5
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

11 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: export_ledger, get_account_balance, get_balance_sheet, get_income_statement, get_trial_balance and 6 more

61 parameter(s) across 10 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: export_ledger, get_account_balance, get_balance_sheet, get_income_statement, get_trial_balance and 5 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: submit_batch, submit_directive

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 10 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.journalize%2Fjournalize/fixes

export_ledger 1 change 
{
  "name": "export_ledger",
  "description": "Export the full ledger as literal Beancount text — a portable\n    snapshot for fava/bean-report/etc., not the live store. Shares a\n    combined free allowance of 2 with get_balance_sheet,\n    get_income_statement, and get_trial_balance (the \"report tier\") — not\n    2 free calls for each of those four separately.",
  "inputSchema": {
    "type": "object",
    "title": "export_ledgerArguments",
    "required": [
      "public_key",
      "nonce",
      "timestamp",
      "signature"
    ],
    "properties": {
      "nonce": {
        "type": "string",
        "title": "Nonce"
      },
      "signature": {
        "type": "string",
        "title": "Signature"
      },
      "timestamp": {
        "type": "string",
        "title": "Timestamp"
      },
      "public_key": {
        "type": "string",
        "title": "Public Key"
      },
      "payment_header": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Payment Header",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_account_balance 1 change 
{
  "name": "get_account_balance",
  "description": "Balance of a single account. Settles at the same fixed price\n    whether the account exists or not — an \"unknown account\" answer is\n    still a valid, billable response (no per-error pricing discount). No\n    free-trial allowance for this specific tool, unlike list_directives\n    (same price, but list_directives has 2 free calls and this doesn't) —\n    the free tier applies to browsing (list_directives, list_accounts)\n    and the report tier, not per-account lookups.",
  "inputSchema": {
    "type": "object",
    "title": "get_account_balanceArguments",
    "required": [
      "account",
      "public_key",
      "nonce",
      "timestamp",
      "signature"
    ],
    "properties": {
      "nonce": {
        "type": "string",
        "title": "Nonce"
      },
      "account": {
        "type": "string",
        "title": "Account"
      },
      "signature": {
        "type": "string",
        "title": "Signature"
      },
      "timestamp": {
        "type": "string",
        "title": "Timestamp"
      },
      "public_key": {
        "type": "string",
        "title": "Public Key"
      },
      "payment_header": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Payment Header",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_balance_sheet 1 change 
{
  "name": "get_balance_sheet",
  "description": "Full realize() balance sheet — often served from cache. Settles at\n    the same fixed price regardless of cache hit/miss. Shares a combined\n    free allowance of 2 with export_ledger, get_income_statement, and\n    get_trial_balance (the \"report tier\") — not 2 free calls each.",
  "inputSchema": {
    "type": "object",
    "title": "get_balance_sheetArguments",
    "required": [
      "public_key",
      "nonce",
      "timestamp",
      "signature"
    ],
    "properties": {
      "nonce": {
        "type": "string",
        "title": "Nonce"
      },
      "signature": {
        "type": "string",
        "title": "Signature"
      },
      "timestamp": {
        "type": "string",
        "title": "Timestamp"
      },
      "public_key": {
        "type": "string",
        "title": "Public Key"
      },
      "payment_header": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Payment Header",
        "default": null
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.journalize/journalize"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.journalize/journalize"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.journalize%2Fjournalize.svg)](https://glimind.com/server/mcp-registry%2Fdev.journalize%2Fjournalize?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fdev.journalize%2Fjournalize?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.journalize%2Fjournalize.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.journalize%2Fjournalize.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.journalize%2Fjournalize?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:203f7a2eb56301b6…, first seen 2026-10-17, included at leaf 366 of 76,725. Version history · verify what your client received.

Tools (11)

Compare: most reliable data servers · most reliable finance servers · most reliable security servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Journalize MCP server down right now?

As of 2026-10-27 01:56 UTC, the Journalize MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Journalize MCP server provide?

Journalize MCP server advertises 11 tools, including export_ledger, get_account_balance, get_balance_sheet, get_income_statement, get_trial_balance.

How do I install Journalize MCP server?

Point your MCP client at this streamable-http endpoint: https://journalize.dev/mcp

Is the Journalize MCP server safe to connect to an AI agent?

Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Journalize MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve