Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SmartAccounts MCP by usefulapi

REMOTE · SMARTACCOUNTS.USEFULAPI.IO

Read SmartAccounts clients, vendors, invoices, payments, ledger, accounts; create and book records.

64 Trust /100

Last scanned (3 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability76
  • 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 3662 tokens (~203/item across 18 items; 18 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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 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
Changelog

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.

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 14 Oct 26 +3
    • 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 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 59

    First indexed and scored.

Diagnostics

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://smartaccounts.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 smartaccounts.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://smartaccounts.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://smartaccounts.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://smartaccounts.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://smartaccounts.usefulapi.io/mcp
Authorisation server https://smartaccounts.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://smartaccounts.usefulapi.io/mcp Redirected 302 https://usefulapi.io/smartaccounts/
http (plaintext) http://smartaccounts.usefulapi.io/mcp Inconclusive 302 http://smartaccounts.usefulapi.io/mcp
MCP tools · 18 exposed · ~3,461 tokens

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 →

Tool Tokens
smartaccounts_create_client ~285

Add a new client (purchasesales/clients:add). Search first with smartaccounts_list_clients so a client is not created twice. Returns clientId and the generated referenceNumber. This creates a real accounting record in the company's books. This server cannot edit or delete it; correct it in SmartAccounts. It never retries: if a reply is unclear, look in SmartAccounts before calling again. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
address1string––
address2string––
bank_accountstring–Bank account number (IBAN).
citystring––
commentstring–Internal comment.
countrystring–2-letter ISO country code, for example EE.
countystring––
emailstring–Contact email.
invoice_due_daysinteger–Default invoice due date in days.
namestringyesClient name.
phonestring–Contact phone.
postal_codestring––
reg_codestring–Company registry code.
vat_numberstring–VAT registration number.
vat_pcstringyesThe client's default VAT code (the vatPc of smartaccounts_list_vat_rates), for example 20.

No output schema declared.

No examples provided.

smartaccounts_create_ledger_entry ~176

Post a manual general ledger entry (journal entry, general/entries:add) in EUR. Debits must equal credits. Account codes come from smartaccounts_list_accounts. Fails if the period is locked. Returns id, number and amount. This creates a real accounting record in the company's books. This server cannot edit or delete it; correct it in SmartAccounts. It never retries: if a reply is unclear, look in SmartAccounts before calling again. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
commentstring–Internal comment.
datestringyesEntry date, yyyy-mm-dd.
documentstring–Document number text.
rowsarrayyesEntry rows; total debit must equal total credit.

No output schema declared.

No examples provided.

smartaccounts_create_payment ~312

Record a bank or cash payment against one or more invoices (purchasesales/payments:add): a client paying a sales invoice, or a payment to a vendor for a purchase invoice. Use smartaccounts_list_bank_accounts or _list_cash_accounts for account_name, and the invoice ids from the invoice lists. The currency must match the account's currency. Returns paymentId, number and amount. This creates a real accounting record in the company's books. This server cannot edit or delete it; correct it in SmartAccounts. It never retries: if a reply is unclear, look in SmartAccounts before calling again. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
account_namestringyesThe name of the bank or cash account.
account_typestringyesBANK or CASH.
commentstring–Internal comment.
currencystringyesCurrency code, for example EUR; must match the account's currency.
datestringyesPayment date, yyyy-mm-dd.
documentstring–Document number text.
exchange_ratenumber–Exchange rate; only for a currency without an ECB rate.
partner_idstringyesThe client id (partner_type CLIENT) or vendor id (VENDOR).
partner_typestringyesCLIENT = money received from a client; VENDOR = money paid to a vendor.
rowsarrayyesThe invoices this payment settles.

No output schema declared.

No examples provided.

smartaccounts_create_sales_invoice ~317

Post a new sales (client) invoice (purchasesales/clientinvoices:add). The invoice number is generated by SmartAccounts, totals and VAT are calculated from the rows, and the invoice is booked to the ledger at once (it is not a draft). The client must exist (smartaccounts_list_clients); each row's code must be an article code (smartaccounts_list_articles) and vat_pc a VAT code (smartaccounts_list_vat_rates). Fails if the period is locked. Returns invoiceId, number and the totals. This creates a real accounting record in the company's books. This server cannot edit or delete it; correct it in SmartAccounts. It never retries: if a reply is unclear, look in SmartAccounts before calling again. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
client_idstringyesThe client id (from smartaccounts_list_clients).
commentstring–Internal comment.
currencystring–Currency code (default EUR).
datestringyesInvoice date, yyyy-mm-dd.
due_datestring–Due date, yyyy-mm-dd (default from the client's settings).
exchange_ratenumber–Exchange rate; only for a currency without an ECB rate.
invoice_notestring–Additional text printed on the invoice PDF.
reference_numberstring–Reference number for payment orders (default generated).
rowsarrayyesInvoice rows.

No output schema declared.

No examples provided.

smartaccounts_get_client_balance ~113

The outstanding balance of one client (purchasesales/clients:getbalance), optionally on a past date and with the open documents. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
balance_datestring–Balance on this date, yyyy-mm-dd (default today).
fetch_detailsboolean–Include the documents that make up the balance.
idstringyesThe client id (from smartaccounts_list_clients).

No output schema declared.

No examples provided.

smartaccounts_get_vendor_balance ~114

The outstanding balance owed to one vendor (purchasesales/vendors:getbalance), optionally on a past date and with the open documents. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
balance_datestring–Balance on this date, yyyy-mm-dd (default today).
fetch_detailsboolean–Include the documents that make up the balance.
idstringyesThe vendor id (from smartaccounts_list_vendors).

No output schema declared.

No examples provided.

smartaccounts_list_accounts ~77

The chart of accounts: code, type (ASSET, LIABILITY, INCOME, EXPENSE), Estonian and English description. Use the codes in ledger entries. (settings/accounts:get). Not paged. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

smartaccounts_list_articles ~198

Products, services and warehouse items (purchasesales/articles:get): code, description, type, unit, VAT code, sales and purchase prices, accounts. Search by code or name, or by modification time. Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
codestring–A specific article code.
modified_fromstring–Only articles modified after, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
modified_tostring–Only articles modified before, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).
search_stringstring–Filter by article code or name.

No output schema declared.

No examples provided.

smartaccounts_list_bank_accounts ~72

The company's bank accounts: name (used as accountName in payments), ledger account, currency, IBAN, SWIFT. (settings/bankaccounts:get). Not paged. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

smartaccounts_list_cash_accounts ~66

The company's cash registers: name (used as accountName in payments), ledger account, currency. (settings/cashaccounts:get). Not paged. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

smartaccounts_list_clients ~231

Customers of the company (purchasesales/clients:get): id, name, regCode, vatNumber, bank account, due days, discount, VAT code. Filter by name or registry code, by id, or by modification time. Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
fetch_addressesboolean–Include addresses.
fetch_contactsboolean–Include contacts (emails, phones).
idstring–A specific client id.
modified_fromstring–Only clients modified after, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
modified_tostring–Only clients modified until, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
name_or_reg_codestring–Name or registry code to search for.
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).

No output schema declared.

No examples provided.

smartaccounts_list_ledger_entries ~273

General ledger entries of every type (general/entries:get): manual entries, invoices, payments, VAT returns, depreciation. Filter by date, type, text or payment status. Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
date_fromstring–Entries dated from, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_tostring–Entries dated to, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_typestring–Which date the range filters: entry date (default) or added/modified time.
doc_typestring–Only entries of this type (LEDGER_ENTRY = manual ledger entry).
fetch_rowsboolean–Include the entry rows (account, debit, credit).
filter_descriptionstring–Filter by document number or row description.
idstring–A specific entry id.
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).
payment_statusstring–unpaid or overdue invoices only. Omit for all.

