Merit Aktiva MCP by usefulapi
REMOTE · MERIT-AKTIVA.USEFULAPI.IO
Read Merit Aktiva invoices, customers, vendors, items, payments and reports; create a customer.
Available components
Last scanned (6 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
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 17 Oct 2026 · Probed https://merit-aktiva.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 merit-aktiva.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://merit-aktiva.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://merit-aktiva.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://merit-aktiva.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://merit-aktiva.usefulapi.io/mcp |
| Authorisation server | https://merit-aktiva.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://merit-aktiva.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/merit-aktiva/ |
| http (plaintext) | http://merit-aktiva.usefulapi.io/mcp | Inconclusive | 302 | http://merit-aktiva.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 →
merit_balance_sheet Balance sheet ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Balance date, yyyy-mm-dd. |
| per_count | integer | – | Number of monthly periods, counting back from end_date (default 1). |
No output schema declared.
No examples provided.
merit_create_customer Create a customer ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address. |
| bank_account | string | – | Customer bank account (IBAN). |
| city | string | – | City. |
| contact | string | – | Contact person. |
| country_code | string | yes | 2-letter ISO country code, e.g. EE, PL. |
| county | string | – | County. |
| currency_code | string | – | Default currency, e.g. EUR. |
| string | – | E-mail address (stored only; Merit sends nothing). | |
| home_page | string | – | Web page. |
| name | string | yes | Customer name (unique in the company). |
| not_td_customer | boolean | yes | 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. |
No output schema declared.
No examples provided.
merit_customer_debts_report Customer debts report ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
merit_customer_payments_report Customer payments report ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency_code | string | – | Currency, e.g. EUR. |
| customer_id | string | – | Customer id. |
| customer_name | string | – | Customer name. |
| period_end | string | yes | Period end, yyyy-mm-dd. |
| period_start | string | yes | Period start, yyyy-mm-dd. |
No output schema declared.
No examples provided.
merit_get_gl_batch Get a general ledger transaction ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Batch id (GLBId from merit_list_gl_batches). |
No output schema declared.
No examples provided.
merit_get_purchase_invoice Get a purchase invoice ~58
One purchase invoice in full: header, lines, payments. The attachment is never requested. POST /api/v2/getpurchorder.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Purchase invoice id (PIHId from merit_list_purchase_invoices). |
No output schema declared.
No examples provided.
merit_get_sales_invoice Get a sales invoice ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Invoice id (SIHId from merit_list_sales_invoices). |
No output schema declared.
No examples provided.
merit_income_statement Income statement (profit and loss) ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| department_code | string | – | Only this department (code from merit_list_departments). |
| end_date | string | yes | Last day of the newest month, yyyy-mm-dd. |
| per_count | integer | – | Number of monthly periods, counting back from end_date (default 1). |
No output schema declared.
No examples provided.
merit_list_accounts List the chart of accounts ~68
The general ledger chart of accounts (code, names, VAT, parent flag, active flag). GET /api/v2/accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
No output schema declared.
No examples provided.
merit_list_bank_payments List income or expense payments of a bank account ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
No output schema declared.
No examples provided.
merit_list_banks List bank accounts ~78
The company's bank and cash accounts (BankId, name, IBAN, currency, ledger account). BankId feeds the payment tools. GET /api/v2/banks.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
No output schema declared.
No examples provided.
merit_list_customers Search customers ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
merit_list_departments List departments ~61
Departments (code, name, active flag). GET /api/v2/departments.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
No output schema declared.
No examples provided.
merit_list_dimensions List dimensions ~92
Accounting dimensions and their values (DimId, name, value code, expiry). all_values = true also lists expired values. POST /api/v2/getdimensions.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
merit_list_financial_years List financial years ~36
Accounting periods (financial years) with start, end and active flag. POST /api/v2/getaccperiods.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
merit_list_gl_batches List general ledger transactions ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
No output schema declared.
No examples provided.
merit_list_items List items (articles) ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
merit_list_payment_types List payment types ~96
Payment methods and sources (cash, banks, reporting entities, ledger accounts) usable for purchases, expense reports or sales. POST /api/v2/getpaymenttypes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
merit_list_payments List payments ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
No output schema declared.
No examples provided.
merit_list_purchase_invoices List purchase invoices ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
| unpaid_only | boolean | – | true = only unpaid bills. |
No output schema declared.
No examples provided.
merit_list_sales_invoices List sales invoices ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Last day of the period, yyyy-mm-dd (max 3 months after the start). |
| period_start | string | yes | First day of the period, yyyy-mm-dd. |
| unpaid_only | boolean | – | true = only unpaid invoices. |
No output schema declared.
No examples provided.
merit_list_taxes List VAT rates ~80
All VAT rates of the company (TaxId, code, name, percent, active flag). The TaxId is what invoice rows refer to. GET /api/v2/taxes.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Show at most this many rows (default 100, max 1000); the reply says how many there are in total. |
No output schema declared.
No examples provided.
merit_list_vendors Search vendors ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
merit_purchase_report Purchase report ~127
Purchase totals for a period, grouped by invoice, vendor, item or fixed asset. POST /api/v2/getpurchrep.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | – | yes | 1 = by invoices, 2 = by vendors, 3 = by items, 4 = by fixed assets. |
| start_date | string | yes | Period start, yyyy-mm-dd. |
No output schema declared.
No examples provided.
merit_sales_report Sales report ~133
Sales totals for a period, grouped by invoice, customer, item or country. POST /api/v2/getsalesrep.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | 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 | – | yes | 1 = by invoices, 2 = by customers, 3 = by items, 4 = by countries, 5 = by countries (general). |
| start_date | string | yes | Period start, yyyy-mm-dd. |
No output schema declared.
No examples provided.
merit_search_sales_invoices Find sales invoices by number or customer ~108
Find sales invoices by invoice number, customer name or customer id (give at least one). POST /api/v2/getinvoices2.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · merit-aktiva.usefulapi.io
claude mcp add --transport http io-usefulapi-merit-aktiva 'https://merit-aktiva.usefulapi.io/mcp'
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.