Alpaca Trading API integration for Model Context Protocol (MCP)
Merit Aktiva 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
Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http merit-aktiva-mcp-by-usefulapi https://merit-aktiva.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# merit_list_sales_invoices, merit_search_sales_invoices, merit_get_sales_invoice and 23 more
Merit Aktiva 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 merit-aktiva-mcp-by-usefulapi https://merit-aktiva.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.
26 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.
List sales invoices (header level: number, customer, dates, totals, paid flag) of a period. The period may span at most 3 months (Merit limit); for longer spans make several calls. Use merit_get_sales_invoice for the lines. POST /api/v2/getinvoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
| period_end | string | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| unpaid_only | boolean | no | true = only unpaid invoices. |
| date_type | no | Which date the period filters: 0 = document date (default), 1 = date of last change. | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Find sales invoices by invoice number, customer name or customer id (give at least one). POST /api/v2/getinvoices2.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_no | string | no | Invoice number. |
| customer_name | string | no | Customer name. |
| customer_id | string | no | Customer id (from merit_list_customers). |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
One sales invoice in full: header, lines (items, quantities, VAT, accounts), payments and dimension allocations. The PDF attachment is never requested. POST /api/v2/getinvoice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Invoice id (SIHId from merit_list_sales_invoices). |
List purchase invoices (vendor bills) of a period: bill number, vendor, dates, totals, paid flag. The period may span at most 3 months (Merit limit); for longer spans make several calls. POST /api/v2/getpurchorders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
| period_end | string | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| unpaid_only | boolean | no | true = only unpaid bills. |
| date_type | no | Which date the period filters: 0 = document date (default), 1 = date of last change. | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
One purchase invoice in full: header, lines, payments. The attachment is never requested. POST /api/v2/getpurchorder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Purchase invoice id (PIHId from merit_list_purchase_invoices). |
Search customers by name (partial match), registry number or VAT number (exact), id, or changed since a date. At least one filter is required: Merit cannot return the whole customer list in one reply. POST /api/v1/getcustomers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Part of the customer name. |
| reg_no | string | no | Registry number, exact. |
| vat_reg_no | string | no | VAT number, exact. |
| id | string | no | Customer id. |
| changed_since | string | no | Only customers created or changed on or after this date. |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Search vendors (suppliers) by name (partial match), registry number or VAT number (exact), id, or changed since a date. At least one filter is required: Merit cannot return the whole vendor list in one reply. POST /api/v1/getvendors.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Part of the vendor name. |
| reg_no | string | no | Registry number, exact. |
| vat_reg_no | string | no | VAT number, exact. |
| id | string | no | Vendor id. |
| changed_since | string | no | Only vendors created or changed on or after this date. |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
List items, services and stock articles with price, unit, VAT and accounts. Optional filters: code or description (partial), type, id. With location_code the reply adds stock quantity and cost of that warehouse. POST /api/v1/getitems.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | Item id. |
| code | string | no | Part of the item code. |
| description | string | no | Part of the item description. |
| type | no | 1 = stock item, 2 = service, 3 = item. | |
| location_code | string | no | Warehouse code: adds goods on hand quantity and cost. |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
The general ledger chart of accounts (code, names, VAT, parent flag, active flag). GET /api/v2/accounts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
All VAT rates of the company (TaxId, code, name, percent, active flag). The TaxId is what invoice rows refer to. GET /api/v2/taxes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Departments (code, name, active flag). GET /api/v2/departments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
The company's bank and cash accounts (BankId, name, IBAN, currency, ledger account). BankId feeds the payment tools. GET /api/v2/banks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Accounting periods (financial years) with start, end and active flag. POST /api/v2/getaccperiods.
No parameter schema on file.
Accounting dimensions and their values (DimId, name, value code, expiry). all_values = true also lists expired values. POST /api/v2/getdimensions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| all_values | boolean | no | true = include expired dimension values (default false). |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Payment methods and sources (cash, banks, reporting entities, ledger accounts) usable for purchases, expense reports or sales. POST /api/v2/getpaymenttypes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | no | 1 = purchases, 2 = expense reports, 3 = sales. | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
List payments (customer and vendor receipts and payouts) of a period, with the documents they paid. The period may span at most 3 months (Merit limit); for longer spans make several calls. POST /api/v2/getpayments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
| period_end | string | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| bank_id | string | no | Only this bank account (BankId from merit_list_banks). |
| payment_type | integer | no | Merit payment type filter (see merit_list_payment_types). |
| date_type | no | Which date the period filters: 0 = document date (default), 1 = date of last change. | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
List the income payments (money received) or expense payments (money paid out) booked on one bank account for a document-date period, with the documents each paid. The period may span at most 3 months (Merit limit); for longer spans make several calls. GET /api/v2/Banks/{bankId}/IncomePayments or /ExpensePayments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bank_id | string | yes | BankId from merit_list_banks. |
| direction | string | yes | income = payments received, expense = payments made. |
| doc_date_from | string | yes | Document date from, yyyy-mm-dd. |
| doc_date_to | string | yes | Document date to, yyyy-mm-dd (max 3 months after doc_date_from). |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
List general ledger batches (journal entries, also those created from invoices and payments) of a period: batch code, number, date, total. The period may span at most 3 months (Merit limit); for longer spans make several calls. POST /api/v1/getglbatches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
| period_end | string | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| date_type | no | Which date the period filters: 0 = document date (default), 1 = date of last change. | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
One general ledger batch with all its debit and credit lines (account, memo, department, tax, amounts). The attachment is never requested. POST /api/v1/getglbatch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Batch id (GLBId from merit_list_gl_batches). |
Open customer receivables: for each unpaid document the customer, date, due date, total, paid and unpaid amount. Give a customer name (empty string = all customers) or a customer id; over_due_days keeps only documents overdue by at least that many days. POST /api/v1/getcustdebtrep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_name | string | no | Customer name; an empty string or omitting it with no customer_id selects ALL customers. |
| customer_id | string | no | Customer id. |
| over_due_days | integer | no | Only documents overdue by at least this many days. |
| as_of | string | no | Debt as of this date (default today). |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Customer invoices with their unpaid amount and overdue flag for a period, for one customer (name or id). Only the FIRST page is returned: if has_more is true, narrow the period or the customer (the continuation endpoint is not supported). POST /api/v2/getcustpaymrep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_name | string | no | Customer name. |
| customer_id | string | no | Customer id. |
| period_start | string | yes | Period start, yyyy-mm-dd. |
| period_end | string | yes | Period end, yyyy-mm-dd. |
| currency_code | string | no | Currency, e.g. EUR. |
The profit and loss report: one row per report line, with balances for per_count months counting back from end_date (newest first). Optional department filter. POST /api/v1/getprofitrep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| end_date | string | yes | Last day of the newest month, yyyy-mm-dd. |
| per_count | integer | no | Number of monthly periods, counting back from end_date (default 1). |
| department_code | string | no | Only this department (code from merit_list_departments). |
The balance sheet: one row per report line (assets, liabilities, equity) with balances for per_count months counting back from end_date. POST /api/v1/getbalancerep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| end_date | string | yes | Balance date, yyyy-mm-dd. |
| per_count | integer | no | Number of monthly periods, counting back from end_date (default 1). |
Sales totals for a period, grouped by invoice, customer, item or country. POST /api/v2/getsalesrep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | Period start, yyyy-mm-dd. |
| end_date | string | yes | Period end, yyyy-mm-dd. |
| report_type | yes | 1 = by invoices, 2 = by customers, 3 = by items, 4 = by countries, 5 = by countries (general). | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
Purchase totals for a period, grouped by invoice, vendor, item or fixed asset. POST /api/v2/getpurchrep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | Period start, yyyy-mm-dd. |
| end_date | string | yes | Period end, yyyy-mm-dd. |
| report_type | yes | 1 = by invoices, 2 = by vendors, 3 = by items, 4 = by fixed assets. | |
| max_results | integer | no | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
WRITE: creates ONE new customer record in the Merit company (name must be unique; an existing customer is never overwritten, Merit answers with an error). Nothing is invoiced, sent or paid. In Estonia not_td_customer must be true for private persons and foreign companies; city is required in Estonia for a non-EE country. Returns the new customer id. POST /api/v2/sendcustomer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Customer name (unique in the company). |
| country_code | string | yes | 2-letter ISO country code, e.g. EE, PL. |
| not_td_customer | boolean | yes | true for private persons and foreign companies (Estonia), true for private persons (Poland); false for a local company. |
| reg_no | string | no | Registry or personal id code. |
| vat_reg_no | string | no | VAT number. |
| currency_code | string | no | Default currency, e.g. EUR. |
| payment_deadline_days | integer | no | Payment term in days (default from company settings). |
| address | string | no | Street address. |
| city | string | no | City. |
| county | string | no | County. |
| postal_code | string | no | Postal code. |
| phone_no | string | no | Phone number. |
| string | no | E-mail address (stored only; Merit sends nothing). | |
| home_page | string | no | Web page. |
| sales_invoice_language | string | no | Invoice language for this customer (Estonia: ET, EN, RU, FI; Poland: PL, EN, RU). |
| contact | string | no | Contact person. |
| bank_account | string | no | Customer bank account (IBAN). |
- 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 Merit Aktiva 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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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.0.0.
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 Merit Aktiva 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.