io.github.Kotaro-Studio/kuongeo
REMOTE · KUONGEO.COM
Japan: next bus/tram/boat from 26 places, RTK bases, JMA warnings, municipality facts. No key.
Available components
Last scanned (3 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security46
- 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 7 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1074 tokens (~153/item across 7 items; 7 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 Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% 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 7 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 17 Oct 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.
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 77. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 57 to 70. That category is still filling its 30-day observation window: 17 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.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 57. That category is still filling its 30-day observation window: 15 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.
- 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
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://kuongeo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kuongeo.com | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f3ccc0f1a8d9612d0e144ef8572942e3 |
| SANs: kuongeo.com, *.kuongeo.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 kuongeo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| kuongeo.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kuongeo.com/mcp | Verified | 200 | |
| http (plaintext) | http://kuongeo.com/mcp | Served over HTTP | 200 |
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 →
answer One-shot answer for a place in Japan ~141
Give a place name in Japanese or English (e.g. 帯広, Obihiro, 京都市 の基準局, 札幌の警報). Returns in one call: the municipality (5-digit code), JMA warnings in force, the nearest free RTK base station (km, mountpoint, host) and the page URLs. No key. Use this first when a user asks about a Japanese place; call here/rtk_bases_near for detail.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| q | string | yes | place name, Japanese or English. Extra words like 基準局/警報/near are fine |
No output schema declared.
No examples provided.
gnss_in_japan GNSS in Japan guide index ~81
Index of the English field guide for engineers using GNSS in Japan: QZSS status, CLAS, MADOCA-PPP, GEONET and community bases, coordinates and heights (JGD2011/JGD2024), bringing equipment and radio law. Returns titles, one-line summaries and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
No output schema declared.
No examples provided.
here Here, now (Japan) ~205
For one point in Japan: municipality and its 5-digit code, JMA warnings and advisories in force (with English names), nearest AMeDAS observation, heat (WBGT), earthquakes within 300 km, hazard zones (flood, tsunami, storm surge, landslide), elevation, nearest free RTK base, furusato-nozei prices for the municipality and the cost of living of the matching surveyed city (rent, utilities, staples; Statistics Bureau monthly survey) from kurashigram.com. Same as GET https://kuongeo.com/api/here. Warnings are relayed from JMA, not issued here.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| lat | number | yes | latitude (20 to 46) |
| lon | number | yes | longitude (122 to 154) |
| sections | string | – | comma list of muni,warnings,observation,earthquakes,hazards,heat,elevation,rtk,prices (default all) |
No output schema declared.
No examples provided.
kurashigram_prices kurashigram prices for a municipality ~75
Furusato-nozei return goods listed by a Japanese municipality on Rakuten, normalised to grams per 10,000 yen of donation, from kurashigram.com (CC BY 4.0). Keyed by the same 5-digit municipality code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 5-digit municipality code |
No output schema declared.
No examples provided.
next_departures Next bus, tram, monorail or boat from a place in Japan (KUON GEO NEXT) ~213
For travellers in Japan. Give a place or sight in Japanese or English (e.g. Miyajima, 宮島, Naoshima ferry, Shirakawa-go bus, Churaumi, Aso crater, Kumamoto Station, Toyama Station tram, Ise Jingu, Naha Airport). Returns in one call: the next boat (time, minutes to go, operator, last boat today) and the next bus/tram/monorail (time, minutes, route, destination, stop number, live or timetable), the page URL and the JSON URL. Covers Hiroshima, Kumamoto, Okayama/Uno Port, Toyama/Shirakawa-go, Ise/Toba and Okinawa (26 places, 2026-09). Live positions only where operators publish them; boats are timetables. No key.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| q | string | yes | place or sight, Japanese or English; extra words like next/ferry/bus are fine |
No output schema declared.
No examples provided.
place Municipality page data ~98
Static facts for a municipality of Japan by 5-digit code (JIS X 0402): names (ja/en), prefecture, population (2020 census), JMA warning area and region, centre point, and the URL of its page on kuongeo.com. Use the here tool with the centre point for live values.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 5-digit municipality code, e.g. 01207 (Obihiro) |
No output schema declared.
No examples provided.
rtk_bases_near Nearest free RTK base stations ~69
Nearest online community RTK base stations (NTRIP) to a point, worldwide, from KUON GEO's 10-minute polling. Returns mountpoint, host, distance in km and a baseline grade.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | – |
| lon | number | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.Kotaro-Studio/kuongeo MCP server?
io.github.Kotaro-Studio/kuongeo is a hosted endpoint at https://kuongeo.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 · kuongeo.com
claude mcp add --transport http kotaro-studio-kuongeo 'https://kuongeo.com/mcp'
What is the io.github.Kotaro-Studio/kuongeo MCP server?
io.github.Kotaro-Studio/kuongeo is an MCP server listed in the public MCP registry as io.github.Kotaro-Studio/kuongeo. Japan: next bus/tram/boat from 26 places, RTK bases, JMA warnings, municipality facts. No key. This page covers its hosted endpoint (https://kuongeo.com/mcp).
Is the io.github.Kotaro-Studio/kuongeo MCP server safe to use?
io.github.Kotaro-Studio/kuongeo scores 69 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.Kotaro-Studio/kuongeo MCP server expose?
io.github.Kotaro-Studio/kuongeo exposes 7 tools: next_departures, answer, here, place, rtk_bases_near, and 2 more. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.
Does the io.github.Kotaro-Studio/kuongeo MCP server require authentication?
No. We connected to io.github.Kotaro-Studio/kuongeo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Kotaro-Studio/kuongeo MCP server still maintained?
io.github.Kotaro-Studio/kuongeo 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.