SuperFaktura MCP by usefulapi
REMOTE · SUPERFAKTURA.USEFULAPI.IO
Read SuperFaktura invoices, clients, expenses, bank and stock; create clients, expenses and drafts.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 −56
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_client_with_a_contact_person” functional
- New prompt “check_bank_moves_and_cash_register_balances” functional
- New prompt “check_stock_items_and_their_movements” functional
- New prompt “find_invoices_that_are_still_unpaid” functional
- New prompt “record_an_expense_or_prepare_a_draft_invoice” functional
- New prompt “review_the_expenses_you_recorded” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.18.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.18.0 functional
- Server version: 1.16.2 → 1.17.0 functional
- 30 Oct 26 +1
- Server version: 1.16.1 → 1.16.2 functional
- Server version: 1.16.0 → 1.16.1 functional
- 29 Oct 26 0
- Server version: 1.15.0 → 1.16.0 functional
- Server version: 1.14.0 → 1.15.0 functional
- 28 Oct 26 +1
- Server version: 1.12.0 → 1.14.0 functional
- 27 Oct 26 0
- Server version: 1.11.0 → 1.12.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://superfaktura.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 superfaktura.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://superfaktura.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/superfaktura/ |
| http (plaintext) | http://superfaktura.usefulapi.io/mcp | Inconclusive | 302 | http://superfaktura.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 →
superfaktura_add_contact_person Add a contact person to a client ~95
WRITE: adds a contact person (name and e-mail, optional phone) to an existing client. Nothing is sent to that person. Not idempotent. POST /contact_people/add/api:1.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Existing client id. |
| string | yes | Contact person's e-mail (stored only). | |
| name | string | yes | Contact person's name. |
| phone | string | – | – |
No output schema declared.
No examples provided.
superfaktura_create_client Create a client ~236
WRITE: adds a new client to the SuperFaktura address book (only the name is required). Nothing is sent to the client. Not idempotent: calling twice creates two clients, so check superfaktura_list_clients first. POST /clients/create.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street and number. |
| city | string | – | – |
| comment | string | – | Internal note on the client. |
| country_id | integer | – | Country id (superfaktura_list_countries); Slovakia is 191. Defaults to the instance's country. |
| dic | string | – | Tax id (DIČ, Slovak). |
| string | – | Client e-mail (stored only; nothing is sent to it). | |
| iban | string | – | – |
| ic_dph | string | – | VAT id (IČ DPH in Slovakia, DIČ in the Czech Republic). |
| ico | string | – | Company id (IČO). |
| name | string | yes | Client name (company or person). |
| phone | string | – | – |
| swift | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
superfaktura_create_expense Record a received expense ~250
WRITE: records a received document (expense) with ONE total amount and VAT rate, e.g. a supplier invoice or a bill. It is created unpaid: no payment is recorded and nothing is sent. No attachments. Not idempotent: calling twice records two expenses. POST /expenses/add.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount WITHOUT VAT. |
| category_id | integer | – | Expense category id from superfaktura_list_expense_categories. |
| client_id | integer | – | Supplier (client) id from superfaktura_list_clients. |
| comment | string | – | Comment. |
| created | string | – | Issue date (default today). |
| currency | string | – | 3-letter currency code, e.g. EUR, CZK. |
| delivery | string | – | Delivery date (default today). |
| document_number | string | – | The supplier's document number. |
| due | string | – | Due date (default today). |
| name | string | yes | Expense name / what it is for. |
| type | string | – | Expense type (default invoice = received invoice). |
| variable | string | – | Variable symbol. |
| vat | number | – | VAT rate in percent (default 0). |
No output schema declared.
No examples provided.
superfaktura_create_invoice Create an unsent invoice document ~603
WRITE: creates ONE document in SuperFaktura for the user to review: type draft (concept, default), estimate (quote), order or proforma. A final regular invoice cannot be created here. It is NOT sent (no e-mail, no post), NOT marked paid or sent, and has no payment link or discount. Give an existing client_id (its name is read first with one extra GET /clients/view/{id}, so the call uses 2 requests of the daily quota) OR a new client's name (+ optional ico/dic/ic_dph/address...). Items: name, unit price without VAT, VAT rate, quantity. Not idempotent: pass a checksum (max 32 chars) so a timed-out call can be recovered with superfaktura_get_response_by_checksum instead of retried. POST /invoices/create.
| Name | Type | Req | Description |
|---|---|---|---|
| checksum | string | – | Your own unique token (max 32 chars) to recover the reply if the call times out. |
| client_address | string | – | Client street and number, with client_name. |
| client_city | string | – | Client city, with client_name. |
| client_country_id | integer | – | Client country id (superfaktura_list_countries), with client_name. |
| client_dic | string | – | Client tax id (DIČ), with client_name. |
| client_email | string | – | Client e-mail, with client_name (stored only; nothing is sent). |
| client_ic_dph | string | – | Client VAT id, with client_name. |
| client_ico | string | – | Client company id (IČO), with client_name. |
| client_id | integer | – | Existing client id (superfaktura_list_clients). Give this OR client_name. |
| client_name | string | – | Name of a new/matching client (used when client_id is not given). |
| client_zip | string | – | Client ZIP, with client_name. |
| comment | string | – | Comment on the document. |
| constant | string | – | Constant symbol. |
| created | string | – | Issue date (default today). |
| delivery | string | – | Delivery date. |
| due | string | – | Due date. |
| header_comment | string | – | Comment above the items (shown on the document). |
| internal_comment | string | – | Internal comment (not shown on the document). |
| invoice_currency | string | – | 3-letter currency code, e.g. EUR, CZK. |
| items | array | yes | 1-100 items. |
| name | string | – | Document title (default generated from the number). |
| order_no | string | – | Order number. |
| sequence_id | integer | – | Numbering sequence id (superfaktura_list_sequences). |
| specific | string | – | Specific symbol. |
| type | string | – | Document type: draft (default), estimate, order or proforma. |
| variable | string | – | Variable symbol (the document number when empty). |
No output schema declared.
No examples provided.
superfaktura_create_tag Create a tag ~59
WRITE: adds a new tag name (usable on invoices, expenses and clients in the SuperFaktura app). A duplicate name is refused by SuperFaktura. POST /tags/add.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tag name. |
No output schema declared.
No examples provided.
superfaktura_get_cash_register Get a cash register ~58
One cash register with currency, number of entries and current balance (read only). GET /cash_registers/view/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| cash_register_id | integer | yes | Cash register id (from superfaktura_list_cash_registers). |
No output schema declared.
No examples provided.
superfaktura_get_client Get a client ~56
One client with address, tax ids, bank data, default currency/due days/discount and statistics. GET /clients/view/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Client id (from superfaktura_list_clients). |
No output schema declared.
No examples provided.
superfaktura_get_company Get the company profile and API limits ~140
The company the API key is working in (name, IČO, DIČ, IČ DPH, address, VAT-payer flag, bank accounts) and the remaining API quota (SuperFaktura's fair-use policy is 1000 requests per day and 31000 per month; every tool call here uses one request). Good first call. With all_companies=true also the other companies the user can access (their ids are the company_id of the login). GET /users/getUserCompaniesData.
| Name | Type | Req | Description |
|---|---|---|---|
| all_companies | boolean | – | true = every company the user has access to, not only the current one. |
No output schema declared.
No examples provided.
superfaktura_get_expense Get an expense ~58
One expense with its items, VAT rates, payments and supplier. Attachments are not returned. GET /expenses/view/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| expense_id | integer | yes | Expense id (from superfaktura_list_expenses). |
No output schema declared.
No examples provided.
superfaktura_get_invoice Get an invoice ~97
One document (invoice, proforma, quote ...) with its header (number, dates, status, amounts, currency, symbols, comments), client, items, VAT summary, payments and related documents. The public access token and payment links of the document are not returned. GET /invoices/view/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | Invoice id (the id of a superfaktura_list_invoices row). |
No output schema declared.
No examples provided.
superfaktura_get_response_by_checksum Recover the reply of a create by its checksum ~80
If a superfaktura_create_invoice call timed out, fetch the reply of the ORIGINAL request by the checksum it was sent with (kept 3 months), so the document is not created twice. GET /api_logs/getResponseByChecksum/{checksum}.
| Name | Type | Req | Description |
|---|---|---|---|
| checksum | string | yes | The checksum given to superfaktura_create_invoice. |
No output schema declared.
No examples provided.
superfaktura_get_stock_item Get a stock item ~57
One warehouse item with SKU, price, VAT, purchase price and quantity in stock. GET /stock_items/view/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| stock_item_id | integer | yes | Stock item id (from superfaktura_list_stock_items). |
No output schema declared.
No examples provided.
superfaktura_list_bank_accounts List bank accounts ~42
The company's bank accounts as stored in SuperFaktura (bank name, IBAN, SWIFT, default flag). GET /bank_accounts/index.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superfaktura_list_bank_moves List imported bank account moves ~230
Bank transactions imported into SuperFaktura (date, amount, currency, variable symbol, counter account, matching state), newest first by default. Filter by date range, credit/debit or amount. Paged: pass next_page as page. GET /accounts/index.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | number | – | – |
| amount_to | number | – | – |
| date_period | string | – | Transaction date as a period. |
| date_since | string | – | Transactions on or after (yyyy-mm-dd). |
| date_to | string | – | Transactions on or before (yyyy-mm-dd). |
| direction | string | – | Sort direction. |
| move_type | string | – | credit = incoming, debit = outgoing. |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-100 (the account's profile default when omitted). |
| search | string | – | Text to search for (matched by SuperFaktura in names, numbers, e-mails ... of the records). |
No output schema declared.
No examples provided.
superfaktura_list_cash_registers List cash registers ~38
The company's cash registers with currency, number of entries and current balance (read only). GET /cash_registers/getDetails.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superfaktura_list_clients List or search clients ~187
List the address book (clients and suppliers) with contact data and totals. search matches name, IČO, DIČ, IČ DPH, bank account, e-mail, address, city, phone, note and tags. Paged: pass next_page as page. GET /clients/index.json.
| Name | Type | Req | Description |
|---|---|---|---|
| created_period | string | – | Created in this period. |
| direction | string | – | Sort direction (default DESC). |
| modified_period | string | – | Changed in this period. |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-100 (the account's profile default when omitted). |
| search | string | – | Text to search for (matched by SuperFaktura in names, numbers, e-mails ... of the records). |
No output schema declared.
No examples provided.
superfaktura_list_contact_persons List a client's contact persons ~50
The contact persons (name, e-mail, phone) stored for one client. GET /contact_people/getContactPeople/{client_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Client id. |
No output schema declared.
No examples provided.
superfaktura_list_countries List countries ~42
SuperFaktura's country ids with ISO code and EU flag, for the country_id of clients. GET /countries/index/view_full:1.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superfaktura_list_expense_categories List expense categories ~38
The expense category tree (id, name, parent) for the category_id of expenses. GET /expenses/expense_categories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superfaktura_list_expenses List or search expenses ~299
List received documents (expenses: received invoices, bills, internal documents) with amounts, VAT, supplier and payment status. status: issued (new), partially_paid, paid, overdue. Without a date filter SuperFaktura applies its default period; pass created_period='all' for everything. Paged: pass next_page as page. GET /expenses/index.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | number | – | – |
| amount_to | number | – | – |
| category_id | integer | – | Expense category id (superfaktura_list_expense_categories). |
| client_id | integer | – | Supplier (client) id. |
| created_period | string | – | Issue date as a period. |
| created_since | string | – | Issued on or after (yyyy-mm-dd). |
| created_to | string | – | Issued on or before (yyyy-mm-dd). |
| direction | string | – | Sort direction (default DESC). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-100 (the account's profile default when omitted). |
| search | string | – | Text to search for (matched by SuperFaktura in names, numbers, e-mails ... of the records). |
| status | string | – | Payment status. |
| type | string | – | Expense type (note the vendor's spelling recieved_credit_note). |
No output schema declared.
No examples provided.
superfaktura_list_invoices List or search invoices ~392
List issued documents with client, items, totals and payment status. type selects the document kind (default regular = ordinary invoices; also proforma, estimate = quote, order, cancel = credit note, delivery, draft, reverse_order; several allowed). Without a date filter SuperFaktura returns only the CURRENT YEAR; use created_period='all' or a date range for older ones. status: issued, partially_paid, paid, overdue. search matches client name, number, VS ... Paged: pass next_page as page. GET /invoices/index.json.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | number | – | Minimum amount. |
| amount_to | number | – | Maximum amount. |
| client_id | integer | – | Only documents of this client (superfaktura_list_clients). |
| created_period | string | – | Issue date as a period (default this_year when no date filter is given). |
| created_since | string | – | Issued on or after (yyyy-mm-dd). |
| created_to | string | – | Issued on or before (yyyy-mm-dd). |
| direction | string | – | Sort direction (default DESC). |
| invoice_no | string | – | Formatted document number, e.g. 2026001. |
| modified_period | string | – | Last changed in this period. |
| order_no | string | – | Order number the document was created from. |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-100 (the account's profile default when omitted). |
| search | string | – | Text to search for (matched by SuperFaktura in names, numbers, e-mails ... of the records). |
| status | string | – | Payment status. |
| type | array | – | Document types (default: regular). |
| variable | string | – | Variable symbol. |
No output schema declared.
No examples provided.
superfaktura_list_sequences List numbering sequences ~47
The document numbering sequences per document type (id, name, mask, next formatted number, default flag); sequence ids are used when creating documents. GET /sequences/index.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superfaktura_list_stock_items List or search stock items ~189
List warehouse items (name, SKU, unit, price, VAT, quantity in stock). search matches name, SKU and description; sku matches the SKU. Paged: pass next_page as page. GET /stock_items/index.json.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction. |
| in_stock_only | boolean | – | true = only items that are in stock. |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-100 (the account's profile default when omitted). |
| price_from | number | – | – |
| price_to | number | – | – |
| search | string | – | Text to search for (matched by SuperFaktura in names, numbers, e-mails ... of the records). |
| sku | string | – | Search by SKU. |
No output schema declared.
No examples provided.
superfaktura_list_stock_movements List stock movements of an item ~122
The stock log of one item (quantity changes, notes, related invoice or expense). Paged: pass next_page as page. GET /stock_items/movements/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default ASC). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Results per page, 1-100 (the account's profile default when omitted). |
| stock_item_id | integer | yes | Stock item id. |
No output schema declared.
No examples provided.
superfaktura_list_tags List tags ~32
The tags (id and name) usable on invoices, expenses and clients. GET /tags/index.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SuperFaktura MCP by usefulapi server?
SuperFaktura MCP by usefulapi is a hosted endpoint at https://superfaktura.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 · superfaktura.usefulapi.io
claude mcp add --transport http io-usefulapi-superfaktura 'https://superfaktura.usefulapi.io/mcp'
What is the SuperFaktura MCP by usefulapi server?
SuperFaktura MCP by usefulapi is listed in the public MCP registry as io.usefulapi/superfaktura. Read SuperFaktura invoices, clients, expenses, bank and stock; create clients, expenses and drafts. This page covers its hosted endpoint (https://superfaktura.usefulapi.io/mcp).
Is the SuperFaktura MCP by usefulapi server safe to use?
SuperFaktura MCP by usefulapi scores 18 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 SuperFaktura MCP by usefulapi server expose?
SuperFaktura MCP by usefulapi exposes 25 tools: superfaktura_get_company, superfaktura_list_invoices, superfaktura_get_invoice, superfaktura_list_clients, superfaktura_get_client, and 20 more. Their descriptions and schemas cost roughly 3,497 tokens of context every time the server is loaded.
Does the SuperFaktura MCP by usefulapi server require authentication?
Its publisher declares no required credentials for SuperFaktura MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the SuperFaktura MCP by usefulapi server still maintained?
SuperFaktura MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the SuperFaktura MCP by usefulapi server?
VerifyMCP ran 4 checks on SuperFaktura MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about SuperFaktura MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.