io.github.BerkantACUN/efatura-kontrol
PYPI · EFATURA-KONTROL
GİB e-Fatura/e-Arşiv/e-İrsaliye belgelerini GİB'in XSD ve şematron kurallarıyla yerelde denetler
Available components
Last scanned (2 hours ago)
Scores higher than 90% of PyPI servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- 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
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to BerkantACUN/efatura-kontrol). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 44 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 738 tokens (~147/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +10
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.63 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed pypi/efatura-kontrol@0.1.0
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 | BerkantACUN/efatura-kontrol |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BerkantACUN/efatura-kontrol/.github/workflows/publish.yaml@refs/tags/v0.1.0 |
| Rekor log index | 2906273418 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:89db6da75a1f4683e75c562e6588b47886c861adfffb38cac75248509657fd3d |
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 30 packages
| Packages resolved | 30 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
belge_dogrula ~223
UBL-TR belgesini denetler: XML biçimi, OASIS UBL 2.1 XSD, GİB e-Fatura şematronu (498 kural, kod listeleri dahil), satır/vergi/tevkifat/dip toplam aritmetiği, imza yapısı. Her bulgu: kod, seviye (hata/uyari/bilgi), GİB'in özgün mesajı, satır numarası, Türkçe açıklama ve düzeltme. `dosya` yerel yol ya da `xml` belge metni; `tur` fatura|earsiv|irsaliye|irsaliye-yaniti| uygulama-yaniti|zarf (verilmezse kök elemandan ve ProfileID'den bulunur). Validates a Turkish UBL-TR e-invoice with the tax authority's own schematron and returns findings.
| Name | Type | Req | Description |
|---|---|---|---|
| dosya | – | – | – |
| tur | – | – | – |
| xml | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
belge_ozeti ~96
Belgenin kimliği: senaryo, fatura tipi, numara, UUID, tarih, para birimi, satıcı/alıcı (VKN/TCKN, unvan), satırlar (ilk 50), vergiler, dip toplamlar, imzalı mı. Summary of a UBL-TR document: parties, lines, taxes and totals.
| Name | Type | Req | Description |
|---|---|---|---|
| dosya | – | – | – |
| xml | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bulgu_acikla ~68
Bir bulgu kodunun (örn. sch-GeneralUnitCodeCheck-1, hesap-dip-odenecek) Türkçe açıklaması, hangi alanın neden reddedildiği ve nasıl düzeltileceği. Explains a finding code.
| Name | Type | Req | Description |
|---|---|---|---|
| kod | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
kod_listeleri ~52
Mevcut GİB kod listelerinin adları ve Türkçe açıklamaları; kaynak paket sürümleri. Names of the available code lists and the GİB package versions this build uses.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
kod_listesi ~107
GİB kod listesinin değerleri (şematronun fiilen uyguladığı liste): UnitCodeList, TaxType, InvoiceTypeCodeList, ProfileIDType, CurrencyCodeList, WithholdingTaxTypeWithPercent, TaxExemptionReasonCodeType, PaymentMeansCodeTypeList... `ara` ile alt dize filtresi. Values of a GİB code list as enforced by the schematron.
| Name | Type | Req | Description |
|---|---|---|---|
| ara | – | – | – |
| liste | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.BerkantACUN/efatura-kontrol MCP server?
io.github.BerkantACUN/efatura-kontrol runs locally as a PyPI package, launched with uvx efatura-kontrol. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · efatura-kontrol
claude mcp add berkantacun-efatura-kontrol -- uvx efatura-kontrol
What is the io.github.BerkantACUN/efatura-kontrol MCP server?
io.github.BerkantACUN/efatura-kontrol is an MCP server listed in the public MCP registry as io.github.BerkantACUN/efatura-kontrol. GİB e-Fatura/e-Arşiv/e-İrsaliye belgelerini GİB'in XSD ve şematron kurallarıyla yerelde denetler. This page covers its PyPI package (efatura-kontrol).
Is the io.github.BerkantACUN/efatura-kontrol MCP server safe to use?
io.github.BerkantACUN/efatura-kontrol scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.BerkantACUN/efatura-kontrol MCP server expose?
io.github.BerkantACUN/efatura-kontrol exposes 5 tools: belge_dogrula, belge_ozeti, bulgu_acikla, kod_listesi, kod_listeleri. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.
Is the io.github.BerkantACUN/efatura-kontrol MCP server still maintained?
io.github.BerkantACUN/efatura-kontrol is still listed as active in the MCP registry. We last reached this channel on 5 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.BerkantACUN/efatura-kontrol MCP server under?
io.github.BerkantACUN/efatura-kontrol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.