# Mekari Jurnal MCP by usefulapi (remote · jurnal.usefulapi.io)

MCP server for Mekari Jurnal — company accounting, sales, purchases and customer/vendor creation.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `jurnal.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal.md), [page](https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal)

## Channel facts

- Endpoint: `https://jurnal.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Mekari Jurnal MCP by usefulapi server?

Mekari Jurnal MCP by usefulapi is a hosted endpoint at https://jurnal.usefulapi.io/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.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "io-usefulapi-jurnal": {
      "type": "http",
      "url": "https://jurnal.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-jurnal]
url = "https://jurnal.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-jurnal": {
      "type": "remote",
      "url": "https://jurnal.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-jurnal --url 'https://jurnal.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-jurnal:
    url: "https://jurnal.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-jurnal": {
      "Transport": "http",
      "Url": "https://jurnal.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-jurnal -t streamable-http -u 'https://jurnal.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-jurnal": {
      "type": "http",
      "url": "https://jurnal.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (38)

### `jurnal_get_current_user` (~43 tokens)

Get the current user

The Jurnal user the credential acts as: id, name, email, status, owner flag and roles. GET /public/jurnal/api/v1/users/me.

### `jurnal_list_companies` (~93 tokens)

List companies

The Jurnal company (or companies) the credential belongs to: id, name, industry, address, tax number, currency settings and feature flags. GET /companies.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_customers` (~144 tokens)

List customers

Customers with display name, addresses, email, phone, tax number and receivable balance. Paged. GET /customers.

Input parameters:

- `include_archive` (boolean): false = only active (non-archived) records; Jurnal includes archived ones by default.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).
- `sort_key` (string): Sort field: display_name, billing_address, email, phone, balance_customer.
- `sort_order` (string): Sort direction.

### `jurnal_get_customer` (~35 tokens)

Get a customer

One customer by id (from jurnal_list_customers). GET /customers/{id}.

Input parameters:

- `id` (integer, required): Customer id.

### `jurnal_list_vendors` (~144 tokens)

List vendors

Vendors (suppliers) with display name, addresses, email, phone, tax number and payable balance. Paged. GET /vendors.

Input parameters:

- `include_archive` (boolean): false = only active (non-archived) records; Jurnal includes archived ones by default.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).
- `sort_key` (string): Sort field: display_name, billing_address, email, phone.
- `sort_order` (string): Sort direction.

### `jurnal_get_vendor` (~35 tokens)

Get a vendor

One vendor by id (from jurnal_list_vendors). GET /vendors/{id}.

Input parameters:

- `id` (integer, required): Vendor id.

### `jurnal_list_products` (~165 tokens)

List products

Products and services: code, name, buy and sell prices, stock quantity, category, units, active flag. Paged. GET /products.

Input parameters:

- `include_archive` (boolean): false = only active (non-archived) records; Jurnal includes archived ones by default.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).
- `sort_key` (string): Sort field: product_code, name, quantity_inventory, last_avg_price, last_buy_price, buy_price_per_unit, sell_price_per_unit, product_categories_name.
- `sort_order` (string): Sort direction.

### `jurnal_get_product` (~34 tokens)

Get a product

One product by id (from jurnal_list_products). GET /products/{id}.

Input parameters:

- `id` (integer, required): Product id.

### `jurnal_list_accounts` (~74 tokens)

List chart of accounts

The chart of accounts: id, number, name, category, currency and balance. Not paged. Use the ids as account_id in jurnal_get_general_ledger. GET /accounts.

Input parameters:

- `include_archive` (boolean): false = only active (non-archived) records; Jurnal includes archived ones by default.

### `jurnal_get_account` (~33 tokens)

Get an account

One chart-of-accounts entry by id. GET /accounts/{id}.

Input parameters:

- `id` (integer, required): Account id.

### `jurnal_list_sales_invoices` (~146 tokens)

List sales invoices

Sales invoices: number, customer, dates, status, total (original_amount) and balance due (remaining). Sort by transaction_date or remaining to find recent or unpaid ones. Paged. GET /sales_invoices.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).
- `sort_key` (string): Sort field: transaction_date, get_number, people_display_name, transaction_status_name, remaining, original_amount, created_at.
- `sort_order` (string): Sort direction.

### `jurnal_get_sales_invoice` (~39 tokens)

Get a sales invoice

One sales invoice with its lines, taxes and payments. GET /sales_invoices/{id}.

Input parameters:

- `id` (integer, required): Sales invoice id.

### `jurnal_list_sales_orders` (~78 tokens)

List sales orders

Sales orders with customer, dates, status and totals. Paged. GET /sales_orders.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_sales_quotes` (~81 tokens)

List sales quotes

Sales quotes (offers) with customer, dates, status and totals. Paged. GET /sales_quotes.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_receive_payments` (~76 tokens)

List received payments

Customer payments received against sales invoices. Paged. GET /receive_payments.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_purchase_invoices` (~198 tokens)

List purchase invoices

Purchase invoices (bills from vendors): number, vendor, dates, status, total and balance due. Paged. GET /purchase_invoices.

Input parameters:

- `end_date` (string): Only transactions up to this date, yyyy-mm-dd. Needs sort_key transaction_no or created_at.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).
- `sort_key` (string): Sort field: transaction_date, created_at, transaction_no, people_display_name, due_date, transaction_status_name, remaining, original_amount.
- `sort_order` (string): Sort direction.
- `start_date` (string): Only transactions from this date, yyyy-mm-dd. Needs sort_key transaction_no or created_at (Jurnal applies the date range only with those).

### `jurnal_get_purchase_invoice` (~39 tokens)

Get a purchase invoice

One purchase invoice with its lines, taxes and payments. GET /purchase_invoices/{id}.

Input parameters:

- `id` (integer, required): Purchase invoice id.

### `jurnal_list_purchase_orders` (~78 tokens)

List purchase orders

Purchase orders with vendor, dates, status and totals. Paged. GET /purchase_orders.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_purchase_payments` (~77 tokens)

List purchase payments

Payments made to vendors against purchase invoices. Paged. GET /purchase_payments.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_expenses` (~116 tokens)

List expenses

Expenses: number, date, beneficiary, status, total and balance due. Paged. GET /expenses.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).
- `sort_key` (string): Sort field: transaction_date, transaction_no, transaction_status_name, remaining, original_amount.
- `sort_order` (string): Sort direction.

### `jurnal_get_expense` (~31 tokens)

Get an expense

One expense with its lines. GET /expenses/{id}.

Input parameters:

- `id` (integer, required): Expense id.

### `jurnal_list_journal_entries` (~75 tokens)

List journal entries

Manual journal entries (general journal). Paged. GET /journal_entries.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_get_journal_entry` (~38 tokens)

Get a journal entry

One journal entry with its debit and credit lines. GET /journal_entries/{id}.

Input parameters:

- `id` (integer, required): Journal entry id.

### `jurnal_list_taxes` (~81 tokens)

List taxes

The company's tax rates (PPN, PPh and so on). Paged. GET /taxes.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_tags` (~20 tokens)

List transaction tags

Transaction tags. Not paged. GET /tags.

### `jurnal_list_payment_methods` (~29 tokens)

List payment methods

Payment methods (cash, transfer and so on). Not paged. GET /payment_methods.

### `jurnal_list_warehouses` (~79 tokens)

List warehouses

Warehouses (needs a Jurnal plan with inventory). Paged. GET /warehouses.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `page_size` (integer): Results per page, 1-100 (Jurnal's default applies when omitted).

### `jurnal_list_product_categories` (~22 tokens)

List product categories

Product categories. Not paged. GET /product_categories.

### `jurnal_get_profit_and_loss` (~108 tokens)

Get the profit and loss report

Profit and loss (income statement) for a period: revenue, cost of sales, expenses and net profit by account. Dates are yyyy-mm-dd. GET /profit_and_loss.

Input parameters:

- `compare_type` (string): Period shortcut (day = today). Use custom with start_date and end_date.
- `end_date` (string): End of the period, yyyy-mm-dd (default today).
- `start_date` (string): Start of the period, yyyy-mm-dd (default today).

### `jurnal_get_balance_sheet` (~56 tokens)

Get the balance sheet

Balance sheet as of end_date (yyyy-mm-dd, default today): assets, liabilities and equity by account. GET /balance_sheet.

Input parameters:

- `end_date` (string): End of the period, yyyy-mm-dd (default today).

### `jurnal_get_trial_balance` (~92 tokens)

Get the trial balance

Trial balance for a period: opening, movement and closing balance of every account. GET /trial_balance.

Input parameters:

- `compare_type` (string): Period shortcut (day = today). Use custom with start_date and end_date.
- `end_date` (string): End of the period, yyyy-mm-dd (default today).
- `start_date` (string): Start of the period, yyyy-mm-dd (default today).

### `jurnal_get_cash_flow` (~90 tokens)

Get the cash flow report

Cash flow statement for a period (operating, investing, financing). GET /cash_flow.

Input parameters:

- `compare_type` (string): Period shortcut (day = today). Use custom with start_date and end_date.
- `end_date` (string): End of the period, yyyy-mm-dd (default today).
- `start_date` (string): Start of the period, yyyy-mm-dd (default today).

### `jurnal_get_general_ledger` (~113 tokens)

Get the general ledger

General ledger for a period, optionally limited to some accounts (ids from jurnal_list_accounts). GET /general_ledger.

Input parameters:

- `account_ids` (array): Only these accounts (ids from jurnal_list_accounts).
- `compare_type` (string): Period shortcut (day = today). Use custom with start_date and end_date.
- `end_date` (string): End of the period, yyyy-mm-dd (default today).
- `start_date` (string): Start of the period, yyyy-mm-dd (default today).

### `jurnal_get_aged_receivables` (~38 tokens)

Get aged receivables

Aged receivables: what customers owe, bucketed by how overdue it is. GET /aged_receivables.

### `jurnal_get_aged_payables` (~37 tokens)

Get aged payables

Aged payables: what is owed to vendors, bucketed by how overdue it is. GET /aged_payables.

### `jurnal_get_executive_summary` (~41 tokens)

Get the executive summary

Executive summary: key figures (cash, revenue, profit, receivables, payables) for the company. GET /executive_summary.

### `jurnal_create_customer` (~149 tokens)

Create a customer

Create a new customer contact in Jurnal. This writes to the user's books (a customer can be archived or deleted later in Jurnal). Only display_name is required. POST /customers.

Input parameters:

- `address` (string)
- `associate_company` (string): Company the contact belongs to.
- `billing_address` (string)
- `display_name` (string, required): Display name shown in Jurnal (required).
- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `mobile` (string)
- `other_detail` (string)
- `phone` (string)
- `tax_no` (string): Tax number (NPWP).

### `jurnal_create_vendor` (~152 tokens)

Create a vendor

Create a new vendor (supplier) contact in Jurnal. This writes to the user's books (a vendor can be archived or deleted later in Jurnal). Only display_name is required. POST /vendors.

Input parameters:

- `address` (string)
- `associate_company` (string): Company the contact belongs to.
- `billing_address` (string)
- `display_name` (string, required): Display name shown in Jurnal (required).
- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `mobile` (string)
- `other_detail` (string)
- `phone` (string)
- `tax_no` (string): Tax number (NPWP).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 65

## Common questions

### What is the Mekari Jurnal MCP by usefulapi server?

Mekari Jurnal MCP by usefulapi is listed in the public MCP registry as io.usefulapi/jurnal. MCP server for Mekari Jurnal, company accounting, sales, purchases and customer/vendor creation. This page covers its hosted endpoint (https://jurnal.usefulapi.io/mcp).

### Is the Mekari Jurnal MCP by usefulapi server safe to use?

Mekari Jurnal MCP by usefulapi scores 18 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 Mekari Jurnal MCP by usefulapi server expose?

Mekari Jurnal MCP by usefulapi exposes 38 tools: jurnal_get_current_user, jurnal_list_companies, jurnal_list_customers, jurnal_get_customer, jurnal_list_vendors, and 33 more. Their descriptions and schemas cost roughly 2,979 tokens of context every time the server is loaded.

### Does the Mekari Jurnal MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Mekari Jurnal MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Mekari Jurnal MCP by usefulapi server still maintained?

Mekari Jurnal MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Mekari Jurnal MCP by usefulapi server?

VerifyMCP ran 4 checks on Mekari Jurnal MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Mekari Jurnal MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://jurnal.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/jurnal/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-jurnal/jurnal