# Jaryo - Korean company records, sourced. Start with verify_company (no key) (remote · mcp.jaryo.org)

\~960k Korean corporations, not only listed: official IDs linked, live NTS status, English names

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.jaryo.org`: 75/100 (this document), [markdown](https://verifymcp.io/servers/org-jaryo-korean-companies/mcp.md), [page](https://verifymcp.io/servers/org-jaryo-korean-companies/mcp)

## Channel facts

- Endpoint: `https://mcp.jaryo.org`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1042 tokens (~115/item across 9 items; 7 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Jaryo - Korean company records, sourced. Start with… MCP server?

Jaryo - Korean company records, sourced. Start with… is a hosted endpoint at https://mcp.jaryo.org/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-jaryo-korean-companies 'https://mcp.jaryo.org/'
```

### Cursor

```json
{
  "mcpServers": {
    "org-jaryo-korean-companies": {
      "url": "https://mcp.jaryo.org/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-jaryo-korean-companies": {
      "type": "http",
      "url": "https://mcp.jaryo.org/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-jaryo-korean-companies]
url = "https://mcp.jaryo.org/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-jaryo-korean-companies": {
      "type": "remote",
      "url": "https://mcp.jaryo.org/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-jaryo-korean-companies --url 'https://mcp.jaryo.org/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-jaryo-korean-companies:
    url: "https://mcp.jaryo.org/"
```

### Netclaw

```json
{
  "McpServers": {
    "org-jaryo-korean-companies": {
      "Transport": "http",
      "Url": "https://mcp.jaryo.org/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-jaryo-korean-companies -t streamable-http -u 'https://mcp.jaryo.org/'
```

### Other

```json
{
  "mcpServers": {
    "org-jaryo-korean-companies": {
      "type": "http",
      "url": "https://mcp.jaryo.org/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 72, +1)

- [security] Tool “verify_company” rewrote its description, which is the text the model reads

### 2026-11-11 (score 71, +1)

- [security] Tool “verify_company” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “match_companies”

### 2026-11-10 (score 70, 0)

- [security] Tool “get_company” rewrote its description, which is the text the model reads
- [security] Tool “list_company_records” rewrote its description, which is the text the model reads
- [security] Tool “resolve_company” rewrote its description, which is the text the model reads
- [security] Tool “search_companies” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “verify_company” reworded the description of “q”

### 2026-11-09 (score 70)

First indexed and scored.

## MCP tools (7)

### `verify_company` (~262 tokens)

Verify a Korean company

Start here. Verify a Korean corporation by name, business registration number (10 digits), corporate registration number (13 digits), DART code (8 digits) or stock code (6 digits): does it exist, its National Tax Service status (active / suspended / closed, with the date it was checked), official numbers, Korean and English names, address, industry and sources. Up to 10 matches, best-known company first; more_matches=true means add the business number or city to narrow. Each match has match_type and former_names (previous names; match_type former_name when the query equals only one of them); name results also have rank_reason (why it is in that place) and the response has ranking. industry.ko / industry.en are official KSIC names (11th revision); industry.tax_business_type is a tax classification, not KSIC. Corporations only — individual businesses are answered as not supported. No scores or judgements. No key needed. (한국 법인 확인)

Input parameters:

- `q` (string, required): Company name (Korean or English), business registration number / 사업자등록번호 (10 digits), corporate registration number / 법인등록번호 (13 digits), DART corp code (8 digits) or stock code (6 digits)

### `resolve_company` (~205 tokens)

Resolve a Korean company

Find the Jaryo entity for a Korean company from its name (Korean or English) or an official identifier: business registration number (biz_no, 10 digits), corporate registration number (corp_reg_no, 13 digits), DART corp code (8 digits) or KONEPS vendor id. Returns candidates with confidence. Requires a Jaryo API key (free: https://jaryo.org/keys/). (한국 회사 찾기)

Input parameters:

- `biz_no` (string): 사업자등록번호, 10 digits, hyphens allowed
- `corp_reg_no` (string): 법인등록번호, 13 digits
- `dart_corp_code` (string): DART 고유번호, 8 digits
- `g2b_vendor_id` (string): KONEPS (나라장터) vendor id = business registration number
- `name` (string): Company name, Korean or English (2+ characters), or a stock code (6 digits)

### `match_companies` (~215 tokens)

Match a list of Korean companies

Match up to 1,000 rows of your own company list to official Korean identifiers. Each row is a string or an object/array of cells — a company name and/or a business registration number (10 digits), corporate registration number (13), DART code (8) or stock code (6), in any order. Returns per row: result (matched / ambiguous / not_found / not_supported / invalid), match_type, entity_id, official numbers and the official English name; several equally good candidates are answered as ambiguous, not guessed. Identifiers only (tax status is free at verify_company). Rows are not stored. Each row uses one unit of your daily limit. Requires a Jaryo API key (free: https://jaryo.org/keys/). (회사 목록 맞추기)

Input parameters:

- `rows` (array, required): e.g. ["삼성전자", {"name": "HYBE", "biz_no": "120-86-78223"}, ["카카오", "1208147521"]]

### `get_company` (~77 tokens)

Get a company profile

Company profile by Jaryo id: names (ko/en), all identifiers, current profile records (DART overview, procurement vendor profile, tax status, pension headcount) and record counts. Every value carries its source and license. Requires a Jaryo API key.

Input parameters:

- `id` (string, required): Jaryo entity id (26-char ULID)

### `list_company_records` (~92 tokens)

List public records of a company

Public records attached to a company: procurement awards and contracts, sanctions, DART filings, employment (pension headcount), tax status. Newest first, paginated. Requires a Jaryo API key.

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `id` (string, required): Jaryo entity id
- `limit` (integer)
- `type` (string): Record type filter

### `search_companies` (~70 tokens)

Search Korean companies by name

Search companies by Korean or English name. Returns up to 20 entities. Requires a Jaryo API key.

Input parameters:

- `limit` (integer)
- `q` (string, required): Name or part of it (2+ characters; 3+ match any part, 2 match the start of a name)

### `list_sources` (~31 tokens)

List data sources and licenses

Catalog of Korean public data sources Jaryo uses, with license, redistribution status and update cadence. No key needed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-jaryo-korean-companies/mcp#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 70
- 2026-11-09: 70

## Common questions

### What is the Jaryo - Korean company records, sourced. Start with… MCP server?

Jaryo - Korean company records, sourced. Start with… is an MCP server listed in the public MCP registry as org.jaryo/korean-companies. ~960k Korean corporations, not only listed: official IDs linked, live NTS status, English names. This page covers its hosted endpoint (https://mcp.jaryo.org).

### Is the Jaryo - Korean company records, sourced. Start with… MCP server safe to use?

Jaryo - Korean company records, sourced. Start with… scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Jaryo - Korean company records, sourced. Start with… MCP server expose?

Jaryo - Korean company records, sourced. Start with… exposes 7 tools: verify_company, resolve_company, match_companies, get_company, list_company_records, and 2 more. Their descriptions and schemas cost roughly 952 tokens of context every time the server is loaded.

### Does the Jaryo - Korean company records, sourced. Start with… MCP server require authentication?

No. We connected to Jaryo - Korean company records, sourced. Start with… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Jaryo - Korean company records, sourced. Start with… MCP server still maintained?

Jaryo - Korean company records, sourced. Start with… is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Jaryo - Korean company records, sourced. Start with… MCP server?

VerifyMCP ran 12 checks on Jaryo - Korean company records, sourced. Start with…, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Jaryo - Korean company records, sourced. Start with…: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.jaryo.org/
- Repository: https://github.com/windmarks74/jaryo-mcp
- Website: https://jaryo.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-jaryo-korean-companies/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-jaryo-korean-companies/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-jaryo-korean-companies/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-jaryo-korean-companies/mcp
