Reference Source · MCP server health

io.github.kr-data-api/korea-data

7 endpoints on the official MCP registry. Probed daily.

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of the last 7 probes · 0% of the last 30
Handshake latencymedian 39 ms, 95th 39 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check,kr-data/korea-ecommerce-seller-registry

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of the last 7 probes · 0% of the last 30
Handshake latencymedian 39 ms, 95th 39 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check,kr-data/korea-ecommerce-seller-registry,kr-data/korea-health-recalls

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of the last 7 probes · 0% of the last 30
Handshake latencymedian 41 ms, 95th 41 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check,kr-data/korea-ecommerce-seller-registry,kr-data/korea-health-recalls,kr-data/korea-company-headcount,kr-data/korea-financial-institution-registry

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of the last 7 probes · 0% of the last 30
Handshake latencymedian 40 ms, 95th 40 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check,kr-data/korea-ecommerce-seller-registry,kr-data/korea-health-recalls,kr-data/korea-company-headcount,kr-data/korea-financial-institution-registry,kr-data/korea-hs-import-requirements

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of the last 7 probes · 0% of the last 30
Handshake latencymedian 43 ms, 95th 43 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check,kr-data/korea-ecommerce-seller-registry,kr-data/korea-health-recalls,kr-data/korea-company-headcount,kr-data/korea-financial-institution-registry,kr-data/korea-hs-import-requirements,kr-data/korea-medical-device-approval

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of the last 7 probes · 0% of the last 30
Handshake latencymedian 44 ms, 95th 44 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

https://mcp.apify.com?tools=kr-data/korea-business-verify,kr-data/korea-address,kr-data/korea-law,kr-data/korea-flood-car-check,kr-data/korea-ecommerce-seller-registry,kr-data/korea-health-recalls,kr-data/korea-company-headcount,kr-data/korea-financial-institution-registry,kr-data/korea-hs-import-requirements,kr-data/korea-medical-device-approval,kr-data/korea-apt-transactions

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions0% of the last 7 probes · 0% of the last 30
Handshake latencymedian 91 ms, 95th 3665 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

Embed the badge

[![MCP](https://referencesource.org/mcp-health/badge/io-github-kr-data-api-korea-data.svg)](https://referencesource.org/mcp-health/server/io-github-kr-data-api-korea-data/)

The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key. This entry publishes 7 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.

What was actually measured

One HTTP POST carrying a JSON-RPC initialize, and if that succeeds, a tools/list. Nothing here is a score, a rating or a judgement about whether the server is any good — only whether an ordinary MCP client could complete a session with it on the day we asked. “Needs credentials” is not a fault: it means the endpoint wants an account, which is a perfectly reasonable thing for it to want.

The tool contract row is a digest of what tools/list returned — each tool's name, description and input schema, hashed — so that a rename, a newly-required field or a rewritten description can be spotted even though none of them breaks the connection. We keep the digests and nothing else: no tool name, description or schema of anybody's is stored or republished here, which is also why this can say that a contract moved and by how much, but not what it now says.

The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]