saaskr — Korean SaaS Directory (한국 SaaS 디렉토리)
REMOTE · SAASKR.COM · SCANNED SEP 23
Search and compare SaaS built in South Korea. 3,800+ services, liveness-checked weekly.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 657 tokens (~131/item across 5 items; 5 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) MCP server?
saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) is a hosted endpoint at https://saaskr.com/api/mcp, 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 · saaskr.com
claude mcp add --transport http com-saaskr-korean-saas-directory 'https://saaskr.com/api/mcp'
{
"mcpServers": {
"com-saaskr-korean-saas-directory": {
"url": "https://saaskr.com/api/mcp"
}
}
} {
"servers": {
"com-saaskr-korean-saas-directory": {
"type": "http",
"url": "https://saaskr.com/api/mcp"
}
}
} [mcp_servers.com-saaskr-korean-saas-directory] url = "https://saaskr.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-saaskr-korean-saas-directory": {
"type": "remote",
"url": "https://saaskr.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-saaskr-korean-saas-directory --url 'https://saaskr.com/api/mcp' --transport streamable-http
mcp_servers:
com-saaskr-korean-saas-directory:
url: "https://saaskr.com/api/mcp" {
"McpServers": {
"com-saaskr-korean-saas-directory": {
"Transport": "http",
"Url": "https://saaskr.com/api/mcp"
}
}
} assistant mcp add com-saaskr-korean-saas-directory -t streamable-http -u 'https://saaskr.com/api/mcp'
{
"mcpServers": {
"com-saaskr-korean-saas-directory": {
"type": "http",
"url": "https://saaskr.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 23 Sept 2026 · Probed https://saaskr.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saaskr.com | CN=WE1,O=Google Trust Services,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 1e335b93305a6a930e7c0de2a6990468 |
| SANs: saaskr.com, *.saaskr.com | ||||||
| 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 saaskr.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| saaskr.com. | absent | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://saaskr.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://saaskr.com/api/mcp | HTTPS enforced | 308 | https://saaskr.com/api/mcp |
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 →
compare_korean_saas ~63
한국 SaaS 두 개를 나란히 비교한다(카테고리·운영 상태·인기도·소개).
| Name | Type | Req | Description |
|---|---|---|---|
| slug_a | string | yes | 첫 번째 SaaS slug |
| slug_b | string | yes | 두 번째 SaaS slug |
No output schema declared.
No examples provided.
get_korean_saas ~57
특정 한국 SaaS의 상세 정보(소개·카테고리·공식 사이트·운영 상태·후기)를 가져온다.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | search_korean_saas 가 반환한 slug |
No output schema declared.
No examples provided.
list_saas_categories ~37
한국 SaaS 카테고리 16개와 각 카테고리의 서비스 수, 고르는 기준을 반환한다.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_korean_saas ~174
한국에서 만든 SaaS를 검색한다. 이름·태그라인·소개·태그를 대상으로 하며, 운영 중이 확인된 서비스만 반환한다. 카테고리로 좁힐 수 있다. "한국 AI 도구", "국산 협업툴" 같은 요청에 사용.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 카테고리 slug로 좁히기. 가능한 값: ai, productivity, social, design, developer-tools, marketing, fintech, ecommerce, education, health, media, lifestyle, hr, gaming, travel, food |
| limit | number | – | 최대 결과 수(기본 10, 최대 30) |
| query | string | – | 검색어(한국어). 예: "회의록", "결제", "디자인" |
No output schema declared.
No examples provided.
submit_korean_saas ~269
내가 만든 SaaS를 saaskr 디렉토리에 등록한다. 사용자가 "내 서비스 등록해줘", "saaskr에 올려줘"라고 할 때 사용. 이미 등록된 서비스면 기존 페이지를 알려주고, 새 서비스면 심사 큐에 넣는다(링크가 살아있는지 등 자동 검증 후 발행). 등록 전 사용자에게 이름·URL·한 줄 설명을 확인받고, 소개는 사용자가 준 정보로만 채운다(임의로 지어내지 말 것).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 카테고리 slug(선택). 가능한 값: ai, productivity, social, design, developer-tools, marketing, fintech, ecommerce, education, health, media, lifestyle, hr, gaming, travel, food |
| description | string | – | 서비스 소개(선택, 4000자 이내) |
| is_owner | boolean | – | 본인이 만든 서비스면 true |
| name | string | yes | 서비스 이름 |
| submitter_email | string | – | 연락받을 이메일(선택) |
| tagline | string | yes | 한 줄 설명(5자 이상, 200자 이내) |
| website_url | string | yes | 서비스 공식 URL (https:// 로 시작) |
No output schema declared.
No examples provided.
What is the saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) MCP server?
saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) is an MCP server listed in the public MCP registry as com.saaskr/korean-saas-directory. Search and compare SaaS built in South Korea. 3,800+ services, liveness-checked weekly. This page covers its hosted endpoint (https://saaskr.com/api/mcp).
Is the saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) MCP server safe to use?
saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) scores 80 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 saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) MCP server expose?
saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) exposes 5 tools: search_korean_saas, get_korean_saas, list_saas_categories, compare_korean_saas, submit_korean_saas. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Does the saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) MCP server require authentication?
No. We connected to saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) MCP server still maintained?
saaskr — Korean SaaS Directory (한국 SaaS 디렉토리) is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.