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.

io.github.cmendezs/mcp-ksef-pl

PYPI · MCP-KSEF-PL

Polish e-invoicing MCP: KSeF API v2, FA(3)/FA(2) XML, Peppol BIS 3.0, NIP/REGON validation.

Available components

−15 this week 78 Trust /100

Last scanned (21 hours ago)

Scores higher than 76% of PyPI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to cmendezs/mcp-ksef-pl). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 53 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4639 tokens (~82/item across 56 items; 56 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "peppol_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Oct 26 +1
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

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 4 Nov 2026 · Analysed pypi/mcp-ksef-pl@0.10.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo cmendezs/mcp-ksef-pl
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/cmendezs/mcp-ksef-pl/.github/workflows/publish.yml@refs/tags/v0.10.1
Rekor log index 2805184081
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:e7f596687f4850de9424661392539c6f55c45301d2462d3393a14ad38e8c5aa8

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 56 exposed · ~4,416 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
validate_fa3_invoice ~139

Validate a KSeF FA(3) XML invoice before submission to KSeF API v2 (PL-6.2). Runs XSD validation against specs/schemat_FA(3)_v1-0E.xsd (requires lxml) and FA(3)-specific business-rule checks including namespace, mandatory Adnotacje sub-elements, JST/GV flags, and the absence of the FA(2) <FaWiersze> wrapper. Call this after generate_fa3_invoice and before submit_invoice_to_ksef. Returns a DocumentValidationResult with errors and warnings.

NameTypeReqDescription
xml_contentstringyes–
NameTypeReqDescription
errorsarray––
metadataobject––
validbooleanyes–
warningsarray––

No examples provided.

validate_mls_message ~92

Validate a Peppol Message Level Status (MLS) document. Runs the bundled MLS Schematron rules (requires the ``[xslt2]`` optional extra). No bespoke MLS XSD exists — full UBL 2.1 XSD validation is out of scope.

NameTypeReqDescription
mls_xml_base64stringyesBase64-encoded MLS (UBL ApplicationResponse-2) XML.

Structured output declared, but exposes no named fields.

No examples provided.

validate_peppol_invoice ~199

Validate a Peppol BIS 3.0 / EN 16931 UBL 2.1 XML invoice. Checks the CEN EN16931 base rules only (structural + arithmetic/totals, ~50 BR-* rules) via mcp-einvoicing-core's bundled Schematron validator. Does NOT check the Peppol-specific overlay (profile/process ID registration, EndpointID scheme, narrowed code lists) — the result's metadata.scope is "en16931-base-only", and a warning is included. This is not a full Peppol BIS3 conformance check; a document that passes may still be rejected by a real Peppol Access Point (no confirmed OpenPeppol redistribution rights for the overlay rules). Call this after generate_peppol_invoice to check the generated output. Returns a DocumentValidationResult with errors and warnings.

NameTypeReqDescription
xml_contentstringyes–
NameTypeReqDescription
errorsarray––
metadataobject––
validbooleanyes–
warningsarray––

No examples provided.

validate_polish_nip ~66

Validate a Polish NIP (tax identification number). Applies the official 10-digit checksum algorithm. Accepts NIP with or without dashes/spaces. Returns {'valid': bool, 'nip': str, 'normalized': str}.

NameTypeReqDescription
nipstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_polish_regon ~52

Validate a Polish REGON (business registry number — 9 or 14 digits). Returns {'valid': bool, 'regon': str, 'length': int}.

NameTypeReqDescription
regonstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_tsr_report ~67

Validate a Peppol Transaction Statistics Report (TSR) document. Runs XSD structural validation, then Schematron business rules (requires the ``[xslt2]`` optional extra).

NameTypeReqDescription
report_xml_base64stringyesBase64-encoded TSR XML document.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.cmendezs/mcp-ksef-pl server?

io.github.cmendezs/mcp-ksef-pl runs locally as a PyPI package, launched with uvx mcp-ksef-pl. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-ksef-pl

# add to Claude Code
claude mcp add cmendezs-mcp-ksef-pl -- uvx mcp-ksef-pl
Common questions

What is the io.github.cmendezs/mcp-ksef-pl server?

io.github.cmendezs/mcp-ksef-pl is listed in the public MCP registry as io.github.cmendezs/mcp-ksef-pl. Polish e-invoicing MCP: KSeF API v2, FA(3)/FA(2) XML, Peppol BIS 3.0, NIP/REGON validation. This page covers its PyPI package (mcp-ksef-pl).

Is the io.github.cmendezs/mcp-ksef-pl server safe to use?

io.github.cmendezs/mcp-ksef-pl scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.cmendezs/mcp-ksef-pl server expose?

io.github.cmendezs/mcp-ksef-pl exposes 56 tools: generate_fa2_invoice, generate_fa3_invoice, validate_fa2_invoice, validate_fa3_invoice, parse_fa2_invoice, and 51 more. Their descriptions and schemas cost roughly 4,416 tokens of context every time the server is loaded.

Is the io.github.cmendezs/mcp-ksef-pl server still maintained?

io.github.cmendezs/mcp-ksef-pl is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.cmendezs/mcp-ksef-pl server under?

io.github.cmendezs/mcp-ksef-pl declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.