Japan Corporate Filings
REMOTE · EDINET-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS
Search Japanese corporate disclosures (FSA EDINET): securities reports and shareholding reports.
Available components
Last scanned (59 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 17 Oct 2026 · Probed https://edinet-mcp.easakura.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easakura.workers.dev | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a7163aae2923cc020e1322b0e402e606 |
| SANs: easakura.workers.dev, *.easakura.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of edinet-mcp.easakura.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://edinet-mcp.easakura.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://edinet-mcp.easakura.workers.dev/mcp | Inconclusive | 404 |
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 →
get_daily_filings 特定日の全開示書類一覧（EDINET） ~90
指定日に提出された全開示書類の一覧を取得する。大量保有報告書のウォッチ、決算開示の網羅チェックなどに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 日付 YYYY-MM-DD |
| doc_type | string | – | 書類種別で絞り込み |
| max_results | integer | – | 最大件数 |
No output schema declared.
No examples provided.
search_filings 企業の開示書類を検索（EDINET） ~186
金融庁EDINETから上場企業等の開示書類（有価証券報告書・四半期報告書・大量保有報告書など）を検索する。企業名または証券コードで、直近N日分（最大31日）の提出書類を横断検索。投資リサーチ・信用調査・競合分析に使う。
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | 企業名（部分一致。例: トヨタ） |
| days_back | integer | – | 何日前まで遡るか（1〜31） |
| doc_type | string | – | 書類種別で絞り込み |
| max_results | integer | – | 最大件数 |
| sec_code | string | – | 証券コード4桁（例: 7203） |
No output schema declared.
No examples provided.
How do I install the Japan Corporate Filings MCP server?
Japan Corporate Filings is a hosted endpoint at https://edinet-mcp.easakura.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · edinet-mcp.easakura.workers.dev
claude mcp add --transport http easakura-japan-corporate-filings-mcp 'https://edinet-mcp.easakura.workers.dev/mcp'
What is the Japan Corporate Filings MCP server?
Japan Corporate Filings is an MCP server listed in the public MCP registry as io.github.easakura/japan-corporate-filings-mcp. Search Japanese corporate disclosures (FSA EDINET): securities reports and shareholding reports. This page covers its hosted endpoint (https://edinet-mcp.easakura.workers.dev/mcp).
Is the Japan Corporate Filings MCP server safe to use?
Japan Corporate Filings scores 18 out of 100 on VerifyMCP. 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 Japan Corporate Filings MCP server expose?
Japan Corporate Filings exposes 2 tools: search_filings, get_daily_filings. Their descriptions and schemas cost roughly 276 tokens of context every time the server is loaded.
Does the Japan Corporate Filings MCP server require authentication?
Its publisher declares no required credentials for Japan Corporate Filings. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Japan Corporate Filings MCP server still maintained?
Japan Corporate Filings is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.