Greece Invoices (AADE myDATA national API)
Server Details
Greece myDATA invoices for AI agents: build AADE XML, transmit to myDATA, query by MARK.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Server Listing
- Greece Invoice MCP
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one creates invoices and the other queries by MARK. No ambiguity or overlap.
Both tool names follow a clear verb_noun pattern (create_invoice, query_invoice), consistent and predictable.
With only 2 tools, the server feels extremely thin for the scope of a national invoicing API. Essential operations like update, cancel, list, and search are missing.
The surface covers creation and query by MARK only, leaving major gaps such as updating, cancelling, listing invoices by criteria, or handling other document types.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
create_invoice1 field changed- changed
Input schema / properties / counterpart_vat / descriptionPrevious value: -"Buyer (counterpart) Greek VAT number / ΑΦΜ, 9 digits (EL/GR prefix optional). Required for a B2B invoice; omit for a retail receipt."New value: +"Buyer (counterpart) Greek VAT number / ΑΦΜ, 9 digits (EL/GR prefix optional). Always required — v1 covers B2B invoices (invoiceType 1.1/2.1/5.1); retail receipts without a counterpart are not supported yet."
- Changed
query_invoice1 field changed- changed
Input schema / properties / mark / descriptionPrevious value: -"The MARK (unique registration number) returned by create_invoice. Pass 0 to list transmitted docs from the start."New value: +"Result status values: REGISTERED (found, was transmitted by you), NOT_FOUND (no document with that MARK), LISTED (returned in a range listing). The MARK (unique registration number) returned by create_invoice. Pass 0 to list transmitted docs from the start."
2 tool updates
- First observed
create_invoice - First observed
query_invoice
Related MCP Connectors
Italy FatturaPA invoices for AI agents: build FPR12 XML, transmit to the SdI, query status.
Romania e-Factura invoices for AI agents: build UBL 2.1 CIUS-RO, upload to ANAF/SPV, query.
Serbia SEF eFaktura invoices for AI agents: build UBL 2.1 SRB-CIUS, upload to SEF, query, cancel.
Peru CPE invoices for AI agents - issue, query, void facturas/boletas via SUNAT (2 backends).
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage e-invoices through natural language, supporting EU compliance formats like ZUGFeRD and XRechnung, as well as US plain PDF invoices.7-
- AlicenseAqualityBmaintenanceRead-only MCP server for the Greek AADE myDATA e-books API, enabling natural language queries about invoices, income, and expenses with decoded bilingual labels.41MIT

InvoiceXMLofficial
AlicenseNot gradedqualityCmaintenanceInvoiceXML brings e-invoice compliance to your AI agent. Create, validate, convert, render, and extract structured invoices across UBL (Peppol BIS Billing 3.0, used worldwide), CII, Factur-X, ZUGFeRD, and XRechnung, all checked against the EN 16931 standard and official Schematron rules. Ask your assistant to generate a compliant invoice, validate one for errors, or convert between formats, with n5MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to issue Italian FatturaPA electronic invoices and transmit them to the SdI via Invoicetronic. Supports creating and querying invoices with Italian VAT rates.MIT