Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

K-AgentPay: Korea travel & K-pop data

REMOTE · API.K-AGENTPAY.COM

Korea travel & K-pop live data for agents: concerts, Seoul trip packs, crowd, subway, airport.

+4 this week 74 Trust /100

Last scanned (2 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 512 tokens (~56/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://api.k-agentpay.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.k-agentpay.com CN=YE2,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 6b1a5caec0070f5c158d6a817ef0bccc734
SANs: api.k-agentpay.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.k-agentpay.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
k-agentpay.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=31536000
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.k-agentpay.com/mcp Verified 200
http (plaintext) http://api.k-agentpay.com/mcp HTTPS enforced 308 https://api.k-agentpay.com/mcp
MCP tools · 9 exposed · ~512 tokens

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 →

Tool Tokens
incheon_airport_wait ~58

Live Incheon Airport departure-hall waiting minutes and queue per hall (T1/T2) and the shortest hall. 10 free calls/day.

NameTypeReqDescription
langstring–answer language: en (default), ja or ko

No output schema declared.

No examples provided.

korea_festivals ~53

Festivals and events in Korea from a date (YYYYMMDD). 10 free calls/day.

NameTypeReqDescription
fromstring––
langstring–answer language: en (default), ja or ko

No output schema declared.

No examples provided.

kpop_new_concerts ~73

Concerts in Korea newly registered or updated since a date (YYYYMMDD, default 7 days), optional artist. 10 free calls/day.

NameTypeReqDescription
langstring–answer language: en (default), ja or ko
qstring––
sincestring––

No output schema declared.

No examples provided.

kpop_search ~64

Free. Search K-pop / pop concerts in Korea for the next 6 months by artist or title (any language). Returns concert ids.

NameTypeReqDescription
langstring–answer language: en (default), ja or ko
qstringyesartist or title

No output schema declared.

No examples provided.

request_korea_data ~44

Free. Ask for Korea data these tools don't cover yet; the most requested is added first.

NameTypeReqDescription
useCasestring––
wantstringyes–

No output schema declared.

No examples provided.

seoul_now ~66

Live crowd level, 12-hour crowd forecast and weather for a Seoul place (e.g. Myeongdong, Hongdae). 10 free calls/day.

NameTypeReqDescription
langstring–answer language: en (default), ja or ko
placestringyes–

No output schema declared.

No examples provided.

seoul_places ~43

Free. The 121 Seoul places (with codes) accepted by seoul_now.

NameTypeReqDescription
langstring–answer language: en (default), ja or ko

No output schema declared.

No examples provided.

seoul_subway_now ~59

Next trains at a Seoul subway station right now (station in English, Japanese or Korean). 10 free calls/day.

NameTypeReqDescription
langstring–answer language: en (default), ja or ko
stationstringyes–

No output schema declared.

No examples provided.

seoul_trip_pack ~52

Seoul concert trip pack (tickets, venue, last trains, crowd, hotels/food nearby) — paid only: returns how to buy it.

NameTypeReqDescription
idstringyesconcert id from kpop_search

No output schema declared.

No examples provided.

Install

How do I install the K-AgentPay: Korea travel & K-pop data MCP server?

K-AgentPay: Korea travel & K-pop data is a hosted endpoint at https://api.k-agentpay.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 · api.k-agentpay.com

# add to Claude Code
claude mcp add --transport http com-k-agentpay-kaia-x402 'https://api.k-agentpay.com/mcp'
Common questions

What is the K-AgentPay: Korea travel & K-pop data MCP server?

K-AgentPay: Korea travel & K-pop data is an MCP server listed in the public MCP registry as com.k-agentpay/kaia-x402. Korea travel & K-pop live data for agents: concerts, Seoul trip packs, crowd, subway, airport. This page covers its hosted endpoint (https://api.k-agentpay.com/mcp).

Is the K-AgentPay: Korea travel & K-pop data MCP server safe to use?

K-AgentPay: Korea travel & K-pop data scores 74 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 K-AgentPay: Korea travel & K-pop data MCP server expose?

K-AgentPay: Korea travel & K-pop data exposes 9 tools: kpop_search, seoul_places, request_korea_data, incheon_airport_wait, seoul_subway_now, and 4 more. Their descriptions and schemas cost roughly 512 tokens of context every time the server is loaded.

Does the K-AgentPay: Korea travel & K-pop data MCP server require authentication?

No. We connected to K-AgentPay: Korea travel & K-pop data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the K-AgentPay: Korea travel & K-pop data MCP server still maintained?

K-AgentPay: Korea travel & K-pop data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.