Home / MCP registry index / io.usefulapi/jurnal

Mekari Jurnal MCP by usefulapi

io.usefulapi/jurnal in the official MCP registry. Endpoint https://jurnal.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: MCP server for Mekari Jurnal — company accounting, sales, purchases and customer/vendor creation.

We read its 38 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http jurnal https://jurnal.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "jurnal": {
      "url": "https://jurnal.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"jurnal","type":"http","url":"https://jurnal.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

jurnal_get_current_user jurnal_list_companies jurnal_list_customers jurnal_get_customer jurnal_list_vendors jurnal_get_vendor jurnal_list_products jurnal_get_product jurnal_list_accounts jurnal_get_account jurnal_list_sales_invoices jurnal_get_sales_invoice jurnal_list_sales_orders jurnal_list_sales_quotes jurnal_list_receive_payments jurnal_list_purchase_invoices jurnal_get_purchase_invoice jurnal_list_purchase_orders jurnal_list_purchase_payments jurnal_list_expenses jurnal_get_expense jurnal_list_journal_entries jurnal_get_journal_entry jurnal_list_taxes jurnal_list_tags jurnal_list_payment_methods jurnal_list_warehouses jurnal_list_product_categories jurnal_get_profit_and_loss jurnal_get_balance_sheet jurnal_get_trial_balance jurnal_get_cash_flow jurnal_get_general_ledger jurnal_get_aged_receivables jurnal_get_aged_payables jurnal_get_executive_summary jurnal_create_customer jurnal_create_vendor

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 3d1992305f55eb16. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-jurnal/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-jurnal)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.