japan-intelligence-api
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@japan-intelligence-apianalyze Toyota's latest disclosures"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Japan Intelligence API
AIエージェントのための日本市場インテリジェンス基盤
Japan Intelligence は、日本の公開情報を構造化し、AIエージェントが即座に利用可能な形式で提供するAPIプラットフォームです。14のデータソースを横断統合し、企業分析・マクロ経済・金融政策・環境災害を49エンドポイント + 27 MCPツールで完結させます。
🎯 1つのAPIキーで日本の全て — 適時開示、機関投資家の持分変動、500万法人のデータベース、政府統計10系列、株価ヒストリカル、日銀短観、投資部門別売買動向、日米金融政策、天気予報、地震データ、経済カレンダー、AI解釈を統合提供
Architecture
┌──────────────────────────────────────────────────────────────────┐
│ AI Agent (Claude, Cursor, etc.) │
│ ↓ MCP (22 tools) │
│ ┌──────────────────────────────┐ │
│ │ MCP Server (22 tools) │ │
│ └──────────────┬───────────────┘ │
│ ↓ REST API (35 endpoints) │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ Japan Intelligence API (FastAPI) │ │
│ │ │ │
│ │ Layer 2: AI Interpretation (Gemini 2.5 Flash) │ │
│ │ Layer 1: Structured Data + Cache-Control (per-source) │ │
│ │ │ │
│ │ ┌─────┐ ┌──────┐ ┌────────┐ ┌──────┐ ┌────────┐ │ │
│ │ │TDnet│ │EDINET│ │gBizINFO│ │e-Stat│ │J-Quants│ │ │
│ │ └─────┘ └──────┘ └────────┘ └──────┘ └────────┘ │ │
│ │ ┌────┐ ┌───┐ ┌───┐ ┌─────┐ ┌───────────┐ │ │
│ │ │FRED│ │BOJ│ │JPX│ │Macro│ │Interpreter│ │ │
│ │ └────┘ └───┘ └───┘ └─────┘ └───────────┘ │ │
│ └──────────────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────────┘Related MCP server: Edition Intelligence Platform
Data Sources (14)
# | Source | Data | Coverage |
1 | TDnet | 適時開示 — 業績修正、M&A、自社株買い、配当等15カテゴリ自動分類 | 全上場企業 |
2 | EDINET | 大量保有報告書 — 機関投資家の持分変動(5%超) | 全上場企業 |
3 | gBizINFO | 企業情報 — 補助金、認定、特許、財務、調達 | 500万法人 |
4 | e-Stat | 政府統計10系列 — GDP、CPI、失業率、鉱工業生産、小売、景気ウォッチャー、家計調査、貿易統計 | 日本経済全体 |
5 | J-Quants | 市場データ — 全銘柄マスタ、決算、財務、株価ヒストリカル(OHLCV + 移動平均)、セクター分析 | 全上場銘柄 |
6 | FRED | 日米マクロ — 金利、CPI、雇用、為替、VIX(10系列) | 米国+日本 |
7 | BOJ | 日銀短観 — 業況判断DI(大企業/中小×製造業/非製造業+設備投資計画) | 四半期更新 |
8 | JPX | 投資部門別売買動向 — 外国人、個人、信託銀行、事業法人(9部門構造化) | 週次 |
9 | Macro | リアルタイム指標 — 原油、金、ドル円、VIX、日経、S&P + 異常変動検知 | 6指標 |
10 | AI | Gemini 2.5 Flash による構造化データ解釈(Layer 2) | 全データ |
11 | The社史 | 上場企業253社の創業〜現在の社歴 | 主要上場企業 |
12 | Open-Meteo | 天気予報(JMAモデル) — 8主要都市 + ビジネスインパクト判定 | 東京〜那覇 |
13 | USGS | 地震データ — 日本周辺M3+、セクター影響分析、津波警報 | 日本全域 |
14 | Calendar | 経済カレンダー — BOJ会合、短観、GDP、CPI、決算、休場日 | 2026年 |
Key Endpoints (44)
Intelligence — 1コールで全て把握
# 日本全体ブリーフィング(朝の第一手)★
GET /api/v1/briefing
# 企業インテリジェンス — 6軸分析(プロフィール+財務+株価+開示+保有+マクロ)★
GET /api/v1/intelligence/{ticker}
# マーケットスナップショット — 市場全体 + 投資部門別フロー + セクター概況
GET /api/v1/market/snapshot
# 開示統計 — 市場の温度感
GET /api/v1/disclosures/statsCorporate Data
GET /api/v1/company/{id} # 企業プロフィール
GET /api/v1/company/{id}/patents # 特許ポートフォリオ
GET /api/v1/company/{id}/subsidies # 補助金実績
GET /api/v1/company/{id}/certifications # 認定情報
GET /api/v1/company/{id}/finance # 財務データ
GET /api/v1/company/search?name=ソニー # 企業名検索
GET /api/v1/disclosures # 適時開示一覧
GET /api/v1/disclosures/{ticker} # 銘柄別開示
GET /api/v1/holdings # 大量保有報告
GET /api/v1/holdings/{ticker} # 銘柄別大量保有Market & Financials
GET /api/v1/financials/{ticker} # 財務サマリー(売上・利益・EPS・予想)
GET /api/v1/stocks # 全上場銘柄マスタ
GET /api/v1/earnings # 決算カレンダー
GET /api/v1/prices/{ticker} # 株価ヒストリカル(OHLCV + MA5/25/75 + 騰落率)★NEW
GET /api/v1/sectors # セクター分析(17/33業種 + 市場区分別構成)★NEWGovernment Statistics & Global Macro
GET /api/v1/stats/series # 利用可能統計系列一覧
GET /api/v1/stats/summary # マクロ統計サマリー(1コール)
GET /api/v1/stats/{series_id} # 個別統計(gdp, cpi, unemployment等10系列)
GET /api/v1/stats/search/{kw} # 統計検索
GET /api/v1/global/series # FRED系列一覧
GET /api/v1/global/policy # 日米金融政策サマリー(1コール)
GET /api/v1/global/{series_key} # FRED個別系列
GET /api/v1/tankan # 日銀短観サマリー
GET /api/v1/tankan/{series_id} # 短観個別系列
GET /api/v1/tankan/series/list # 短観系列一覧
GET /api/v1/investor-flows # 投資部門別売買動向(9部門構造化)Macro & Events
GET /api/v1/macro # マクロ6指標
GET /api/v1/macro/events # 異常変動検知 + 恩恵/逆風銘柄
POST /api/v1/interpret # AI解釈(Layer 2)
GET /api/v1/ticker/{ticker} # 銘柄名解決
GET /api/v1/health # ヘルスチェックEnvironment & Disaster
GET /api/v1/weather # 日本8都市の天気予報(ビジネスインパクト判定付き)
GET /api/v1/weather/cities # 利用可能な都市一覧
GET /api/v1/earthquakes # 日本周辺の地震データ(セクター影響分析付き)
GET /api/v1/calendar # 経済カレンダー(BOJ会合・短観・GDP・CPI・決算・休場日)
GET /api/v1/calendar/holidays # 東証休場日
GET /api/v1/calendar/categories # カレンダーカテゴリ一覧Response Caching
ソース特性別に最適化されたHTTPキャッシュ:
Source | Cache-Control max-age | 理由 |
TDnet | 5分 | リアルタイム性重視 |
Macro | 5分 | リアルタイム性重視 |
Intelligence | 10分 | 複合ソース |
FRED | 1時間 | 高頻度参照 |
e-Stat | 6時間 | 月次更新 |
BOJ | 6時間 | 四半期更新 |
EDINET | 6時間 | 日次更新 |
J-Quants | 12時間 | 日次更新 |
JPX | 12時間 | 週次更新 |
gBizINFO | 24時間 | 低頻度更新 |
ETag対応(304 Not Modified)、stale-while-revalidate対応。
Authentication
All endpoints (except /docs, /redoc, /health) require API key authentication:
# Header authentication (recommended)
curl -H "X-API-Key: YOUR_API_KEY" https://japan-intelligence-api.onrender.com/api/v1/briefing
# Bearer token
curl -H "Authorization: Bearer YOUR_API_KEY" https://japan-intelligence-api.onrender.com/api/v1/briefing
# Query parameter
curl "https://japan-intelligence-api.onrender.com/api/v1/briefing?api_key=YOUR_API_KEY"Rate limit: 100 requests/hour per API key (X-RateLimit-Limit/Remaining headers).
MCP Server (27 tools for AI Agents)
Category | Tool | Description |
Intelligence |
| 🌟 Daily briefing — market, policy, tankan, sentiment, investor flows |
| Market overview — macro + events + disclosures + investor flows + sectors | |
| 🌟 Cross-source 6-axis company analysis (profile + financials + stock price + disclosures + holdings + macro) | |
| Disclosure statistics — sentiment gauge | |
Market |
| TDnet corporate disclosures with impact assessment |
| 6 key macro indicators (Nikkei, USD/JPY, VIX, etc.) | |
| Macro anomaly detection with stock mapping | |
Company |
| gBizINFO full company data (patents, subsidies, etc.) |
| Search 5M+ corporations | |
| J-Quants financial statements with forecasts | |
| All listed stocks master | |
| Upcoming earnings dates | |
| 🆕 Stock price history with MA5/25/75 + daily/weekly/monthly changes | |
| 🆕 Market structure — 17/33 sector classifications + market segment distribution | |
Economics |
| e-Stat 10 series (GDP, CPI, economy watchers, trade, etc.) |
| Macro statistics summary (1 call) | |
| FRED US + Japan macro (rates, CPI, FX, VIX) | |
| US-Japan monetary policy summary (1 call) | |
| BOJ Tankan business sentiment DI | |
| JPX weekly investor flow data (9 categories with directional signals) | |
Utility |
| Ticker → company name resolution |
| AI interpretation (Layer 2, Gemini 2.5) |
Claude Desktop / Cursor Configuration
{
"mcpServers": {
"japan-intelligence": {
"command": "node",
"args": ["/path/to/mcp-server/dist/index.js"],
"env": {
"JAPAN_INTELLIGENCE_API_URL": "https://japan-intelligence-api.onrender.com",
"JI_API_KEY": "YOUR_API_KEY"
}
}
}
}Framework Integration (LangChain / CrewAI)
LangChain
from integrations.transcode_langchain import get_transcode_tools
from langchain_openai import ChatOpenAI
from langgraph.prebuilt import create_react_agent
tools = get_transcode_tools(api_key="your-api-key")
llm = ChatOpenAI(model="gpt-4o")
agent = create_react_agent(llm, tools)
result = agent.invoke({
"messages": [("user", "What's happening in Japanese markets today?")]
})11 tools: japan_briefing, company_intelligence, market_snapshot, disclosures, ai_summarized_disclosures, holdings, investor_flows, macro_events, tankan_summary, economic_calendar, batch_intelligence
CrewAI
from integrations.transcode_crewai import TranscodeTools
from crewai import Agent, Task, Crew
tools = TranscodeTools(api_key="your-api-key")
analyst = Agent(
role="Japan Market Analyst",
goal="Analyze Japanese market conditions and identify opportunities",
tools=tools.all(), # 9 tools, or tools.core() for 4 essentials
)
task = Task(
description="Create a morning briefing on Japanese markets",
expected_output="Structured market report with key takeaways",
agent=analyst,
)
crew = Crew(agents=[analyst], tasks=[task])
result = crew.kickoff()Standalone (No Framework)
from integrations.transcode_langchain import TranscodeClient
client = TranscodeClient(api_key="your-api-key")
briefing = client.briefing()
intel = client.intelligence("7203") # ToyotaBatch API (Developer/Pro)
# Multi-ticker intelligence
POST /api/v1/batch/intelligence {"tickers": ["7203", "6501", "9984"]}
# Multi-ticker disclosures
POST /api/v1/batch/disclosures {"tickers": ["7203", "6501"], "days": 3}
# Bulk ticker resolution
POST /api/v1/batch/tickers {"tickers": ["7203", "6501", "9984"]}AI-Summarized Disclosures (Exclusive)
# English AI summaries + impact scoring for all disclosures
GET /api/v1/disclosures/summarized?days=3&min_impact=3Returns:
{
"ai_summary": {
"summary_en": "Share buyback announced by Toyota, signals undervaluation view",
"impact_score": 4,
"sector_relevance": "Automotive, Manufacturing",
"source": "gemini"
}
}Telemetry
GET /api/v1/telemetry/today # Today's API usage stats
GET /api/v1/telemetry/history # Historical usage (7 days default)Quick Start
# 1. Clone
git clone https://github.com/hiroshic9-png/japan-intelligence-api.git
cd japan-intelligence-api
# 2. Setup
python -m venv venv && source venv/bin/activate
pip install -r requirements.txt
# 3. Configure
cp .env.example .env
# Edit .env with your API keys
# 4. Run
python -m api.main
# → http://localhost:8080/docsEnvironment Variables
Variable | Required | Description |
| Yes | EDINET disclosure API key |
| Yes | Google Gemini API key (Layer 2 interpretation) |
| Yes | gBizINFO API token |
| Yes | e-Stat application ID |
| Yes | J-Quants v2 API key |
| Yes | FRED API key |
| Optional | API authentication key (enables auth when set) |
| Optional | Multi-tier keys: |
API Documentation
Interactive documentation:
Swagger UI: https://japan-intelligence-api.onrender.com/docs
License
Proprietary. All rights reserved.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceProvides AI assistants with access to comprehensive financial data including real-time stock quotes, company fundamentals, financial statements, market analysis, SEC filings, and economic indicators through 253+ tools across 24 categories.Last updated289Apache 2.0
- AlicenseAqualityAmaintenanceJapan Operations OS for AI agents — 14 knowledge domains covering regulations, protocols, calendar, travel, food culture, language, disaster safety, daily life, and persistent memory. 31 MCP tools via REST + Streamable HTTP.Last updated31MIT
- Alicense-qualityCmaintenanceCompound MCP agent that integrates EDINET, TDNET, e-Stat, and stock price sources for comprehensive Japanese company analysis, macro economic snapshots, and earnings monitoring through a single interface.Last updated2Apache 2.0
- Alicense-qualityDmaintenanceProvides 10 financial data tools (market data, economic indicators, news, insider trades, and calendars) via a single MCP layer, enabling any MCP-compatible LLM to access diverse financial data through a unified interface.Last updatedMIT
Related MCP Connectors
Real SEC, 13F, insider, congress & macro data your AI agent can cite. Hosted MCP, 24 tools.
The financial MCP for AI agents - 90+ financial tables, SEC filings, signals, alt-data.
100+ MCP tools for AI agents: content metadata, trade intelligence, business-expertise analysis.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hiroshic9-png/japan-intelligence-api'
If you have feedback or need assistance with the MCP directory API, please join our Discord server