Skip to content

Jithox E-Invoice Readiness

by jithox.com · remote · no sign-in to list tools · v1.2.1 · published by com.jithox

Read-only EU e-invoice checks: VAT format, VIES, Peppol lookup. Returns evidence, no filing.

Changes · 1
CompareRegistry entry

5 tools: 1 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http einvoice-readiness https://mcp.jithox.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 1Claude Code: ask
  • verify_vat_viesCheck a VAT number's ACTIVE status against the official EU VIES source.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check a VAT number's ACTIVE status against the official EU VIES source. Returns valid / invalid / invalid_input / unavailable with provenance (source, checkedAt). When VIES is unavailable it says so truthfully and makes no validity claim. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
Only reads 4Claude Code: allow
  • get_einvoice_readinessReadiness snapshot for YOUR canary workspace: one plain state, what is ready, what is missing, and the next safe step.No findings

    Why it is in this group

    • The name "get_einvoice_readiness" says "get": a word for reading.
    Description, as the server wrote it
    Readiness snapshot for YOUR canary workspace: one plain state, what is ready, what is missing, and the next safe step. Diagnostics, not a compliance certificate. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
  • lookup_peppol_participantCheck whether a receiver is registered on the Peppol network and accepts BIS Billing 3.0 invoices, via the official SML/SMP discovery route when enabled (otherwise an honest mock t…No findings

    Why it is in this group

    • The name "lookup_peppol_participant" says "lookup": a word for reading.
    Description, as the server wrote it
    Check whether a receiver is registered on the Peppol network and accepts BIS Billing 3.0 invoices, via the official SML/SMP discovery route when enabled (otherwise an honest mock that says so). Only status registered/not_registered is definitive; unavailable/not_configured are truthful and never a hidden "no". Provide vatId or endpointId (at least one) plus the receiver country. Lookup only — never a send action, and no send tool exists here. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • destructiveHint: false
  • validate_invoiceStructurally validate a draft EU invoice and report machine-readable issues (schema problems, VAT-id format, date sanity, BIS 3.0 completeness, computed totals).No findings

    Why it is in this group

    • The name "validate_invoice" says "validate": a word for reading.
    Description, as the server wrote it
    Structurally validate a draft EU invoice and report machine-readable issues (schema problems, VAT-id format, date sanity, BIS 3.0 completeness, computed totals). Full report, never fails fast. Not legal approval. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • validate_vat_numberDeterministic structure/checksum validation of an EU VAT number (incl.No findings

    Why it is in this group

    • The name "validate_vat_number" says "validate": a word for reading.
    Description, as the server wrote it
    Deterministic structure/checksum validation of an EU VAT number (incl. the Belgian modulo-97 checksum) with the normalized identifier and a stable issue code. Format plausibility only — not a live VIES result. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http einvoice-readiness https://mcp.jithox.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__einvoice-readiness__validate_invoice",
      "mcp__einvoice-readiness__validate_vat_number",
      "mcp__einvoice-readiness__lookup_peppol_participant",
      "mcp__einvoice-readiness__get_einvoice_readiness"
    ],
    "ask": [
      "mcp__einvoice-readiness__verify_vat_vies"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as einvoice-readiness. Review it before you use it.