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
Available components
Last scanned (22 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +1
- Tool “verify_company” rewrote its description, which is the text the model reads security
- 11 Nov 26 +1
- Tool “verify_company” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “match_companies” functional
- 10 Nov 26 0
- 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 security
- Stability: unverified → 0.03 ▲ functional
- “verify_company” reworded the description of “q” cosmetic
- 9 Nov 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.jaryo.org
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jaryo.org | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 98cc177fedac31571369b0825c936ef6 |
| SANs: jaryo.org, mcp.jaryo.org, *.mcp.jaryo.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.jaryo.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| jaryo.org. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jaryo.org | Verified | 200 | |
| http (plaintext) | http://mcp.jaryo.org | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company Get a company profile ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Jaryo entity id (26-char ULID) |
No output schema declared.
No examples provided.
list_company_records List public records of a company ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous page |
| id | string | yes | Jaryo entity id |
| limit | integer | – | – |
| type | string | – | Record type filter |
No output schema declared.
No examples provided.
list_sources List data sources and licenses ~31
Catalog of Korean public data sources Jaryo uses, with license, redistribution status and update cadence. No key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
match_companies Match a list of Korean companies ~215
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/). (회사 목록 맞추기)
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | e.g. ["삼성전자", {"name": "HYBE", "biz_no": "120-86-78223"}, ["카카오", "1208147521"]] |
No output schema declared.
No examples provided.
resolve_company Resolve a Korean company ~205
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/). (한국 회사 찾기)
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
search_companies Search Korean companies by name ~70
Search companies by Korean or English name. Returns up to 20 entities. Requires a Jaryo API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | Name or part of it (2+ characters; 3+ match any part, 2 match the start of a name) |
No output schema declared.
No examples provided.
verify_company Verify a Korean company ~262
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. (한국 법인 확인)
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | 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) |
No output schema declared.
No examples provided.
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.
remote · mcp.jaryo.org
claude mcp add --transport http org-jaryo-korean-companies 'https://mcp.jaryo.org/'
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.