No output schema declared.

No examples provided.

smartaccounts_list_payment_methods ~57

Payment methods: name, ledger account, whether cash. (settings/paymentmethods:get). Not paged. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

smartaccounts_list_payments ~284

Bank and cash payments from clients and to vendors (purchasesales/payments:get): date, partner, account, currency, amount, optionally the rows (which invoices were paid). Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
account_namestring–Filter by the bank or cash account name.
account_typestring–Only bank or only cash payments.
date_fromstring–Payments dated from, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_tostring–Payments dated to, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_typestring–Which date the range filters: payment date (default) or modification time.
fetch_rowsboolean–Include the payment rows.
idstring–A specific payment id.
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).
partner_idstring–Filter by client or vendor id.
partner_namestring–Filter by client or vendor name.
partner_typestring–Only client payments or only vendor payments.

No output schema declared.

No examples provided.

smartaccounts_list_purchase_invoices ~292

Purchase (vendor) invoices (purchasesales/vendorinvoices:get): number, vendor, dates, amounts, VAT, outstanding amount, optionally the rows. Filter by date, vendor, number or payment status (unpaid, overdue). Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
date_fromstring–Invoices dated from, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_tostring–Invoices dated to, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_typestring–Which date the range filters: invoice date (default), entry date, due date or modification time.
fetch_rowsboolean–Include the invoice rows.
idstring–A specific invoice id.
invoice_numberstring–Filter by invoice number.
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).
payment_statusstring–unpaid = not fully paid; overdue = unpaid and past due. Omit for all.
vendor_idstring–Only this vendor's invoices.
vendor_namestring–Filter by vendor name.

