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.

Vyfakturuj MCP by usefulapi

REMOTE · VYFAKTURUJ.USEFULAPI.IO

Read and create Vyfakturuj invoices and contacts: search, number series, payment methods, tags.

64 Trust /100

Last scanned (16 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 18 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 2110 tokens (~211/item across 10 items; 10 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 Management20
  • Stability observed for 6 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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 18 Oct 2026 · Probed https://vyfakturuj.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 vyfakturuj.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://vyfakturuj.usefulapi.io/.well-known/oauth-protected-resource/mcp"

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

Protected resource metadata

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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vyfakturuj.usefulapi.io/mcp Redirected 302 https://usefulapi.io/vyfakturuj/
http (plaintext) http://vyfakturuj.usefulapi.io/mcp Inconclusive 302 http://vyfakturuj.usefulapi.io/mcp
MCP tools · 10 exposed · ~1,892 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
vyfakturuj_create_contact ~236

WRITE. Adds a contact to the address book (it is not a customer message: nothing is sent). Give at least a name (the address-book label) or company or last name. Returns the new contact with its id. POST /contact/.

NameTypeReqDescription
DICstring–DIC (VAT id).
ICstring–ICO (company id).
citystring–City.
companystring–Company name.
country_codestring–ISO 3166 country code, e.g. CZ, SK, DE.
days_dueinteger–Default days until due for this contact.
firstnamestring–First name.
lastnamestring–Last name.
mail_tostring–E-mail where invoices and reminders go.
namestring–Address-book name (how it is listed).
notestring–Your note about the contact.
streetstring–Street.
telstring–Phone.
webstring–Web.
zipstring–Postal code (PSC).

No output schema declared.

No examples provided.

vyfakturuj_create_invoice ~629

WRITE. Creates a document in Vyfakturuj. Vyfakturuj has NO draft state: the document is issued at once and takes the next number of its number series (delete or cancel it in Vyfakturuj if wrong). Does NOT send an e-mail to the customer, does NOT mark it paid and moves no money; automatic reminders and paid notices are switched off for it (disable_automated_mails). Name the customer with id_customer (an address-book contact, from vyfakturuj_list_contacts) or with the customer_* fields. Items need text and unit_price. Optional id_number_series / id_payment_method come from vyfakturuj_list_number_series / vyfakturuj_list_payment_methods; the account defaults apply otherwise. Prices are net unless calculate_vat is 2 (gross). POST /invoice/.

NameTypeReqDescription
VSinteger–Variable symbol (default: derived from the number).
calculate_vat––1 items are net (VAT added), 2 items are gross, 3 special VAT regime, 4 domestic reverse charge, 5 not a VAT payer, 6 foreign reverse charge.
currencystring–Currency, ISO 4217 (default: the account's).
customer_DICstring–Customer DIC (VAT id).
customer_ICstring–Customer ICO (company id).
customer_citystring–Customer city.
customer_country_codestring–ISO 3166 country code, e.g. CZ, SK, DE.
customer_firstnamestring–Customer first name.
customer_lastnamestring–Customer last name.
customer_namestring–Customer company name (when no id_customer).
customer_streetstring–Customer street.
customer_zipstring–Customer postal code (PSC).
date_createdstring–Issue date yyyy-mm-dd (default today).
date_taxable_supplystring–Date of taxable supply (DUZP) yyyy-mm-dd.
days_dueinteger–Days until due (splatnost).
id_customer––Address-book contact id (from vyfakturuj_list_contacts); fills the customer block.
id_number_series––Number series id (from vyfakturuj_list_number_series); must match the document type.
id_payment_method––Payment method id (from vyfakturuj_list_payment_methods).
itemsarrayyesDocument items (1-200).
languagestring–Language of the document.
note_internalstring–Internal note (not on the document).
order_numberstring–Order id / reference.
text_before_itemsstring–Text before the items.
text_invoice_footerstring–Text in the footer.
type––Document type: 1 faktura (default), 2 zalohova faktura, 4 proforma faktura, 8 vyzva k platbe, 512 objednavka.

No output schema declared.

No examples provided.

vyfakturuj_get_contact ~61

One address-book contact with every field (billing and delivery address, ICO/DIC, e-mails, default texts and days_due). GET /contact/{id}/.

NameTypeReqDescription
id–yesThe contact id (from vyfakturuj_list_contacts).

No output schema declared.

No examples provided.

vyfakturuj_get_invoice ~88

One document with all fields: supplier and customer blocks, items (text, quantity, unit_price, vat_rate, totals), dates, VS, bank details, total, flags and flags_decoded, payment method, public page, PDF and online-payment URLs. GET /invoice/{id}/.

NameTypeReqDescription
id–yesThe invoice id (from vyfakturuj_list_invoices).

No output schema declared.

No examples provided.

vyfakturuj_get_template ~85

One template / recurring invoice (sablona, pravidelna faktura) by id: its items, customer, schedule and settings. The API has no list endpoint for templates, so the id comes from the user (the number in the template's URL in Vyfakturuj). GET /template/{id}/.

NameTypeReqDescription
id–yesThe template id.

No output schema declared.

No examples provided.

vyfakturuj_list_contacts ~222

Search the address book (adresar): id, name, company, ICO (IC), DIC, address, e-mail (mail_to), phone, default days_due. Filter by free text q, ICO, DIC, name, e-mail or phone. Paged with rows_limit/rows_offset. GET /contact/.

NameTypeReqDescription
DICstring–Exact DIC (VAT id).
ICstring–Exact ICO (company id).
mail_tostring–E-mail address of the contact.
namestring–Address-book name.
qstring–Free-text search.
rows_limitinteger–Rows to return, 1-100 (default 25).
rows_offsetinteger–Rows to skip (default 0). Use next_offset from the previous reply.
sortstring–Sort: column~asc or column~desc, several joined by | (for example date_created~desc|number~asc).
telstring–Phone number.

No output schema declared.

No examples provided.

vyfakturuj_list_invoices ~402

Search documents (faktury, zalohove faktury, proformy, objednavky ...); pass sort=date_created~desc for the newest first. Each row has id, number, type, dates, customer, VS, currency, total, flags and flags_decoded (paid, sent_to_customer, cancelled, ...) and the public/PDF URLs; use vyfakturuj_get_invoice for the whole document with items. Filter by free text q, customer id, document type, number, variable symbol (VS), currency or creation date range. Paged with rows_limit/rows_offset. GET /invoice/.

NameTypeReqDescription
VSstring–Variable symbol (variabilni symbol).
currencystring–Currency, ISO 4217, e.g. CZK, EUR.
date_created_fromstring–Created on or after this date (yyyy-mm-dd).
date_created_tostring–Created on or before this date (yyyy-mm-dd).
id_customer––Only invoices of this address-book contact (from vyfakturuj_list_contacts).
numberstring–Exact document number.
qstring–Free-text search over the invoices.
rows_limitinteger–Rows to return, 1-100 (default 25).
rows_offsetinteger–Rows to skip (default 0). Use next_offset from the previous reply.
sortstring–Sort: column~asc or column~desc, several joined by | (for example date_created~desc|number~asc).
type––Document type: 1 faktura, 2 zalohova faktura, 4 proforma, 8 vyzva k platbe, 16 danovy doklad, 32 opravny danovy doklad, 64 prijmovy doklad, 128 opravny doklad, 512 objednavka.

No output schema declared.

No examples provided.

vyfakturuj_list_number_series ~61

The numbering series (ciselne rady) of the account: id_number_series, the document type it is for, name and the number pattern. Use the id in vyfakturuj_create_invoice. GET /settings/number-series/.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vyfakturuj_list_payment_methods ~66

The payment methods of the account (id_payment_method, name, type: 1 bank transfer, 2 cash, 4 cash on delivery, 8 card, ...). Use the id in vyfakturuj_create_invoice. GET /settings/payment-method/.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

vyfakturuj_list_tags ~42

The tags (stitky) of the account: id_tag, name and colour. Invoices carry an id_tag. GET /settings/tags/.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Vyfakturuj MCP by usefulapi server?

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

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

What is the Vyfakturuj MCP by usefulapi server?

Vyfakturuj MCP by usefulapi is listed in the public MCP registry as io.usefulapi/vyfakturuj. Read and create Vyfakturuj invoices and contacts: search, number series, payment methods, tags. This page covers its hosted endpoint (https://vyfakturuj.usefulapi.io/mcp).

Is the Vyfakturuj MCP by usefulapi server safe to use?

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

Vyfakturuj MCP by usefulapi exposes 10 tools: vyfakturuj_list_invoices, vyfakturuj_get_invoice, vyfakturuj_create_invoice, vyfakturuj_list_contacts, vyfakturuj_get_contact, and 5 more. Their descriptions and schemas cost roughly 1,892 tokens of context every time the server is loaded.

Does the Vyfakturuj MCP by usefulapi server require authentication?

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

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