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.

GAJA (가자) - Korea Travel & Measured Visits MCP

REMOTE · GAJA.MOCEAN.KR

Real-world measured visit big data and travel course recommendation MCP for South Korea.

Available components

+3 this week 66 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 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
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 603 tokens (~150/item across 4 items; 4 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

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 →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 18 Nov 26 +46
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.20 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 17 Nov 26 −45
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.13 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 14 Nov 26 +1

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

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 62

    First indexed and scored.

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 21 Nov 2026 · Probed https://gaja.mocean.kr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mocean.kr CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 61d2f68dc55ef4670e279691511face8
SANs: mocean.kr, gaja.mocean.kr, *.gaja.mocean.kr
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 gaja.mocean.kr. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
kr. DS published 64641 13 Verified
mocean.kr. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gaja.mocean.kr/mcp Verified 200
http (plaintext) http://gaja.mocean.kr/mcp Inconclusive 406
MCP tools · 4 exposed · ~603 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
gaja_get_data_freshness ~113

이 서버가 가진 데이터의 기준 시점·집계 구간·표본 수를 돌려준다. Returns the as-of date, coverage window and sample size. [auth] 읽기 · 인증 불필요 [output] {'data_through': 'str', 'covers': 'dict', 'compares': 'dict', 'sample_regions': 'int', 'updated_on': 'str', 'provenance': 'dict'}

NameTypeReqDescription
lang–––

No output schema declared.

No examples provided.

gaja_get_foreign_surge ~127

외국인 방문이 급증한 한국 지역을 돌려준다. 방한 관광 질의에 쓴다. Returns Korean districts with the largest surge in foreign visitors, for inbound-travel questions. [auth] 읽기 · 인증 불필요 [output] {'regions': 'list[{region_cd, region_nm, sido_nm, visitors_cur, visitors_prev, delta, rate}]', 'window': 'dict', 'provenance': 'dict'}

NameTypeReqDescription
lang–––
limit–––
sort–––

No output schema declared.

No examples provided.

gaja_recommend_places ~242

한국 시군구 하나에 대해 실제 방문 데이터로 고른 가볼 만한 곳과 하루 단위 코스(오전·점심·오후·저녁·숙소)를 날씨와 근거와 함께 돌려준다. Returns places worth visiting in one Korean district, chosen from measured visits, plus a day-by-day course with weather and the reasons. [auth] 읽기 · 인증 불필요 [output] {'region': 'dict', 'dates': 'dict', 'places': 'list[{name, category, lat, lon, addr, reason}]', 'days': 'list[{day, items:[{time, name, group, category}], legs:[{mode, minutes, km}]}] (legs[i] = items[i]→items[i+1] 이동)', 'weather': 'list[{day, tmin, tmax, pop, rain_flag}]', 'basis': 'str', 'provenance': 'dict', 'places_source': 'list[str]'}

NameTypeReqDescription
days–––
lang–––
regionstringyes–

No output schema declared.

No examples provided.

gaja_recommend_trending_places ~121

실제 방문 데이터로 요즘 방문이 늘고 있는 한국 지역을 돌려준다. 전국 시군구 단위(서울 외 지역 포함). Returns Korean districts where visits are rising, nationwide — not limited to Seoul. [auth] 읽기 · 인증 불필요 [output] {'places': 'list[{region_cd, region_nm, sido_nm, rate, hot_score, reason}]', 'provenance': 'dict'}

NameTypeReqDescription
lang–––
limit–––
region–––

No output schema declared.

No examples provided.

Install

How do I install the GAJA (가자) - Korea Travel & Measured Visits MCP server?

GAJA (가자) - Korea Travel & Measured Visits MCP is a hosted endpoint at https://gaja.mocean.kr/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 · gaja.mocean.kr

# add to Claude Code
claude mcp add --transport http rlrdus-qq-gaja-mcp 'https://gaja.mocean.kr/mcp'
Common questions

What is the GAJA (가자) - Korea Travel & Measured Visits MCP server?

GAJA (가자) - Korea Travel & Measured Visits MCP is listed in the public MCP registry as io.github.rlrdus-qq/gaja-mcp. Real-world measured visit big data and travel course recommendation MCP for South Korea. This page covers its hosted endpoint (https://gaja.mocean.kr/mcp).

Is the GAJA (가자) - Korea Travel & Measured Visits MCP server safe to use?

GAJA (가자) - Korea Travel & Measured Visits MCP scores 66 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 GAJA (가자) - Korea Travel & Measured Visits MCP server expose?

GAJA (가자) - Korea Travel & Measured Visits MCP exposes 4 tools: gaja_recommend_trending_places, gaja_recommend_places, gaja_get_foreign_surge, gaja_get_data_freshness. Their descriptions and schemas cost roughly 603 tokens of context every time the server is loaded.

Does the GAJA (가자) - Korea Travel & Measured Visits MCP server require authentication?

No. We connected to GAJA (가자) - Korea Travel & Measured Visits MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GAJA (가자) - Korea Travel & Measured Visits MCP server still maintained?

GAJA (가자) - Korea Travel & Measured Visits MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 GAJA (가자) - Korea Travel & Measured Visits MCP server?

VerifyMCP ran 12 checks on GAJA (가자) - Korea Travel & Measured Visits MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about GAJA (가자) - Korea Travel & Measured Visits MCP: HTTPS. 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.