https://mcp.apify.com/?tools=leoworks/naver-shopping-rank-tracker,leoworks/naver-blog-brand-monitor,leoworks/naver-ai-briefing-monitor,leoworks/korean-review-classifier,leoworks/kbeauty-ranking-review-monitor,leoworks/aliexpress-reviews-classifier,leoworks/aliexpress-search-scraperneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | — of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 41 ms, 95th 62 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
https://mcp.apify.com/?tools=leoworks/naver-shopping-rank-tracker,leoworks/naver-blog-brand-monitor,leoworks/naver-ai-briefing-monitor,leoworks/korean-review-classifier,leoworks/kbeauty-ranking-review-monitor,leoworks/aliexpress-reviews-classifier,leoworks/aliexpress-search-scraper,leoworks/social-comment-classifier,leoworks/japanese-review-classifier,leoworks/spanish-review-classifierneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | — of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 57 ms, 95th 1041 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
https://mcp.apify.com/?tools=leoworks/naver-shopping-rank-tracker,leoworks/naver-blog-brand-monitor,leoworks/naver-ai-briefing-monitor,leoworks/korean-review-classifier,leoworks/kbeauty-ranking-review-monitor,leoworks/aliexpress-reviews-classifier,leoworks/aliexpress-search-scraper,leoworks/social-comment-classifier,leoworks/japanese-review-classifier,leoworks/spanish-review-classifier,leoworks/google-maps-review-classifier,leoworks/google-maps-lead-qualifier,leoworks/amazon-review-classifier,leoworks/job-posting-classifier,leoworks/company-website-classifierneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 3704 ms, 95th 3704 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
https://mcp.apify.com/?tools=leoworks/naver-shopping-rank-tracker,leoworks/naver-blog-brand-monitor,leoworks/naver-ai-briefing-monitor,leoworks/korean-review-classifier,leoworks/kbeauty-ranking-review-monitor,leoworks/aliexpress-reviews-classifier,leoworks/aliexpress-search-scraper,leoworks/social-comment-classifier,leoworks/japanese-review-classifier,leoworks/spanish-review-classifier,leoworks/google-maps-review-classifier,leoworks/google-maps-lead-qualifier,leoworks/amazon-review-classifier,leoworks/job-posting-classifier,leoworks/company-website-classifier,leoworks/naver-place-review-classifier,leoworks/google-maps-review-health-checkneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 42 ms, 95th 776 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
[](https://referencesource.org/mcp-health/server/io-github-illee-leoworks-data-tools/)
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 4 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.
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]