io.github.Kotaro-Studio/kuongeo
REMOTE · KUONGEO.COM · SCANNED SEP 20
GNSS/RTK and weather archive for Japan: nearest RTK bases, municipality facts, JMA warnings. No key.
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 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 5 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 598 tokens (~119/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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'
{
"mcpServers": {
"kotaro-studio-kuongeo": {
"url": "https://kuongeo.com/mcp"
}
}
} {
"servers": {
"kotaro-studio-kuongeo": {
"type": "http",
"url": "https://kuongeo.com/mcp"
}
}
} [mcp_servers.kotaro-studio-kuongeo] url = "https://kuongeo.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kotaro-studio-kuongeo": {
"type": "remote",
"url": "https://kuongeo.com/mcp",
"enabled": true
}
}
} openclaw mcp add kotaro-studio-kuongeo --url 'https://kuongeo.com/mcp' --transport streamable-http
mcp_servers:
kotaro-studio-kuongeo:
url: "https://kuongeo.com/mcp" {
"McpServers": {
"kotaro-studio-kuongeo": {
"Transport": "http",
"Url": "https://kuongeo.com/mcp"
}
}
} assistant mcp add kotaro-studio-kuongeo -t streamable-http -u 'https://kuongeo.com/mcp'
{
"mcpServers": {
"kotaro-studio-kuongeo": {
"type": "http",
"url": "https://kuongeo.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.
- 20 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 57
First indexed and scored.
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 20 Sept 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 | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3fa4151d91781e7413a294a793bf1339 |
| 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 →
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.
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.
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. GNSS/RTK and weather archive for Japan: nearest RTK bases, municipality facts, JMA warnings. 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 58 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 5 tools: here, place, rtk_bases_near, kurashigram_prices, gnss_in_japan. Their descriptions and schemas cost roughly 528 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.