Developer Tools

journalize.dev

Provides an API to manage Beancount accounting directives, allowing submission, validation, and querying of financial data.

2 endpoints11 known toolsFirst detected July 23, 2026Last detected September 3, 2026

ENDPOINT 1

https://journalize.dev/mcp

No auth detected

MCP server metadata

Name: agent-native-ledger
Version: 1.28.1

Capabilities

experimentalpromptsresourcestools

Server instructions

A double-entry accounting ledger for AI agents. Every write and read is a paid x402 action except register and validate_directive. Call register once to get a keypair, then sign every subsequent call with it.

Known tools 11

submit_directive

Submit one Beancount directive (open, transaction, close, balance, price, note, document — any type).

Inferred read-only

validate_directive

Free dry-run: parse+book text against your full history without persisting or charging anything.

Inferred read-only

submit_batch

Submit up to 1000 directives atomically — all persist together or none do.

Inferred read-only

list_directives

List raw directives (optionally filtered by account/date range).

Inferred read-only

list_accounts

List all opened accounts with their currency constraints and booking method.

Inferred read-only

get_account_balance

Balance of a single account.

Inferred read-only

export_ledger

Export the full ledger as literal Beancount text — a portable snapshot for fava/bean-report/etc., not the live store.

Inferred read-only

get_balance_sheet

Full realize() balance sheet — often served from cache.

Inferred read-only

get_income_statement

Income statement, period-scoped by since/until (ISO date strings, both optional — omitted means whole history).

Inferred read-only

get_trial_balance

Trial balance, period-scoped same as income statement — same underlying compute, priced and audited as its own resource.

Inferred read-only

register

Generate a new Ed25519 keypair for ledger identity.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agent-native-ledger]
url = "https://journalize.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "agent-native-ledger": {
      "type": "http",
      "url": "https://journalize.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: agent-native-ledger
Remote MCP URL: https://journalize.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agent-native-ledger": {
      "url": "https://journalize.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "agent-native-ledger": {
      "type": "http",
      "url": "https://journalize.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "agent-native-ledger",
  "transport": "streamable-http",
  "url": "https://journalize.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://journalize.dev/mcp-deprecated-do-not-use

No auth detected

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.journalize-dev]
url = "https://journalize.dev/mcp-deprecated-do-not-use"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "journalize-dev": {
      "type": "http",
      "url": "https://journalize.dev/mcp-deprecated-do-not-use"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: journalize-dev
Remote MCP URL: https://journalize.dev/mcp-deprecated-do-not-use

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "journalize-dev": {
      "url": "https://journalize.dev/mcp-deprecated-do-not-use"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "journalize-dev": {
      "type": "http",
      "url": "https://journalize.dev/mcp-deprecated-do-not-use"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "journalize-dev",
  "transport": "streamable-http",
  "url": "https://journalize.dev/mcp-deprecated-do-not-use"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for journalize.dev was fetched 2026-07-28T00:00:06.559Z and is being refreshed.

Trust status Neutral

journalize.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.