# Merit Aktiva MCP by usefulapi (remote · merit-aktiva.usefulapi.io)

Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://merit-aktiva.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## 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-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3530 tokens (~135/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Merit Aktiva MCP by usefulapi server?

Merit Aktiva MCP by usefulapi is a hosted endpoint at https://merit-aktiva.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-merit-aktiva 'https://merit-aktiva.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-merit-aktiva": {
      "type": "http",
      "url": "https://merit-aktiva.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-10-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (26)

### `merit_list_sales_invoices` (~187 tokens)

List sales invoices

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.

Input parameters:

- `date_type`: Which date the period filters: 0 = document date (default), 1 = date of last change.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `period_end` (string, required): Last day of the period, yyyy-mm-dd (max 3 months after the start).
- `period_start` (string, required): First day of the period, yyyy-mm-dd.
- `unpaid_only` (boolean): true = only unpaid invoices.

### `merit_search_sales_invoices` (~108 tokens)

Find sales invoices by number or customer

Find sales invoices by invoice number, customer name or customer id (give at least one). POST /api/v2/getinvoices2.

Input parameters:

- `customer_id` (string): Customer id (from merit_list_customers).
- `customer_name` (string): Customer name.
- `invoice_no` (string): Invoice number.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_get_sales_invoice` (~67 tokens)

Get a sales invoice

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.

Input parameters:

- `id` (string, required): Invoice id (SIHId from merit_list_sales_invoices).

### `merit_list_purchase_invoices` (~180 tokens)

List purchase 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.

Input parameters:

- `date_type`: Which date the period filters: 0 = document date (default), 1 = date of last change.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `period_end` (string, required): Last day of the period, yyyy-mm-dd (max 3 months after the start).
- `period_start` (string, required): First day of the period, yyyy-mm-dd.
- `unpaid_only` (boolean): true = only unpaid bills.

### `merit_get_purchase_invoice` (~58 tokens)

Get a purchase invoice

One purchase invoice in full: header, lines, payments. The attachment is never requested. POST /api/v2/getpurchorder.

Input parameters:

- `id` (string, required): Purchase invoice id (PIHId from merit_list_purchase_invoices).

### `merit_list_customers` (~157 tokens)

Search customers

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.

Input parameters:

- `changed_since` (string): Only customers created or changed on or after this date.
- `id` (string): Customer id.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `name` (string): Part of the customer name.
- `reg_no` (string): Registry number, exact.
- `vat_reg_no` (string): VAT number, exact.

### `merit_list_vendors` (~161 tokens)

Search vendors

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.

Input parameters:

- `changed_since` (string): Only vendors created or changed on or after this date.
- `id` (string): Vendor id.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `name` (string): Part of the vendor name.
- `reg_no` (string): Registry number, exact.
- `vat_reg_no` (string): VAT number, exact.

### `merit_list_items` (~164 tokens)

List items (articles)

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.

Input parameters:

- `code` (string): Part of the item code.
- `description` (string): Part of the item description.
- `id` (string): Item id.
- `location_code` (string): Warehouse code: adds goods on hand quantity and cost.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `type`: 1 = stock item, 2 = service, 3 = item.

### `merit_list_accounts` (~68 tokens)

List the chart of accounts

The general ledger chart of accounts (code, names, VAT, parent flag, active flag). GET /api/v2/accounts.

Input parameters:

- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_list_taxes` (~80 tokens)

List VAT rates

All VAT rates of the company (TaxId, code, name, percent, active flag). The TaxId is what invoice rows refer to. GET /api/v2/taxes.

Input parameters:

- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_list_departments` (~61 tokens)

List departments

Departments (code, name, active flag). GET /api/v2/departments.

Input parameters:

- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_list_banks` (~78 tokens)

List bank accounts

The company's bank and cash accounts (BankId, name, IBAN, currency, ledger account). BankId feeds the payment tools. GET /api/v2/banks.

Input parameters:

- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_list_financial_years` (~36 tokens)

List financial years

Accounting periods (financial years) with start, end and active flag. POST /api/v2/getaccperiods.

### `merit_list_dimensions` (~92 tokens)

List dimensions

Accounting dimensions and their values (DimId, name, value code, expiry). all_values = true also lists expired values. POST /api/v2/getdimensions.

Input parameters:

- `all_values` (boolean): true = include expired dimension values (default false).
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_list_payment_types` (~96 tokens)

List payment types

Payment methods and sources (cash, banks, reporting entities, ledger accounts) usable for purchases, expense reports or sales. POST /api/v2/getpaymenttypes.

Input parameters:

- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `type`: 1 = purchases, 2 = expense reports, 3 = sales.

### `merit_list_payments` (~199 tokens)

List payments

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.

Input parameters:

- `bank_id` (string): Only this bank account (BankId from merit_list_banks).
- `date_type`: Which date the period filters: 0 = document date (default), 1 = date of last change.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `payment_type` (integer): Merit payment type filter (see merit_list_payment_types).
- `period_end` (string, required): Last day of the period, yyyy-mm-dd (max 3 months after the start).
- `period_start` (string, required): First day of the period, yyyy-mm-dd.

### `merit_list_bank_payments` (~188 tokens)

List income or expense payments of a bank account

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.

Input parameters:

