_ registry / mcp streamable-http · checked 2h ago

kuongeo

https://kuongeo.com

Registry code: c47181ff9a21d0fd

api record

Tools for Japan: next_departures (next bus, tram, monorail or boat from a place: Miyajima, Naoshima, Shirakawa-go, Aso, Ise, Okinawa and more; live where operators publish positions), here (warnings, observation, hazards, RTK, prices for a point), place (municipality facts by 5-digit code), rtk_bases_near, kurashigram_prices, gnss_in_japan. Values carry their source and time; warnings are relayed from the Japan Meteorological Agency. Notice: no generative AI produces these values; they are published observations and official data as received, with their timestamps. Do not treat them as the…

endpoint
https://kuongeo.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is kuongeo live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is kuongeo free to use?
Not measured yet.
What tools does kuongeo have?
7 tools: answer, kurashigram_prices, next_departures, place, here, rtk_bases_near, gnss_in_japan.
Is kuongeo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99%· all time 99%

latency
173ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 503 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find next public transport departures in japan
  • get weather warnings for a point in japan
  • look up japanese municipality facts
  • find nearby rtk base stations
takes → gives
text → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • answer reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "place name, Japanese or English. Extra words like 基準局/警報/near are fine"
        },
        "lang": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "ja"
        }
      }
    }
    arguments 20 lines
  • kurashigram_prices reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "5-digit municipality code"
        }
      }
    }
    arguments 12 lines
  • next_departures reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "place or sight, Japanese or English; extra words like next/ferry/bus are fine"
        },
        "lang": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en"
        }
      }
    }
    arguments 20 lines
  • place reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "5-digit municipality code, e.g. 01207 (Obihiro)"
        }
      }
    }
    arguments 12 lines
  • here reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lat",
        "lon"
      ],
      "properties": {
        "lat": {
          "type": "number",
          "description": "latitude (20 to 46)"
        },
        "lon": {
          "type": "number",
          "description": "longitude (122 to 154)"
        },
        "lang": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en"
        },
        "sections": {
          "type": "string",
          "description": "comma list of muni,warnings,observation,earthquakes,hazards,heat,elevation,rtk,prices (default all)"
        }
      }
    }
    arguments 29 lines
  • rtk_bases_near reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lat",
        "lon"
      ],
      "properties": {
        "lat": {
          "type": "number"
        },
        "lon": {
          "type": "number"
        }
      }
    }
    arguments 15 lines
  • gnss_in_japan reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "default": "en"
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c47181ff9a21d0fd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c47181ff9a21d0fd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c47181ff9a21d0fd/badge.svg)](https://brick.blue/agent/c47181ff9a21d0fd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.