No output schema declared.

No examples provided.

smartaccounts_list_sales_invoices ~291

Sales (client) invoices (purchasesales/clientinvoices:get): number, client, dates, amounts, VAT, outstanding amount, optionally the rows. Filter by date, client, number or payment status (unpaid, overdue). Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
client_idstring–Only this client's invoices.
client_namestring–Filter by client name.
date_fromstring–Invoices dated from, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_tostring–Invoices dated to, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
date_typestring–Which date the range filters: invoice date (default), entry date, due date or modification time.
fetch_rowsboolean–Include the invoice rows.
idstring–A specific invoice id.
invoice_numberstring–Filter by invoice number.
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).
payment_statusstring–unpaid = not fully paid; overdue = unpaid and past due. Omit for all.

No output schema declared.

No examples provided.

smartaccounts_list_vat_rates ~77

VAT codes: vatPc code, percentage, descriptions, whether active for sales or purchases, accounts. Use vatPc in client and invoice rows. (settings/vatpcs:get). Not paged. The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

smartaccounts_list_vendors ~226

Suppliers of the company (purchasesales/vendors:get): id, name, regCode, vatNumber, bank account, VAT code. Filter by name or registry code, by id, or by modification time. Paged (100 per page). The vendor limit is 60 requests per minute and 1000 per 24 hours; every call here is one request.

NameTypeReqDescription
fetch_addressesboolean–Include addresses.
fetch_contactsboolean–Include contacts (emails, phones).
idstring–A specific vendor id.
modified_fromstring–Only vendors modified after, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
modified_tostring–Only vendors modified until, yyyy-mm-dd (or yyyy-mm-ddTHH:mm:ss, Estonian time).
name_or_reg_codestring–Name or registry code to search for.
pageinteger–Page number, 1-based (default 1). Use next_page_number from the previous reply (100 objects per page).

No output schema declared.

No examples provided.

Install

How do I install the SmartAccounts MCP by usefulapi server?

SmartAccounts MCP by usefulapi is a hosted endpoint at https://smartaccounts.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 · smartaccounts.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-smartaccounts 'https://smartaccounts.usefulapi.io/mcp'
Common questions

What is the SmartAccounts MCP by usefulapi server?

SmartAccounts MCP by usefulapi is listed in the public MCP registry as io.usefulapi/smartaccounts. Read SmartAccounts clients, vendors, invoices, payments, ledger, accounts; create and book records. This page covers its hosted endpoint (https://smartaccounts.usefulapi.io/mcp).

Is the SmartAccounts MCP by usefulapi server safe to use?

SmartAccounts 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 SmartAccounts MCP by usefulapi server expose?

SmartAccounts MCP by usefulapi exposes 18 tools: smartaccounts_list_clients, smartaccounts_get_client_balance, smartaccounts_list_vendors, smartaccounts_get_vendor_balance, smartaccounts_list_articles, and 13 more. Their descriptions and schemas cost roughly 3,461 tokens of context every time the server is loaded.

Does the SmartAccounts MCP by usefulapi server require authentication?

Yes. SmartAccounts 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 SmartAccounts MCP by usefulapi server still maintained?

SmartAccounts 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.