io.github.matematicsolutions/hu-eli-mcp
PYPI · HU-ELI-MCP
MCP server for Hungarian legislation (Nemzeti Jogszabalytar): native ELI and verifiable citations.
Available components
Last scanned (6 hours ago)
Scores higher than 57% of PyPI servers
Category Education and Research
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 Security32
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known advisory affects this package; its severity couldn't be graded. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 72 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1677 tokens (~279/item across 6 items; 6 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −5
- Stability: pass → 0.63 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.80 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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/hu-eli-mcp@0.3.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w8v5-vhqr-4h9v | CVE-2025-69872 | medium | no | |
| PYSEC-2026-2447 | CVE-2025-69872 | none | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 2 |
| 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 →
hu_coverage ~102
Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns: ``Coverage`` with families, an as-of note, and a non-empty list of known gaps.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_note | string | yes | States what the dates mean, and what they do not promise. |
| families | array | – | – |
| known_gaps | array | – | Never empty. An empty list would mean 'not checked', not 'no gaps'. |
| status | string | – | – |
No examples provided.
hu_get_act ~101
Fetch metadata for a Hungarian Act (torveny) by its ELI (year + serial).
| Name | Type | Req | Description |
|---|---|---|---|
| serial | string | yes | the Act's serial number within that year, e.g. ``"5"`` (2013. evi V. torveny is Act no. 5 of 2013, the Hungarian Civil Code). |
| year | string | yes | 4-digit year, e.g. ``"2013"``. |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_note | string | – | – |
| doc_type | – | – | – |
| eli_uri | – | – | – |
| human_readable_citation | – | – | – |
| in_force_date | – | – | – |
| issuer | – | – | – |
| serial | – | – | – |
| source_url | – | – | – |
| subtitle | – | – | – |
| title | – | – | – |
| year | – | – | – |
No examples provided.
hu_get_legislation ~197
Fetch metadata for any Hungarian legislation by its ELI (type + year + issuer + serial). Use this for anything other than Acts (torveny) - government decrees, ministerial decrees, etc. Use `hu_list_doc_types` for valid `doc_type` codes and `hu_list_issuers` for valid `issuer` codes (issuer codes are case-sensitive, e.g. `Korm` for Government).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | yes | NJT type code, e.g. ``"R"`` (rendelet / decree). |
| issuer | string | yes | NJT issuer code, case-sensitive, e.g. ``"Korm"`` (Government). |
| serial | string | yes | the document's serial number within that year, e.g. ``"428"``. |
| year | string | yes | 4-digit year, e.g. ``"2016"``. |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_note | string | – | – |
| doc_type | – | – | – |
| eli_uri | – | – | – |
| human_readable_citation | – | – | – |
| in_force_date | – | – | – |
| issuer | – | – | – |
| serial | – | – | – |
| source_url | – | – | – |
| subtitle | – | – | – |
| title | – | – | – |
| year | – | – | – |
No examples provided.
hu_get_text ~151
Fetch the full document HTML content of a Hungarian piece of legislation. For Acts (torveny), pass `doc_type="TV"` and omit `issuer`. For anything else, pass the `issuer` code (case-sensitive - use `hu_list_issuers`).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | yes | NJT type code, e.g. ``"TV"`` (torveny / Act) or ``"R"`` (rendelet / decree). |
| issuer | – | – | NJT issuer code, case-sensitive (required for everything except `"TV"`). |
| serial | string | yes | the document's serial number within that year. |
| year | string | yes | 4-digit year. |
| Name | Type | Req | Description |
|---|---|---|---|
| byte_size | – | – | – |
| content | – | – | – |
| dataset_note | string | – | – |
| doc_type | string | yes | – |
| eli_uri | – | – | – |
| format | string | – | – |
| human_readable_citation | – | – | – |
| in_force_date | – | – | – |
| issuer | – | – | – |
| serial | string | yes | – |
| source_url | – | – | – |
| subtitle | – | – | – |
| title | – | – | – |
| year | string | yes | – |
No examples provided.
hu_list_doc_types ~64
List valid NJT document-type codes (e.g. TV=Act, R=decree) from /eli/tipuskodok. Returns: ``DocTypeList`` with ``items: list[DocTypeInfo]`` (code + Hungarian name).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_note | string | – | – |
| items | array | – | – |
No examples provided.
hu_list_issuers ~62
List valid NJT issuer codes (case-sensitive, e.g. Korm=Government) from /eli/kibocsatokodok. Returns: ``IssuerList`` with ``items: list[IssuerInfo]`` (code + Hungarian name).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_note | string | – | – |
| items | array | – | – |
No examples provided.
How do I install the io.github.matematicsolutions/hu-eli-mcp server?
io.github.matematicsolutions/hu-eli-mcp runs locally as a PyPI package, launched with uvx hu-eli-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · hu-eli-mcp
claude mcp add matematicsolutions-hu-eli-mcp -- uvx hu-eli-mcp
What is the io.github.matematicsolutions/hu-eli-mcp server?
io.github.matematicsolutions/hu-eli-mcp is listed in the public MCP registry as io.github.matematicsolutions/hu-eli-mcp. MCP server for Hungarian legislation (Nemzeti Jogszabalytar): native ELI and verifiable citations. This page covers its PyPI package (hu-eli-mcp).
Is the io.github.matematicsolutions/hu-eli-mcp server safe to use?
io.github.matematicsolutions/hu-eli-mcp scores 58 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. 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.matematicsolutions/hu-eli-mcp server expose?
io.github.matematicsolutions/hu-eli-mcp exposes 6 tools: hu_get_act, hu_get_legislation, hu_get_text, hu_list_doc_types, hu_coverage, hu_list_issuers. Their descriptions and schemas cost roughly 677 tokens of context every time the server is loaded.
Is the io.github.matematicsolutions/hu-eli-mcp server still maintained?
io.github.matematicsolutions/hu-eli-mcp 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.matematicsolutions/hu-eli-mcp server under?
io.github.matematicsolutions/hu-eli-mcp 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.
What did VerifyMCP test on the io.github.matematicsolutions/hu-eli-mcp server?
VerifyMCP ran 15 checks on io.github.matematicsolutions/hu-eli-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.matematicsolutions/hu-eli-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.