Skip to content

Jithox E-Invoice Readiness MCP server

com.jithox/einvoice-readinessjithox.comstreamable-httpv1.2.1Scanned

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

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Jithox E-Invoice Readiness MCP server can do

The Jithox E-Invoice Readiness MCP server is published by jithox.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: verify_vat_vies), but cannot delete data. 4 tools only read.

3 tools bring in text other people can write (verify_vat_vies, lookup_peppol_participant and get_einvoice_readiness).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • verify_vat_viesCheck a VAT number's ACTIVE status against the official EU VIES source.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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 4Show 4 read-only tools
  • get_einvoice_readinessReadiness snapshot for YOUR canary workspace: one plain state, what is ready, what is missing, and the next safe step.Reads text others writeNo findings

    Why it is in this group

    • The name "get_einvoice_readiness" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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…Reads text others writeNo findings

    Why it is in this group

    • The name "lookup_peppol_participant" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
521
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 521.

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 521
  2. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mcp.jithox.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mcp.jithox.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 521.View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 521
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mcp.jithox.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mcp.jithox.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: yes to not observed

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as einvoice-readiness. Review it before you use it.

Capability tags behind 3 rules
  • mcp__einvoice-readiness__verify_vat_vies untrusted-input
  • mcp__einvoice-readiness__lookup_peppol_participant untrusted-input
  • mcp__einvoice-readiness__get_einvoice_readiness untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.jithox/einvoice-readiness/verify?hash=b17a7ea17dfe2336efa320072293cdbf2a0980b958096287f91cdd22ece893bb" | jq -e '.changed == false'

Pinned hash b17a7ea17dfe, from Oct 21, 2026, 19:10 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.jithox/einvoice-readiness/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.jithox/einvoice-readiness
[![Anlyon Radar](https://radar.anlyon.com/badge/com.jithox/einvoice-readiness.svg)](https://radar.anlyon.com/servers/com.jithox/einvoice-readiness)

Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.

Jithox E-Invoice Readiness MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Jithox E-Invoice Readiness MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Jithox E-Invoice Readiness MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Jithox E-Invoice Readiness MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Jithox E-Invoice Readiness MCP server have?

5 tools: 1 write, 4 read. verify_vat_vies, validate_invoice, validate_vat_number, lookup_peppol_participant and get_einvoice_readiness.

Does the Jithox E-Invoice Readiness MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Jithox E-Invoice Readiness MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Jithox E-Invoice Readiness MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.