Mekari Jurnal MCP by usefulapi
REMOTE · JURNAL.USEFULAPI.IO
MCP server for Mekari Jurnal — company accounting, sales, purchases and customer/vendor creation.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 65
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 5 Nov 2026 · Probed https://jurnal.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jurnal.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jurnal.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/jurnal/ |
| http (plaintext) | http://jurnal.usefulapi.io/mcp | Inconclusive | 302 | http://jurnal.usefulapi.io/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jurnal_create_customer Create a customer ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| associate_company | string | – | Company the contact belongs to. |
| billing_address | string | – | – |
| display_name | string | yes | Display name shown in Jurnal (required). |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| mobile | string | – | – |
| other_detail | string | – | – |
| phone | string | – | – |
| tax_no | string | – | Tax number (NPWP). |
No output schema declared.
No examples provided.
jurnal_create_vendor Create a vendor ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| associate_company | string | – | Company the contact belongs to. |
| billing_address | string | – | – |
| display_name | string | yes | Display name shown in Jurnal (required). |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| mobile | string | – | – |
| other_detail | string | – | – |
| phone | string | – | – |
| tax_no | string | – | Tax number (NPWP). |
No output schema declared.
No examples provided.
jurnal_get_account Get an account ~33
One chart-of-accounts entry by id. GET /accounts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Account id. |
No output schema declared.
No examples provided.
jurnal_get_aged_payables Get aged payables ~37
Aged payables: what is owed to vendors, bucketed by how overdue it is. GET /aged_payables.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_get_aged_receivables Get aged receivables ~38
Aged receivables: what customers owe, bucketed by how overdue it is. GET /aged_receivables.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_get_balance_sheet Get the balance sheet ~56
Balance sheet as of end_date (yyyy-mm-dd, default today): assets, liabilities and equity by account. GET /balance_sheet.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | End of the period, yyyy-mm-dd (default today). |
No output schema declared.
No examples provided.
jurnal_get_cash_flow Get the cash flow report ~90
Cash flow statement for a period (operating, investing, financing). GET /cash_flow.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_get_current_user Get the current user ~43
The Jurnal user the credential acts as: id, name, email, status, owner flag and roles. GET /public/jurnal/api/v1/users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_get_customer Get a customer ~35
One customer by id (from jurnal_list_customers). GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Customer id. |
No output schema declared.
No examples provided.
jurnal_get_executive_summary Get the executive summary ~41
Executive summary: key figures (cash, revenue, profit, receivables, payables) for the company. GET /executive_summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_get_expense Get an expense ~31
One expense with its lines. GET /expenses/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Expense id. |
No output schema declared.
No examples provided.
jurnal_get_general_ledger Get the general ledger ~113
General ledger for a period, optionally limited to some accounts (ids from jurnal_list_accounts). GET /general_ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_get_journal_entry Get a journal entry ~38
One journal entry with its debit and credit lines. GET /journal_entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Journal entry id. |
No output schema declared.
No examples provided.
jurnal_get_product Get a product ~34
One product by id (from jurnal_list_products). GET /products/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Product id. |
No output schema declared.
No examples provided.
jurnal_get_profit_and_loss Get the profit and loss report ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_get_purchase_invoice Get a purchase invoice ~39
One purchase invoice with its lines, taxes and payments. GET /purchase_invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Purchase invoice id. |
No output schema declared.
No examples provided.
jurnal_get_sales_invoice Get a sales invoice ~39
One sales invoice with its lines, taxes and payments. GET /sales_invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Sales invoice id. |
No output schema declared.
No examples provided.
jurnal_get_trial_balance Get the trial balance ~92
Trial balance for a period: opening, movement and closing balance of every account. GET /trial_balance.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_get_vendor Get a vendor ~35
One vendor by id (from jurnal_list_vendors). GET /vendors/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Vendor id. |
No output schema declared.
No examples provided.
jurnal_list_accounts List chart of accounts ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_archive | boolean | – | false = only active (non-archived) records; Jurnal includes archived ones by default. |
No output schema declared.
No examples provided.
jurnal_list_companies List companies ~93
The Jurnal company (or companies) the credential belongs to: id, name, industry, address, tax number, currency settings and feature flags. GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_customers List customers ~144
Customers with display name, addresses, email, phone, tax number and receivable balance. Paged. GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jurnal_list_expenses List expenses ~116
Expenses: number, date, beneficiary, status, total and balance due. Paged. GET /expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jurnal_list_journal_entries List journal entries ~75
Manual journal entries (general journal). Paged. GET /journal_entries.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_payment_methods List payment methods ~29
Payment methods (cash, transfer and so on). Not paged. GET /payment_methods.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_list_product_categories List product categories ~22
Product categories. Not paged. GET /product_categories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_list_products List products ~165
Products and services: code, name, buy and sell prices, stock quantity, category, units, active flag. Paged. GET /products.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jurnal_list_purchase_invoices List purchase invoices ~198
Purchase invoices (bills from vendors): number, vendor, dates, status, total and balance due. Paged. GET /purchase_invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_purchase_orders List purchase orders ~78
Purchase orders with vendor, dates, status and totals. Paged. GET /purchase_orders.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_purchase_payments List purchase payments ~77
Payments made to vendors against purchase invoices. Paged. GET /purchase_payments.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_receive_payments List received payments ~76
Customer payments received against sales invoices. Paged. GET /receive_payments.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_sales_invoices List sales invoices ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jurnal_list_sales_orders List sales orders ~78
Sales orders with customer, dates, status and totals. Paged. GET /sales_orders.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_sales_quotes List sales quotes ~81
Sales quotes (offers) with customer, dates, status and totals. Paged. GET /sales_quotes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_tags List transaction tags ~20
Transaction tags. Not paged. GET /tags.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jurnal_list_taxes List taxes ~81
The company's tax rates (PPN, PPh and so on). Paged. GET /taxes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jurnal_list_vendors List vendors ~144
Vendors (suppliers) with display name, addresses, email, phone, tax number and payable balance. Paged. GET /vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jurnal_list_warehouses List warehouses ~79
Warehouses (needs a Jurnal plan with inventory). Paged. GET /warehouses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
remote · jurnal.usefulapi.io
claude mcp add --transport http io-usefulapi-jurnal 'https://jurnal.usefulapi.io/mcp'
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.