Edinet MCP server

edinet — Japanese corporate filings (EDINET, Financial Services Agency)

Status: PUBLIC, shipped BYOK 2026-09-16 (fleet #1942/#1928). The keyless company lookup works for every caller with no credential; the two filing-list tools take the CALLER's own EDINET Subscription-Key as _apiKey. See "Auth" below for why it shipped that way rather than on a platform key.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

EDINET is Japan's EDGAR: securities reports (有価証券報告書), quarterly and half-year reports, extraordinary reports, large-shareholding reports (大量保有報告書), tender offers, and the XBRL/PDF/CSV documents behind them.

Tools

The two access rules

is served by the FSA with no credential — a ~570 KB ZIP holding one ShiftJIS CSV. The pack unzips it (DecompressionStream('deflate-raw')) and decodes it (TextDecoder('shiftjis')); both are supported in workerd, verified 2026-09-13 on a local wrangler dev, which is worth knowing because no other pack in this repo decodes a legacy Japanese encoding.

1. The code list is keyless. https://disclosure2dl.edinet-fsa.go.jp/searchdocument/codelist/Edinetcode.zip

_apiKey. Sent upstream as the Subscription-Key query parameter.

1. The API v2 needs a free Subscription-Key, passed by the caller as

Auth

BYO key. edinetsearchfilers needs none. edinetlistfilings and edinetcompanyfilings require an EDINET API v2 Subscription-Key, which the caller supplies as _apiKey; without one they refuse with the words "requires an API key", so the gateway books the refusal as a gate rather than as a defect of ours.

Pipeworx holds no platform key for EDINET, and that is a decision, not an oversight (fleet #1942, 2026-09-16). Bruce registered an EDINET account — the account exists — but the FSA's own key-issuance page rendered blank on their side, so the account could not yield a key. Rather than hold a finished pack behind a third party's outage, the pack shipped BYOK.

Anyone re-checking this: the thing to look at is the key page behind a logged-in EDINET account, not the pre-auth URL — …/api/auth/index.aspx?mode=1 302s to Azure B2C and answers normally whether or not the page behind the login works, so probing it unauthenticated tells you nothing either way.

If a key is obtained, platformKeyEnv: 'PLATFORMEDINETKEY' goes in the manifest in the same change that lands wrangler secret put — declaring it early un-sinks routing and points Japanese-filings questions at tools that can only refuse (the fda-inspections precedent, #617).

Traps

Shortened. The full README is on GitHub.