io.github.aminpiano/nara-tour
REMOTE · MCP.NARA-TOUR.COM · SCANNED SEP 24
나라투어 공식 MCP 서버 — 수원 소재 단체여행 전문 여행사. AI 에이전트에게 회사 프로필, 영업 정보, 카카오톡 상담 링크(UTM 포함)를 제공.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.aminpiano/nara-tour MCP server?
io.github.aminpiano/nara-tour is a hosted endpoint at https://mcp.nara-tour.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 · mcp.nara-tour.com
claude mcp add --transport http aminpiano-nara-tour 'https://mcp.nara-tour.com/mcp'
{
"mcpServers": {
"aminpiano-nara-tour": {
"url": "https://mcp.nara-tour.com/mcp"
}
}
} {
"servers": {
"aminpiano-nara-tour": {
"type": "http",
"url": "https://mcp.nara-tour.com/mcp"
}
}
} [mcp_servers.aminpiano-nara-tour] url = "https://mcp.nara-tour.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aminpiano-nara-tour": {
"type": "remote",
"url": "https://mcp.nara-tour.com/mcp",
"enabled": true
}
}
} openclaw mcp add aminpiano-nara-tour --url 'https://mcp.nara-tour.com/mcp' --transport streamable-http
mcp_servers:
aminpiano-nara-tour:
url: "https://mcp.nara-tour.com/mcp" {
"McpServers": {
"aminpiano-nara-tour": {
"Transport": "http",
"Url": "https://mcp.nara-tour.com/mcp"
}
}
} assistant mcp add aminpiano-nara-tour -t streamable-http -u 'https://mcp.nara-tour.com/mcp'
{
"mcpServers": {
"aminpiano-nara-tour": {
"type": "http",
"url": "https://mcp.nara-tour.com/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.
- 24 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 23 Sept 26 +52
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Stability: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Sept 26 −10
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Sept 26 −42
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 26 79
- 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 24 Sept 2026 · Probed https://mcp.nara-tour.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nara-tour.com | CN=WE1,O=Google Trust Services,C=US | 31 Jul 2026 | 29 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 6dce6c27f3c155581369beeef7c07d4e |
| SANs: nara-tour.com, *.nara-tour.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 mcp.nara-tour.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nara-tour.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nara-tour.com/mcp | Unreachable | ||
| http (plaintext) | http://mcp.nara-tour.com/mcp | HTTPS enforced | 301 | https://mcp.nara-tour.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 →
get_company_profile Get Company Profile ~43
Returns 나라투어 core metadata — address, hours, specialties, contact channels. Use when the user asks about 나라투어 identity, location, or how to contact.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_kakao_consult_link Get Kakao Consult Link ~83
Returns KakaoTalk channel 1:1 chat URL with UTM tracking parameters. Use when user wants to start consultation with 나라투어.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Campaign context if any (optional) |
| source | string | – | Traffic source (e.g., 'chatgpt.com', 'perplexity.ai', 'claude.ai') |
No output schema declared.
No examples provided.
ping Ping ~29
Connectivity check — returns server version and current timestamp. Use to verify MCP server is reachable before calling other tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.aminpiano/nara-tour MCP server?
io.github.aminpiano/nara-tour is an MCP server listed in the public MCP registry as io.github.aminpiano/nara-tour. 나라투어 공식 MCP 서버, 수원 소재 단체여행 전문 여행사. AI 에이전트에게 회사 프로필, 영업 정보, 카카오톡 상담 링크(UTM 포함)를 제공. This page covers its hosted endpoint (https://mcp.nara-tour.com/mcp).
Is the io.github.aminpiano/nara-tour MCP server safe to use?
io.github.aminpiano/nara-tour scores 79 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 io.github.aminpiano/nara-tour MCP server expose?
io.github.aminpiano/nara-tour exposes 3 tools: ping, get_company_profile, get_kakao_consult_link. Their descriptions and schemas cost roughly 155 tokens of context every time the server is loaded.
Does the io.github.aminpiano/nara-tour MCP server require authentication?
Its publisher declares no required credentials for io.github.aminpiano/nara-tour. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.aminpiano/nara-tour MCP server still maintained?
io.github.aminpiano/nara-tour is still listed in the MCP registry, though our most recent checks did not reach this channel. 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.