Server data from the Official MCP Registry
~960k Korean corporations, not only listed: official IDs linked, live NTS status, English names
About
~960k Korean corporations, not only listed: official IDs linked, live NTS status, English names
Remote endpoints: streamable-http: https://mcp.jaryo.org
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
7 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"org-jaryo-korean-companies": {
"url": "https://mcp.jaryo.org"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Jaryo MCP - Korean company records
Jaryo (자료, "data" in Korean) is a remote MCP server for looking up Korean companies from public records.
- About 960,000 Korean corporations, not only listed ones.
- Four official numbers linked to each company: business registration number (사업자등록번호), corporate registration number (법인등록번호), DART corp code (DART 고유번호) and stock code (종목코드).
- National Tax Service status, checked live.
- Official English names next to the Korean names.
- Every value carries its source and license. For how fresh each source is, see
https://api.jaryo.org/v1/status.
Facts only — not a credit assessment.
Registry name: org.jaryo/korean-companies · Website: https://jaryo.org
Connect
| URL | https://mcp.jaryo.org |
| Transport | streamable HTTP |
| Auth | Authorization: Bearer <your-key> |
| Key | free at https://jaryo.org/keys/ |
Replace <your-key> with your own key in the examples below.
Claude Desktop
claude_desktop_config.json (uses the mcp-remote bridge, which needs Node.js):
{
"mcpServers": {
"jaryo": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.jaryo.org",
"--header",
"Authorization:${JARYO_AUTH}"
],
"env": { "JARYO_AUTH": "Bearer <your-key>" }
}
}
}
Cursor
~/.cursor/mcp.json:
{
"mcpServers": {
"jaryo": {
"url": "https://mcp.jaryo.org",
"headers": { "Authorization": "Bearer <your-key>" }
}
}
}
VS Code (GitHub Copilot)
.vscode/mcp.json:
{
"servers": {
"jaryo": {
"type": "http",
"url": "https://mcp.jaryo.org",
"headers": { "Authorization": "Bearer <your-key>" }
}
}
}
Tools
Five tools need a key. Two more answer without one: verify_company (a company lookup) and list_sources (the source catalog). All tools are read-only. Responses from the five data tools below and from verify_company carry an attribution list; show it wherever you display the data.
resolve_company
Find the Jaryo company id from a name or an official number. Returns candidates with a confidence value.
Input (any of): name (Korean or English, 2+ characters, or a 6-digit stock code), biz_no (10 digits), corp_reg_no (13 digits), dart_corp_code (8 digits), g2b_vendor_id (KONEPS vendor id, the same number as the business registration number).
{ "biz_no": "124-81-00998" }
Output: candidates[] (up to 10), each with entity_id, confidence, matched_on (which input matched), canonical_name_ko, canonical_name_en; plus attribution[] and notice.
match_companies
Match up to 1,000 rows of your own company list to official numbers. Each row is a string, an object or an array of cells: a name and/or any official number, in any order. Rows are not stored. Each row uses one unit of your daily limit.
{ "rows": ["삼성전자", { "name": "HYBE", "biz_no": "120-86-78223" }, ["카카오", "1208147521"]] }
Output: summary (row counts per result), rows[] with row, result (matched, ambiguous, not_found, not_supported or invalid), match_type, matched_by, entity_id, name, identifiers. Rows with several equally good candidates are answered ambiguous with a candidates list; they are not guessed. Corporations only.
get_company
Company profile by Jaryo id: names (Korean and English), all identifiers, current profile records (DART overview, procurement vendor profile, tax status, pension headcount) and record counts.
{ "id": "<entity_id from resolve_company>" }
Output: id, kind, status (value: active, suspended, closed or unknown, with source_id and fetched_at), names, identifiers, profiles[], record_counts, first_seen, last_seen, attribution[], notice.
list_company_records
Public records attached to a company, newest first, paginated: procurement awards and contracts, sanctions, DART filings, employment (pension headcount), tax status.
{ "id": "<entity_id from resolve_company>", "type": "award", "limit": 20 }
Input: id; optional type (company_profile, vendor_profile, award, contract, filing, employment, status, sanction, corp_outline, corp_code), limit (1-100, default 20), cursor.
Output: company_id, records[] (each with id, record_type, source_id, source_record_key, fetched_at, license_id, data), next_cursor (pass it back as cursor for the next page, null at the end), attribution[], notice.
search_companies
Search by Korean or English name. Up to 20 results.
{ "q": "삼성전자", "limit": 5 }
Input: q (2+ characters; 3+ match any part of a name, 2 match the start of a name), optional limit (1-20).
Output: query, results[] with entity_id, kind, canonical_name_ko, canonical_name_en; plus attribution[] and notice.
Typical flow: resolve_company (or search_companies) to get an entity_id, then get_company and list_company_records.
Limits
Per key: 200 requests per day, 30 per minute, 5 at once. Each tool call counts as 1 request, except match_companies, where each row counts as 1. When a limit is hit the tool returns an error body (RFC 9457 problem JSON) instead of data.
Beta terms
Business use is allowed during the beta (for example counterparty checks, compliance screening, internal tools); reselling, redistributing or bulk-copying the data is not. Show the attribution when you display the data. Full terms: https://jaryo.org/terms/
Sources and licenses
| What | Where |
|---|---|
| Every source, its license, redistribution status and update cadence | https://jaryo.org/licensing/ |
| The same catalog as data | the list_sources tool, or the jaryo://sources resource |
| Field names and code tables | https://jaryo.org/docs/fields/ , or the jaryo://schema resource |
| Attribution text for each value you use | the attribution field of each data tool and verify_company response |
| Source freshness and service status | https://api.jaryo.org/v1/status |
| Terms of use | https://jaryo.org/terms/ |
Links
- Docs: https://jaryo.org/docs/quickstart/
- MCP page: https://jaryo.org/docs/mcp/
- Contact: hello@jaryo.org
Operated by iTBROWN Co., Ltd., Seoul.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
