Server data from the Official MCP Registry
56 MCP tools for 16 Korean public-data sources. Free 100/day per IP, Pro $29/mo unified key.
56 MCP tools for 16 Korean public-data sources. Free 100/day per IP, Pro $29/mo unified key.
This is a well-structured collection of thin MCP wrapper servers for Korean public data APIs. The code is clean, properly handles errors, and uses standard authentication patterns (environment variables for API keys). No hardcoded secrets or dangerous patterns detected. Minor code quality issues around broad exception handling and some input validation gaps do not significantly impact the security posture. Permissions (network HTTP, env vars) are appropriate for the stated purpose of proxying public data APIs. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
7 files analyzed · 9 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: VIVORY_API_KEY
Environment variable: VIVORY_API_BASE
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-jayjodev-vivory-mcp-korea": {
"env": {
"VIVORY_API_KEY": "your-vivory-api-key-here",
"VIVORY_API_BASE": "your-vivory-api-base-here"
},
"args": [
"vivory-mcp-korea"
],
"command": "uvx"
}
}
}From the project's GitHub README.
Korean public-data MCP servers for AI agents — KOSIS Statistics Korea (live), BoK ECOS · NEIS · LOCALDATA (planned).
Built and maintained by Vivory. Backend powered by the Vivory Korea Data Gateway.
Korean public statistics (population, GDP, CPI, employment, trade, etc.) are published by official agencies via Korean-only APIs that require local accounts and return JS-literal responses with mixed taxonomies. This repo packages them as Model Context Protocol servers so any MCP-compatible client (Claude Desktop, Claude Code, etc.) can query Korean data in English with zero setup.
Foreign user → Claude → vivory-mcp-* → api.vivory.app → kosis.kr / ecos.bok.or.kr / etc.
(caching, attribution, normalization)
No KOSIS account, no API key, no Korean phone — just install and ask.
This is a monorepo of MCP server packages. Each is independently installable from PyPI.
| Package | Status | Tools | Source |
|---|---|---|---|
vivory-mcp-kosis | Live | 15 | KOSIS — Statistics Korea curated key indicators |
vivory-mcp-korea | Live (KOSIS only) | 15 | Umbrella — adds BoK ECOS, NEIS, LOCALDATA, etc. as v0.2+ |
vivory-mcp-kosis)vivory-mcp-korea) — auto-grows as we add sourcesEdit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"vivory-kosis": {
"command": "uvx",
"args": ["vivory-mcp-kosis"]
}
}
}
Or to use the umbrella (all Korean data):
{
"mcpServers": {
"vivory-korea": {
"command": "uvx",
"args": ["vivory-mcp-korea"]
}
}
}
Restart Claude Desktop. The tools appear in the tool palette.
PyPI release pending — until then use:
uvx --from "git+https://github.com/jayjodev/vivory-mcp.git#subdirectory=packages/mcp-server-kosis" vivory-mcp-kosis
Ask Claude (or any MCP client):
"What's Korea's CPI trend over the last 24 months?" "Show me Korean quarterly GDP growth, last 12 quarters." "Search KOSIS for tables related to youth unemployment." "What's the indicator ID for 추계인구?"
Claude picks the right tool automatically.
packages/
├── mcp-server-kosis/ # KOSIS standalone MCP server
│ ├── src/vivory_mcp_kosis/
│ │ ├── server.py # 15 KOSIS tool definitions
│ │ └── client.py # HTTP wrapper to api.vivory.app
│ ├── pyproject.toml
│ └── README.md
│
└── mcp-server-korea/ # Umbrella MCP server
├── src/vivory_mcp_korea/
│ ├── server.py # Aggregates tools from all sources
│ ├── client.py
│ └── tools/
│ ├── kosis.py # KOSIS tool catalog
│ └── (ecos.py, neis.py, etc. — planned)
└── ...
All packages are thin wrappers — no API keys, no rate limit handling, no parsing logic. They translate MCP tool calls → HTTP GETs against api.vivory.app, where the heavy lifting lives.
Set VIVORY_API_BASE to point at your own backend:
export VIVORY_API_BASE="http://localhost:8000/api"
The Vivory backend code is not in this repo (it lives in the private Vivory app monorepo). If you want to run the full stack, you'll need to implement the /api/public-tools/kosis/* endpoints yourself or contact us about licensing.
Every tool response includes an attribution block. When citing or redistributing data, include the attribution_required text.
Issues and PRs welcome. Specifically interested in:
vivory-mcp) — packages here mirror what's published to PyPI🇰🇷 Built in Seoul · 🌐 vivory.app
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.