Fakturowo MCP by usefulapi
REMOTE · FAKTUROWO.USEFULAPI.IO
Read invoices, clients and products in Fakturowo; create documents and update payment status.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “issue_a_document_with_the_details_you_provide” functional
- New prompt “look_up_saved_clients_and_products” functional
- New prompt “record_an_invoice_payment_status” functional
- New prompt “review_invoices_and_their_line_items” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.6.0 → 1.8.0 functional
- Server version: 1.5.0 → 1.6.0 functional
- Server version: 1.4.2 → 1.5.0 functional
- 30 Oct 26 +1
- Server version: 1.4.1 → 1.4.2 functional
- Server version: 1.4.0 → 1.4.1 functional
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.2.0 → 1.3.0 functional
- 28 Oct 26 62
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 6 Nov 2026 · Probed https://fakturowo.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 fakturowo.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://fakturowo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/fakturowo/ |
| http (plaintext) | http://fakturowo.usefulapi.io/mcp | Inconclusive | 302 | http://fakturowo.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 →
fakturowo_create_document Create document ~339
WRITE: issue a new document (invoice, proforma, receipt...) on the account. It is saved immediately and takes the next number in its sequence; this tool cannot delete it again, and calling it twice issues two documents. Issue documents one at a time and wait for each reply: Fakturowo says overlapping saves can get the same number when the account's numbering check is off. Needs a buyer and at least one line item; the seller defaults to what the account has saved only if Fakturowo allows that, otherwise pass seller. Returns the new document's id (api_numer); with public_links true also a public PDF and preview link (anyone with the link can open the document). Fakturowo api_zadanie=1.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | object | yes | Buyer details. |
| currency | string | – | Currency code (default PLN). |
| document_type | string | – | Document type (default vat_invoice). |
| issue_date | string | – | Issue date (default today). |
| items | array | yes | Line items (1-300). |
| notes | string | – | Notes printed on the document. |
| paid_amount | number | – | Amount already paid (subtracted from the total). |
| payment_status | string | – | Payment status (default unpaid). |
| payment_type | string | – | Payment method / term. |
| place | string | – | Place of issue (default: the account's saved place). |
| public_links | boolean | – | Return public PDF and preview links (default false). |
| sale_date | string | – | Sale date (default today). |
| seller | object | – | Seller details. |
No output schema declared.
No examples provided.
fakturowo_get_client Get client ~68
One saved client by id (api_numer, from fakturowo_list_clients). PESEL and ID-card numbers are never returned. Fakturowo api_zadanie=4 with api_numer.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client's api_numer. |
No output schema declared.
No examples provided.
fakturowo_get_document Get document ~96
One document by its id (api_numer, from fakturowo_list_documents or the id returned when it was created): the header fields and every line item (name, unit, quantity, net/gross price, discount, VAT rate and amount, gross value). Fakturowo api_zadanie=3 with api_numer.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | integer | yes | The document's api_numer. |
No output schema declared.
No examples provided.
fakturowo_get_next_document_number Get next document number ~67
The running number Fakturowo will give the next document of a type (the sequence counter saved on the account). Nothing is created. Fakturowo api_zadanie=8.
| Name | Type | Req | Description |
|---|---|---|---|
| document_type | string | – | Document type (default vat_invoice). |
No output schema declared.
No examples provided.
fakturowo_get_product Get product ~59
One saved product by id (api_numer, from fakturowo_list_products). Fakturowo api_zadanie=6 with api_numer.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | The product's api_numer. |
No output schema declared.
No examples provided.
fakturowo_list_clients List clients ~98
List the saved clients (contractors), 100 per page: id (api_numer), name, address, tax number, contact details, account number and notes. PESEL and ID-card numbers are never returned. Fakturowo api_zadanie=4.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1; 100 rows per page). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fakturowo_list_documents List documents ~203
List invoices and other documents on the account, 100 per page: id (api_numer), type, number, issue and sale date, currency, net/VAT/gross value, seller and buyer, payment status, due date and KSeF number. Filter by document type or by seller/buyer tax number. Values are the vendor's own (dates DD-MM-YYYY; dokument_rodzaj is the type code with a readable name for common types). Fakturowo api_zadanie=3.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_tax_id | string | – | Only documents of the buyer with this tax number (NIP). |
| document_type | string | – | Only this document type. |
| page | integer | – | Page number, from 1 (default 1; 100 rows per page). Pass the previous reply's next_page. |
| seller_tax_id | string | – | Only documents of the seller with this tax number (NIP). |
No output schema declared.
No examples provided.
fakturowo_list_products List products ~101
List the saved products and services (the catalogue used on documents), 100 per page: id (api_numer), name, unit, VAT rate, net price, gross value, currency, comment, GTU code and discount. Fakturowo api_zadanie=6.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1; 100 rows per page). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
fakturowo_set_document_payment_status Set document payment status ~116
WRITE: change the payment status of an existing document (unpaid, paid, partially_paid) and optionally the amount already paid. Only those fields are sent; Fakturowo edits the document in place. Fakturowo api_zadanie=1 with api_numer.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | integer | yes | The document's api_numer. |
| paid_amount | number | – | Amount already paid (for partially_paid, or to record the amount). |
| status | string | yes | New payment status. |
No output schema declared.
No examples provided.
How do I install the Fakturowo MCP by usefulapi server?
Fakturowo MCP by usefulapi is a hosted endpoint at https://fakturowo.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 · fakturowo.usefulapi.io
claude mcp add --transport http io-usefulapi-fakturowo 'https://fakturowo.usefulapi.io/mcp'
What is the Fakturowo MCP by usefulapi server?
Fakturowo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/fakturowo. Read invoices, clients and products in Fakturowo; create documents and update payment status. This page covers its hosted endpoint (https://fakturowo.usefulapi.io/mcp).
Is the Fakturowo MCP by usefulapi server safe to use?
Fakturowo 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 Fakturowo MCP by usefulapi server expose?
Fakturowo MCP by usefulapi exposes 9 tools: fakturowo_list_documents, fakturowo_get_document, fakturowo_get_next_document_number, fakturowo_list_clients, fakturowo_get_client, and 4 more. Their descriptions and schemas cost roughly 1,147 tokens of context every time the server is loaded.
Does the Fakturowo MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Fakturowo 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 Fakturowo MCP by usefulapi server still maintained?
Fakturowo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 Fakturowo MCP by usefulapi server?
VerifyMCP ran 4 checks on Fakturowo 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 Fakturowo 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.