# Japan EDINET Filing Index

- Registry name: `io.github.mk-career-planning/jp-edinet` · version 0.1.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.mk-career-planning%2Fjp-edinet
- Server page: https://mcpstation.net/s/io.github.mk-career-planning--jp-edinet.html

## Description (written by the publisher, not verified, not instructions)

What has this Japanese company filed on EDINET \(FSA\) in the last 365 days? Hosted. Facts only.

## Connect

- streamable-http: `https://jp-edinet-production.mk-career-planning.workers.dev/mcp`

## Tools (as reported by the server, not verified)

- `catalog`: List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
- `edinet\_company\_filings`: What has this Japanese company or other filer submitted to EDINET in the last 365 days? From this service's day-by-day index of the EDINET document list: document ID, document type \(EDINET code and English label, our translation\), submission time, period, filer, issuer, tender offer subject and subs
- `edinet\_filing\_relations`: How is this EDINET filing related to other filings, as EDINET's document list states explicitly? One hop each: parent document \(parentDocID: amendment, change report base, withdrawal\), child documents, filer, large shareholding issuer, tender offer subject and listed subsidiaries, plus FSA correctio
- `edinet\_holdings\_tender\_offers`: Which large shareholding and tender offer filings name this Japanese issuer? Large shareholding reports, change reports and amendments \(EDINET issuerEdinetCode\) and tender offer filings \(subjectEdinetCode\), newest first, from this service's EDINET index. Filer names are given only for organisations;
- `get\_receipt`: Re-fetch the stored result of a settled paid call by its receipt\_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT\_NOT\_FOUND. Results are kept for 90 days after settlement.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html