japan-intelligence-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JI_API_KEY | No | API authentication key (enables auth when set) | |
| JI_API_KEYS | No | Multi-tier keys: {"key": "tier"} | |
| ESTAT_APP_ID | Yes | e-Stat application ID | |
| FRED_API_KEY | Yes | FRED API key | |
| EDINET_API_KEY | Yes | EDINET disclosure API key | |
| GBIZ_API_TOKEN | Yes | gBizINFO API token | |
| GEMINI_API_KEY | Yes | Google Gemini API key (Layer 2 interpretation) | |
| JQUANTS_API_KEY | Yes | J-Quants v2 API key | |
| JAPAN_INTELLIGENCE_API_URL | No | The URL of the Japan Intelligence API | https://japan-intelligence-api.onrender.com |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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