Jithox Payment Checks

MCP ServerCommunity

Free, read-only MCP checks an AI agent runs before it pays a supplier or sends an EU e-invoice: IBAN verification, payment-change checks, payment preflight, Peppol readiness and Peppol participant lookup. A separate Jithox MCP server covers e-invoicing: e-invoice readiness, invoice and VAT number validation, and VIES VAT verification. Both endpoints are remote, need no account, and answered an MCP handshake when checked on October 6, 2026.

IBAN verificationpayment fraudvendor payment changePeppolEU e-invoicingVAT validation

Status

Community

Auth

None

Hosting

Remote

Community rating

Not rated yet

Role

Source

Provides data. A read-only feed from one provider; it answers questions, doesn't act, and doesn't expect other servers alongside it. More on Source servers → All seven roles →

Open documentation →

Caveats

Two separate servers: payment checks at https://jithox.com/api/mcp (verify_iban, check_payment_change, preflight_payment, check_peppol_ready, lookup_peppol_participant) and e-invoice checks at https://mcp.jithox.com/mcp (get_einvoice_readiness, validate_invoice, validate_vat_number, verify_vat_vies). Both answered an MCP handshake on October 6, 2026.
Community-built by a small publisher; source is MIT-licensed at https://github.com/victor-emmanuel-c/jithox-mcp. No account is required, which also means no service-level commitment.
An IBAN format or checksum pass does not confirm who owns the account. Payment-change checks support, but do not replace, call-back verification to a known contact.
Focused on EU supplier payments and e-invoicing (Peppol, VIES). It does not screen sanctions lists or cover US ACH or wire fraud.
Start with read-only scopes and keep client-side approval prompts on until the connection is proven.

Rate this server

How to connect Jithox Payment Checks

Step 1

Remote server: paste a URL

Jithox Payment Checks publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://jithox.com/api/mcp

Client config snippet

{
  "mcpServers": {
    "f104c6a2-4f62-4715-a745-a069d4da502a": {
      "url": "https://jithox.com/api/mcp"
    }
  }
}

Step 2

Authenticate with no credentials

No credentials are required for public data. Rate limits still apply, so avoid bulk pulls from a chat client.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Compliance, Risk & Regulatory.

Compliance history and diligence file

The regulatory record a buyer's counsel will request.

Sell / M&A ReadinessCompliance, Risk & RegulatoryAdvisor & Firm Intelligence / Prospecting

Read-only: assemble my firm's regulatory record from two directions, my internal compliance or GRC systems for what they actually hold (policy versions, control testing, vendor diligence, open findings and remediation status) and the public regulatory and firm-intelligence sources for registration history, ADV disclosures and complaints. Show them side by side and flag anything disclosed publicly with no internal record, or internally tracked that the public record does not reflect. List exam findings and correspondence separately as 'to gather offline' unless a connected system genuinely holds them. Cite each source and mark anything unverified as 'to confirm'. Do not file, submit or amend anything.

Guardrail · Read-only. The internal half of this record usually lives outside any connected tool, and filings are amended through official channels only.

Diligence readiness checklist

A gap list before you open a data room.

Sell / M&A ReadinessCRMCompliance, Risk & RegulatoryAccounting & Tax

Build a diligence readiness checklist across client, financial, custody and compliance records. For each item say whether it exists today, where it lives, and what work is needed. Use read-only access, keep client identities out of the output, and do not create or share a data room or upload any document.

Guardrail · Read-only. Never let a tool export client data to an external destination.

Annual compliance review prep

A gap list against your compliance calendar.

Compliance & Audit ReadinessCompliance, Risk & RegulatoryCRM

Read-only: review my annual compliance calendar against what my connected systems can actually evidence. Use the compliance or GRC platform for the items it genuinely holds, such as policy versions, control testing, vendor diligence and open findings, and use CRM for the client-facing items, disclosure delivery, agreement dates, suitability updates and contact records for the sample under review. List Item / Owner / Due / Status / Evidence location / Source tool, and mark any calendar item that no connected system covers as 'no connected source' rather than inferring its status. Do not mark anything complete, edit records or file anything.

Guardrail · Read-only. Most servers in this category cover firm security and GRC rather than adviser books and records, so expect gaps a person has to fill.

Read the full connection guide →