Edinet
NPM · @PIPEWORX/MCP-EDINET · 2 COMPONENTS
EDINET — Japan's corporate-filings system (Financial Services Agency).
Available components
Last scanned (9 hours ago)
Scores higher than 72% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-edinet). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 956 tokens (~239/item across 4 items; 4 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 Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 (16)
- Malware scan
- 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 npm/@pipeworx/mcp-edinet@0.2.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-edinet |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-edinet/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617586198 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9db5a37aa9dcec6667487aa61f71313b11eb5bd037f7abed6b0b29f05116064adfda588ea2110ade33bc37c6da92b9ddbeb8beeb1dee3c6f7d46921bc |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
edinet_company_filings ~227
All EDINET filings by one Japanese company over a date range of up to 31 days, newest first. EDINET has no company-search endpoint, so this walks the daily filing lists and keeps that filer's rows. Identify the company with edinet_search_filers first. Requires a free EDINET Subscription-Key via _apiKey. Example: edinet_company_filings({ edinet_code: "E02144", from: "2026-06-01", to: "2026-06-30" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | EDINET API v2 Subscription-Key. |
| edinet_code | string | – | EDINET code of the filer, e.g. "E02144" (Toyota). |
| from | string | yes | Start date (JST) as YYYY-MM-DD. |
| sec_code | string | – | Securities code / ticker instead of an EDINET code, e.g. "7203". |
| to | string | yes | End date (JST) as YYYY-MM-DD, at most 31 days after `from`. |
No output schema declared.
No examples provided.
edinet_financials ~235
Reported annual financials of a Japanese listed company from its EDINET annual securities report: net sales, operating income, net income attributable to owners of the parent, total assets, net assets, with fiscal period, accounting standard (J-GAAP / IFRS / US GAAP), the filing document id, and margins. Each amount states its currency and unit and is the full-fiscal-year figure as filed; an amount whose unit cannot be established is returned unresolved, never guessed. A filer without structured data returns found:false. Requires a free EDINET Subscription-Key via _apiKey. Example: edinet_financials({ sec_code: "8035" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | EDINET API v2 Subscription-Key. |
| edinet_code | string | – | EDINET code, e.g. "E01057". |
| fiscal_year | number | – | Calendar year in which the fiscal year ends (March 2026 year end = 2026). Default: the latest filed. |
| sec_code | string | – | Securities code / ticker instead, e.g. "8035". |
No output schema declared.
No examples provided.
edinet_list_filings ~262
Every disclosure document filed with EDINET on one day — annual and quarterly securities reports, extraordinary reports, large-shareholding reports, tender offers — with filer, document type, period and which formats (XBRL / PDF / CSV / English) exist. Optionally filter to one filer or document type. Requires a free EDINET Subscription-Key via _apiKey. Example: edinet_list_filings({ date: "2026-09-11", limit: 20 }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | EDINET API v2 Subscription-Key. |
| date | string | yes | Filing date (JST) as YYYY-MM-DD. EDINET keeps the last 10 years. |
| doc_type_code | string | – | Keep only this EDINET document-type code, e.g. "120" (annual securities report). |
| edinet_code | string | – | Keep only this filer, e.g. "E02144". |
| limit | number | – | Max filings to return, 1-500. Default 50. |
| sec_code | string | – | Keep only this securities code / ticker, e.g. "7203". |
| xbrl_only | boolean | – | Keep only filings that have XBRL. Default false. |
No output schema declared.
No examples provided.
edinet_search_filers ~180
Resolve a Japanese company to its EDINET code and securities code from the FSA's official EDINET filer list — the lookup every other EDINET call needs. Searches Japanese name, English name, kana, EDINET code and ticker across ~11,000 filers, and returns industry, listing status, fiscal year end and corporate number. Needs no API key. Example: edinet_search_filers({ query: "Toyota" }) → E02144 / 7203.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max filers to return, 1-50. Default 10. |
| listed_only | boolean | – | Only return exchange-listed filers (上場). Default false. |
| query | string | yes | Company name in Japanese or English, an EDINET code (E02144), or a securities code / ticker (7203). |
No output schema declared.
No examples provided.
How do I install the Edinet MCP server?
Edinet runs locally as an npm package, launched with npx -y @pipeworx/mcp-edinet. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-edinet
claude mcp add pipeworx-io-edinet -- npx -y @pipeworx/mcp-edinet
What is the Edinet MCP server?
Edinet is an MCP server listed in the public MCP registry as io.github.pipeworx-io/edinet. EDINET, Japan's corporate-filings system (Financial Services Agency). This page covers its npm package (@pipeworx/mcp-edinet).
Is the Edinet MCP server safe to use?
Edinet scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Edinet MCP server expose?
Edinet exposes 4 tools: edinet_search_filers, edinet_list_filings, edinet_company_filings, edinet_financials. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.
Is the Edinet MCP server still maintained?
Edinet 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 Edinet MCP server under?
Edinet declares the MIT 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 Edinet MCP server?
VerifyMCP ran 16 checks on Edinet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.