com.kimchi-sushi/agent-mcp
REMOTE · KIMCHI-SUSHI.COM
Korean-Japanese bilingual community. Read public posts/comments, route Korea/Japan queries.
Available components
Last scanned (14 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category News and Social
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 Security80
- 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 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 Usability80
- 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
- Tool/resource definitions use about 335 tokens (~47/item across 7 items; 6 tools + 1 resources), lean.Pass
- 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 Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 6 Nov 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
- 28 Sept 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
- 25 Sept 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
- 26 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 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
- 31 Jul 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
- 30 Jul 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 7 Nov 2026 · Probed https://kimchi-sushi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kimchi-sushi.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 5b063cecf6230470f53e0e81d3ad1a88a30 |
| SANs: kimchi-sushi.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kimchi-sushi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kimchi-sushi.com. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kimchi-sushi.com/mcp | Verified | 200 | |
| http (plaintext) | http://kimchi-sushi.com/mcp | HTTPS enforced | 308 | https://kimchi-sushi.com/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 →
fetch Fetch a KimchiSushi source ~39
Fetch one KimchiSushi citation source or public community post by its opaque search result id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Opaque id returned by search. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_kimchisushi_agent_entrypoints Get KimchiSushi agent entrypoints ~34
Route a Korea/Japan question to KimchiSushi community, guide, or citation-source pages.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | – |
| primary_entrypoints | array | yes | – |
| purpose | string | yes | – |
| service | string | yes | – |
| site | string | yes | – |
No examples provided.
get_post_with_comments Get a KimchiSushi post with comments ~34
Fetch one known public KimchiSushi post and its public comments by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| comment_count | number | yes | – |
| comments | array | yes | – |
| post | object | yes | – |
No examples provided.
get_recent_posts Get recent KimchiSushi posts ~46
Return recent or popular public KimchiSushi community posts without a keyword search.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | number | – | – |
| sort | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| posts | array | yes | – |
No examples provided.
health_check Check KimchiSushi MCP health ~21
Check whether an MCP-compatible client can reach KimchiSushi.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | yes | – |
| ok | boolean | yes | – |
| service | string | yes | – |
No examples provided.
search Search KimchiSushi knowledge ~47
Search KimchiSushi for source-backed Korea/Japan study, working-holiday, or public community information.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural-language search query in Korean, Japanese, or English. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
How do I install the com.kimchi-sushi/agent-mcp server?
com.kimchi-sushi/agent-mcp is a hosted endpoint at https://kimchi-sushi.com/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 · kimchi-sushi.com
claude mcp add --transport http com-kimchi-sushi-agent-mcp 'https://kimchi-sushi.com/mcp'
What is the com.kimchi-sushi/agent-mcp server?
com.kimchi-sushi/agent-mcp is listed in the public MCP registry as com.kimchi-sushi/agent-mcp. Korean-Japanese bilingual community. Read public posts/comments, route Korea/Japan queries. This page covers its hosted endpoint (https://kimchi-sushi.com/mcp).
Is the com.kimchi-sushi/agent-mcp server safe to use?
com.kimchi-sushi/agent-mcp scores 87 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 com.kimchi-sushi/agent-mcp server expose?
com.kimchi-sushi/agent-mcp exposes 6 tools: health_check, get_kimchisushi_agent_entrypoints, search, fetch, get_recent_posts, get_post_with_comments. Their descriptions and schemas cost roughly 221 tokens of context every time the server is loaded.
Does the com.kimchi-sushi/agent-mcp server require authentication?
No. We connected to com.kimchi-sushi/agent-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.kimchi-sushi/agent-mcp server still maintained?
com.kimchi-sushi/agent-mcp is still listed as active in the MCP registry. We last reached this channel on 7 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 com.kimchi-sushi/agent-mcp server?
VerifyMCP ran 13 checks on com.kimchi-sushi/agent-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.