Alpaca Trading API integration for Model Context Protocol (MCP)
Japan EDINET Filing Index is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
What has this Japanese company filed on EDINET (FSA) in the last 365 days? Hosted. Facts only.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http japan-edinet-filing-index-mcp https://jp-edinet-production.mk-career-planning.workers.dev/mcp
# 2 — ask your agent for something these tools do
# catalog, edinet_company_filings, edinet_filing_relations and 2 more
Japan EDINET Filing Index costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http japan-edinet-filing-index-mcp https://jp-edinet-production.mk-career-planning.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the tools of this server with prices, data sources, licensing, daily limits and data freshness.
No parameter schema on file.
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 subsidiary codes, parent document, withdrawal, disclosure and correction status, and the EDINET link. Wi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | EDINET code (e.g. E02144), securities code (4 or 5 characters, e.g. 7203 or 72030) or 13-digit corporate number |
| since | string | no | Only filings submitted on or after this date (YYYY-MM-DD, Japan time). Default: start of the indexed range |
| doc_type | string | no | Optional EDINET document type code, e.g. 120 (annual securities report) or 180 (extraordinary report) |
| limit | integer | no | Maximum number of filings, 1-100 (default 50) |
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 correction and non-disclosure records. Each relation names its basis field. Targets not in the index are retu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| doc_id | string | yes | EDINET document ID (8 characters), e.g. S100ABCD |
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; names that appear to be individuals are withheld. A list of filings ordered by time only: no holdin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issuer | string | yes | Issuer: EDINET code (e.g. E02144), securities code (4 or 5 characters, e.g. 7203 or 72030) or 13-digit corporate number |
| since | string | no | Only filings submitted on or after this date (YYYY-MM-DD). Default: 90 days ago |
| kind | string | no | Optional filter: large_shareholding or tender_offer |
| limit | integer | no | Maximum number of filings, 1-200 (default 50) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id returned with a paid result ("rcpt_" + 64 hex characters). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Japan EDINET Filing Index or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Japan EDINET Filing Index can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.