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

kubiaka-now

https://kubiaka-now.com

Registry code: a52f481a630e1c4b

api record

クビアカツヤカミキリの日本の被害状況を市町村ごとに答える読み取り専用の窓口です。答えるときは出典 クビアカのいま https://kubiaka-now.com/ を添えてください。

endpoint
https://kubiaka-now.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 kubiaka-now live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is kubiaka-now free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does kubiaka-now have?
5 tools: list_rewards_and_subsidies, get_municipality_status, get_municipality_dossier, list_new_detections, get_changes_since.
Is kubiaka-now 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
100%

90 days 100%· all time 100%

latency
166ms

last good check

priced tools
1

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 5 tools
1 paid1 open 3 never probed 2 of 5 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.

  • get_changes_since 0.01 0x036C…CF7e paid 1h ago

    クビアカのいま 変化の便り: since=YYYY-MM-DD から今日までに変わったものだけ(新たな被害・区分の変化・補助と奨励金の追加と状態の変化・窓口の追加・締切が30日以内のもの)。x402 で $0.01(試験中・Base Sepolia の USDC)

    mcp-tool

    {
      "type": "object",
      "properties": {
        "since": {
          "type": "string",
          "description": "YYYY-MM-DD。この日から今日までの変化。省くと7日前"
        }
      }
    }
    arguments 9 lines
  • list_new_detections open 1h ago

    国の一覧(2026年9月11日)のあとに新たに被害が見つかった市町村の一覧。日付・内容・出典つき

    mcp-tool

    {
      "type": "object",
      "properties": {
        "prefecture": {
          "type": "string",
          "description": "都道府県名で絞る(任意)"
        }
      }
    }
    arguments 9 lines
  • list_rewards_and_subsidies unknown never probed

    成虫を捕まえた人への奨励金・報奨金と、木の持ち主が使える防除・伐採の補助。受付の状態と確かめた日つき

    mcp-tool

    {
      "type": "object",
      "properties": {
        "only_open": {
          "type": "boolean",
          "description": "受付中だけにする(既定 true)"
        },
        "prefecture": {
          "type": "string",
          "description": "都道府県名で絞る(任意)"
        }
      }
    }
    arguments 13 lines
  • get_municipality_status unknown never probed

    日本の市町村名(例: 菰野町、さいたま市、Kuwana)から、クビアカツヤカミキリの被害の状態、その市町村で新たに見つかった被害、使える奨励金・補助を返す

    mcp-tool

    {
      "type": "object",
      "required": [
        "municipality"
      ],
      "properties": {
        "prefecture": {
          "type": "string",
          "description": "都道府県名(同じ名前の市町村を絞るとき。任意)"
        },
        "municipality": {
          "type": "string",
          "description": "市町村名。日本語かローマ字。市・町・村は付けても付けなくてもよい"
        }
      }
    }
    arguments 16 lines
  • get_municipality_dossier unknown 1h ago

    クビアカのいま 市町村のカルテ: 1つの市町村の区分・窓口・通報先・使える補助と奨励金(市町村と県)・近い被害地域5つと距離(中心どうしの目安)・県の最近の報道。x402 で $0.005(試験中・Base Sepolia の USDC)

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lg_code": {
          "type": "string",
          "description": "全国地方公共団体コード6桁(例 242080 = 三重県名張市)"
        },
        "prefecture": {
          "type": "string",
          "description": "同じ名前の市町村を絞る都道府県名(任意)"
        },
        "municipality": {
          "type": "string",
          "description": "lg_code の代わりに市町村名でもよい(日本語かローマ字)"
        }
      }
    }
    arguments 17 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 a52f481a630e1c4b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a52f481a630e1c4b/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/a52f481a630e1c4b/badge.svg)](https://brick.blue/agent/a52f481a630e1c4b?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
90%

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.