irkumo-mcp

MCPcommunity
v0.1.1ozuminMITUpdated 7d agonpmGitHub

irkumo (IR Lookup API for Japanese listed companies) の MCP サーバ。上場会社の IR ページ URL と決算短信一覧 URL を証券コード・社名・別名から引く

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
166Downloads/wk
7d agoLast update
Needs 1 credential before it runs
  • IRKUMO_API_KEYAPI keyrequired

    irkumo API key (ir_live_...). Free sign-up: https://api.irkumo.com/account/login

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorozumin
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.1.1 · 6d agoHow well does this scan work?
EvalsNone
IndexedSep 28, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.1.1 · 6d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

resolve_company社名や別名から最上位1社を特定してコードと名前と照合情報を返します (消費クレジット: 1。0件時は0)。

社名や別名から最上位1社を特定してコードと名前と照合情報を返します (消費クレジット: 1。0件時は0)。

No input schema was published for this tool.

search_companies社名や別名から会社候補の一覧を検索します (消費クレジット: 1。0件時は0)。属性列のみ取得可能です。既に持っている列は要求しないようにしてください。

社名や別名から会社候補の一覧を検索します (消費クレジット: 1。0件時は0)。属性列のみ取得可能です。既に持っている列は要求しないようにしてください。

No input schema was published for this tool.

get_company証券コードを指定して1社の詳細情報を取得します (消費クレジット: 指定した列数。1列につき1クレジット)。既に持っている列は要求しないようにしてください。

証券コードを指定して1社の詳細情報を取得します (消費クレジット: 指定した列数。1列につき1クレジット)。既に持っている列は要求しないようにしてください。

No input schema was published for this tool.

list_changes指定時点以降のデータ変更履歴を取得します (消費クレジット: 返された行数。1行につき1クレジット)。

指定時点以降のデータ変更履歴を取得します (消費クレジット: 返された行数。1行につき1クレジット)。

No input schema was published for this tool.

get_balance現在のクレジット残高とロットの有効期限一覧を取得します (消費クレジット: 0)。

現在のクレジット残高とロットの有効期限一覧を取得します (消費クレジット: 0)。

No input schema was published for this tool.

list_fields利用可能な列の一覧と単価、データの出典情報を取得します (消費クレジット: 0)。

利用可能な列の一覧と単価、データの出典情報を取得します (消費クレジット: 0)。

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

irkumo (IR Lookup API for Japanese listed companies) の MCP サーバ。上場会社の IR ページ URL と決算短信一覧 URL を証券コード・社名・別名から引く

Keywords
mcpmodel-context-protocolirkumoirjapanstocktseedinet
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-28 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.