Alpaca Trading API integration for Model Context Protocol (MCP)
Mekari Jurnal MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
MCP server for Mekari Jurnal — company accounting, sales, purchases and customer/vendor creation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mekari-jurnal-mcp-by-usefulapi https://jurnal.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# jurnal_get_current_user, jurnal_list_companies, jurnal_list_customers and 35 more
Mekari Jurnal MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mekari-jurnal-mcp-by-usefulapi https://jurnal.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
38 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The Jurnal user the credential acts as: id, name, email, status, owner flag and roles. GET /public/jurnal/api/v1/users/me.
No parameter schema on file.
The Jurnal company (or companies) the credential belongs to: id, name, industry, address, tax number, currency settings and feature flags. GET /companies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Customers with display name, addresses, email, phone, tax number and receivable balance. Paged. GET /customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
| sort_key | string | no | Sort field: display_name, billing_address, email, phone, balance_customer. |
| sort_order | string | no | Sort direction. |
| include_archive | boolean | no | false = only active (non-archived) records; Jurnal includes archived ones by default. |
One customer by id (from jurnal_list_customers). GET /customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Customer id. |
Vendors (suppliers) with display name, addresses, email, phone, tax number and payable balance. Paged. GET /vendors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
| sort_key | string | no | Sort field: display_name, billing_address, email, phone. |
| sort_order | string | no | Sort direction. |
| include_archive | boolean | no | false = only active (non-archived) records; Jurnal includes archived ones by default. |
One vendor by id (from jurnal_list_vendors). GET /vendors/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Vendor id. |
Products and services: code, name, buy and sell prices, stock quantity, category, units, active flag. Paged. GET /products.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
| sort_key | string | no | 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 | no | Sort direction. |
| include_archive | boolean | no | false = only active (non-archived) records; Jurnal includes archived ones by default. |
One product by id (from jurnal_list_products). GET /products/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Product id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_archive | boolean | no | false = only active (non-archived) records; Jurnal includes archived ones by default. |
One chart-of-accounts entry by id. GET /accounts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Account id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
| sort_key | string | no | Sort field: transaction_date, get_number, people_display_name, transaction_status_name, remaining, original_amount, created_at. |
| sort_order | string | no | Sort direction. |
One sales invoice with its lines, taxes and payments. GET /sales_invoices/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Sales invoice id. |
Sales orders with customer, dates, status and totals. Paged. GET /sales_orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Sales quotes (offers) with customer, dates, status and totals. Paged. GET /sales_quotes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Customer payments received against sales invoices. Paged. GET /receive_payments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Purchase invoices (bills from vendors): number, vendor, dates, status, total and balance due. Paged. GET /purchase_invoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
| sort_key | string | no | Sort field: transaction_date, created_at, transaction_no, people_display_name, due_date, transaction_status_name, remaining, original_amount. |
| sort_order | string | no | Sort direction. |
| start_date | string | no | Only transactions from this date, yyyy-mm-dd. Needs sort_key transaction_no or created_at (Jurnal applies the date range only with those). |
| end_date | string | no | Only transactions up to this date, yyyy-mm-dd. Needs sort_key transaction_no or created_at. |
One purchase invoice with its lines, taxes and payments. GET /purchase_invoices/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Purchase invoice id. |
Purchase orders with vendor, dates, status and totals. Paged. GET /purchase_orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Payments made to vendors against purchase invoices. Paged. GET /purchase_payments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Expenses: number, date, beneficiary, status, total and balance due. Paged. GET /expenses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
| sort_key | string | no | Sort field: transaction_date, transaction_no, transaction_status_name, remaining, original_amount. |
| sort_order | string | no | Sort direction. |
One expense with its lines. GET /expenses/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Expense id. |
Manual journal entries (general journal). Paged. GET /journal_entries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
One journal entry with its debit and credit lines. GET /journal_entries/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Journal entry id. |
The company's tax rates (PPN, PPh and so on). Paged. GET /taxes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Transaction tags. Not paged. GET /tags.
No parameter schema on file.
Payment methods (cash, transfer and so on). Not paged. GET /payment_methods.
No parameter schema on file.
Warehouses (needs a Jurnal plan with inventory). Paged. GET /warehouses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, 1-based (default 1). Use next_page from the previous reply. |
| page_size | integer | no | Results per page, 1-100 (Jurnal's default applies when omitted). |
Product categories. Not paged. GET /product_categories.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Start of the period, yyyy-mm-dd (default today). |
| end_date | string | no | End of the period, yyyy-mm-dd (default today). |
| compare_type | string | no | Period shortcut (day = today). Use custom with start_date and end_date. |
Balance sheet as of end_date (yyyy-mm-dd, default today): assets, liabilities and equity by account. GET /balance_sheet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| end_date | string | no | End of the period, yyyy-mm-dd (default today). |
Trial balance for a period: opening, movement and closing balance of every account. GET /trial_balance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Start of the period, yyyy-mm-dd (default today). |
| end_date | string | no | End of the period, yyyy-mm-dd (default today). |
| compare_type | string | no | Period shortcut (day = today). Use custom with start_date and end_date. |
Cash flow statement for a period (operating, investing, financing). GET /cash_flow.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Start of the period, yyyy-mm-dd (default today). |
| end_date | string | no | End of the period, yyyy-mm-dd (default today). |
| compare_type | string | no | Period shortcut (day = today). Use custom with start_date and end_date. |
General ledger for a period, optionally limited to some accounts (ids from jurnal_list_accounts). GET /general_ledger.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | Start of the period, yyyy-mm-dd (default today). |
| end_date | string | no | End of the period, yyyy-mm-dd (default today). |
| compare_type | string | no | Period shortcut (day = today). Use custom with start_date and end_date. |
| account_ids | array | no | Only these accounts (ids from jurnal_list_accounts). |
Aged receivables: what customers owe, bucketed by how overdue it is. GET /aged_receivables.
No parameter schema on file.
Aged payables: what is owed to vendors, bucketed by how overdue it is. GET /aged_payables.
No parameter schema on file.
Executive summary: key figures (cash, revenue, profit, receivables, payables) for the company. GET /executive_summary.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| display_name | string | yes | Display name shown in Jurnal (required). |
| first_name | string | no | — |
| last_name | string | no | — |
| associate_company | string | no | Company the contact belongs to. |
| string | no | — | |
| phone | string | no | — |
| mobile | string | no | — |
| billing_address | string | no | — |
| address | string | no | — |
| tax_no | string | no | Tax number (NPWP). |
| other_detail | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| display_name | string | yes | Display name shown in Jurnal (required). |
| first_name | string | no | — |
| last_name | string | no | — |
| associate_company | string | no | Company the contact belongs to. |
| string | no | — | |
| phone | string | no | — |
| mobile | string | no | — |
| billing_address | string | no | — |
| address | string | no | — |
| tax_no | string | no | Tax number (NPWP). |
| other_detail | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mekari Jurnal MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| jurnal_get_current_user | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_companies | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_customers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_customer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_vendors | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_vendor | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_products | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_product | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_accounts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_account | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_sales_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_sales_invoice | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_sales_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_sales_quotes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_receive_payments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_purchase_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_purchase_invoice | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_purchase_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_purchase_payments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_expenses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_expense | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_journal_entries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_journal_entry | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_taxes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_tags | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_payment_methods | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_warehouses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_list_product_categories | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_profit_and_loss | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_balance_sheet | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_trial_balance | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_cash_flow | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_general_ledger | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_aged_receivables | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_aged_payables | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_get_executive_summary | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_create_customer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| jurnal_create_vendor | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.6.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mekari Jurnal MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.