- `bank_id` (string, required): BankId from merit_list_banks.
- `direction` (string, required): income = payments received, expense = payments made.
- `doc_date_from` (string, required): Document date from, yyyy-mm-dd.
- `doc_date_to` (string, required): Document date to, yyyy-mm-dd (max 3 months after doc_date_from).
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.

### `merit_list_gl_batches` (~172 tokens)

List general ledger transactions

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.

Input parameters:

- `date_type`: Which date the period filters: 0 = document date (default), 1 = date of last change.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `period_end` (string, required): Last day of the period, yyyy-mm-dd (max 3 months after the start).
- `period_start` (string, required): First day of the period, yyyy-mm-dd.

### `merit_get_gl_batch` (~65 tokens)

Get a general ledger transaction

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.

Input parameters:

- `id` (string, required): Batch id (GLBId from merit_list_gl_batches).

### `merit_customer_debts_report` (~180 tokens)

Customer debts report

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.

Input parameters:

- `as_of` (string): Debt as of this date (default today).
- `customer_id` (string): Customer id.
- `customer_name` (string): Customer name; an empty string or omitting it with no customer_id selects ALL customers.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `over_due_days` (integer): Only documents overdue by at least this many days.

### `merit_customer_payments_report` (~132 tokens)

Customer payments report

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.

Input parameters:

- `currency_code` (string): Currency, e.g. EUR.
- `customer_id` (string): Customer id.
- `customer_name` (string): Customer name.
- `period_end` (string, required): Period end, yyyy-mm-dd.
- `period_start` (string, required): Period start, yyyy-mm-dd.

### `merit_income_statement` (~108 tokens)

Income statement (profit and loss)

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.

Input parameters:

- `department_code` (string): Only this department (code from merit_list_departments).
- `end_date` (string, required): Last day of the newest month, yyyy-mm-dd.
- `per_count` (integer): Number of monthly periods, counting back from end_date (default 1).

### `merit_balance_sheet` (~84 tokens)

Balance sheet

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.

Input parameters:

- `end_date` (string, required): Balance date, yyyy-mm-dd.
- `per_count` (integer): Number of monthly periods, counting back from end_date (default 1).

### `merit_sales_report` (~133 tokens)

Sales report

Sales totals for a period, grouped by invoice, customer, item or country. POST /api/v2/getsalesrep.

Input parameters:

- `end_date` (string, required): Period end, yyyy-mm-dd.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `report_type` (required): 1 = by invoices, 2 = by customers, 3 = by items, 4 = by countries, 5 = by countries (general).
- `start_date` (string, required): Period start, yyyy-mm-dd.

### `merit_purchase_report` (~127 tokens)

Purchase report

Purchase totals for a period, grouped by invoice, vendor, item or fixed asset. POST /api/v2/getpurchrep.

Input parameters:

- `end_date` (string, required): Period end, yyyy-mm-dd.
- `max_results` (integer): Show at most this many rows (default 100, max 1000); the reply says how many there are in total.
- `report_type` (required): 1 = by invoices, 2 = by vendors, 3 = by items, 4 = by fixed assets.
- `start_date` (string, required): Period start, yyyy-mm-dd.

### `merit_create_customer` (~343 tokens)

Create a customer

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.

Input parameters:

- `address` (string): Street address.
- `bank_account` (string): Customer bank account (IBAN).
- `city` (string): City.
- `contact` (string): Contact person.
- `country_code` (string, required): 2-letter ISO country code, e.g. EE, PL.
- `county` (string): County.
- `currency_code` (string): Default currency, e.g. EUR.
- `email` (string): E-mail address (stored only; Merit sends nothing).
- `home_page` (string): Web page.
- `name` (string, required): Customer name (unique in the company).
- `not_td_customer` (boolean, required): true for private persons and foreign companies (Estonia), true for private persons (Poland); false for a local company.
- `payment_deadline_days` (integer): Payment term in days (default from company settings).
- `phone_no` (string): Phone number.
- `postal_code` (string): Postal code.
- `reg_no` (string): Registry or personal id code.
- `sales_invoice_language` (string): Invoice language for this customer (Estonia: ET, EN, RU, FI; Poland: PL, EN, RU).
- `vat_reg_no` (string): VAT number.

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60

## Common questions

### What is the Merit Aktiva MCP by usefulapi server?

Merit Aktiva MCP by usefulapi is listed in the public MCP registry as io.usefulapi/merit-aktiva. Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer. This page covers its hosted endpoint (https://merit-aktiva.usefulapi.io/mcp).

### Is the Merit Aktiva MCP by usefulapi server safe to use?

Merit Aktiva MCP by usefulapi scores 64 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 Merit Aktiva MCP by usefulapi server expose?

Merit Aktiva MCP by usefulapi exposes 26 tools: merit_list_sales_invoices, merit_search_sales_invoices, merit_get_sales_invoice, merit_list_purchase_invoices, merit_get_purchase_invoice, and 21 more. Their descriptions and schemas cost roughly 3,324 tokens of context every time the server is loaded.

### Does the Merit Aktiva MCP by usefulapi server require authentication?

Yes. Merit Aktiva MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Merit Aktiva MCP by usefulapi server still maintained?

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

## Links

- Remote endpoint: https://merit-aktiva.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/merit-aktiva/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-merit-aktiva/merit-aktiva.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-merit-aktiva/merit-aktiva.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-merit-aktiva/merit-aktiva