io.github.matematicsolutions/jp-eli-mcp
PYPI · JP-ELI-MCP
MCP server for Japan's e-Gov law search API: search, fetch, and cite national legislation.
Available components
Last scanned (5 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1133 tokens (~188/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
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 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 −5
- Stability: pass → 0.63 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 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/jp-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 | allowlisted | 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 →
jp_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.
jp_get_article ~91
Fetch the text of one article of a law.
| Name | Type | Req | Description |
|---|---|---|---|
| article_num | string | yes | the e-Gov ``Num`` attribute, e.g. ``"1"`` for Article 1, ``"3_2"`` for a branch article (第三条の二). |
| law_id | string | yes | e.g. ``"129AC0000000089"`` (the Civil Code). |
| Name | Type | Req | Description |
|---|---|---|---|
| article_num | string | yes | – |
| caption | – | – | – |
| dataset_note | string | – | – |
| eli_note | string | – | – |
| eli_uri | – | – | – |
| human_readable_citation | – | – | – |
| law_id | string | yes | – |
| source_url | – | – | – |
| text | – | – | – |
No examples provided.
jp_get_full_text ~53
Fetch the full text of a law by ``law_id``. Large laws are truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | string | yes | e.g. ``"129AC0000000089"`` (the Civil Code). |
| Name | Type | Req | Description |
|---|---|---|---|
| byte_size | – | – | – |
| content | – | – | – |
| dataset_note | string | – | – |
| eli_note | string | – | – |
| eli_uri | – | – | – |
| human_readable_citation | – | – | – |
| law_id | string | yes | – |
| source_url | – | – | – |
| truncated | boolean | – | – |
No examples provided.
jp_get_law ~54
Fetch metadata for a law by its e-Gov ``law_id`` (no body text).
| Name | Type | Req | Description |
|---|---|---|---|
| law_id | string | yes | e.g. ``"129AC0000000089"`` (the Civil Code). |
| Name | Type | Req | Description |
|---|---|---|---|
| amendment_enforcement_date | – | – | – |
| amendment_law_id | – | – | – |
| dataset_note | string | – | – |
| eli_note | string | – | – |
| eli_uri | – | – | – |
| human_readable_citation | – | – | – |
| law_id | string | yes | – |
| law_num | – | – | – |
| law_title | – | – | – |
| law_type | – | – | – |
| promulgation_date | – | – | – |
| source_url | – | – | – |
No examples provided.
jp_search_by_keyword ~72
Full-text search across all Japanese laws for a keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | e.g. ``"個人情報"`` (personal information). |
| limit | integer | – | max results, 1-100 (default 10). |
| offset | integer | – | pagination offset (default 0). |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_note | string | – | – |
| items | array | – | – |
| keyword | string | yes | – |
| next_offset | – | – | – |
| total_count | integer | yes | – |
No examples provided.
jp_search_laws ~73
Search Japanese laws by (partial) title.
| Name | Type | Req | Description |
|---|---|---|---|
| law_title | string | yes | e.g. ``"民法"`` (Civil Code) or ``"個人情報の保護に関する法律"``. |
| limit | integer | – | max results, 1-100 (default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_note | string | – | – |
| items | array | – | – |
| query | string | yes | – |
| total_count | integer | yes | – |
No examples provided.
How do I install the io.github.matematicsolutions/jp-eli-mcp server?
io.github.matematicsolutions/jp-eli-mcp runs locally as a PyPI package, launched with uvx jp-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 · jp-eli-mcp
claude mcp add matematicsolutions-jp-eli-mcp -- uvx jp-eli-mcp
What is the io.github.matematicsolutions/jp-eli-mcp server?
io.github.matematicsolutions/jp-eli-mcp is listed in the public MCP registry as io.github.matematicsolutions/jp-eli-mcp. MCP server for Japan's e-Gov law search API: search, fetch, and cite national legislation. This page covers its PyPI package (jp-eli-mcp).
Is the io.github.matematicsolutions/jp-eli-mcp server safe to use?
io.github.matematicsolutions/jp-eli-mcp scores 60 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/jp-eli-mcp server expose?
io.github.matematicsolutions/jp-eli-mcp exposes 6 tools: jp_search_laws, jp_search_by_keyword, jp_get_law, jp_get_article, jp_coverage, jp_get_full_text. Their descriptions and schemas cost roughly 445 tokens of context every time the server is loaded.
Is the io.github.matematicsolutions/jp-eli-mcp server still maintained?
io.github.matematicsolutions/jp-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/jp-eli-mcp server under?
io.github.matematicsolutions/jp-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.