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

jp-flu-regional

https://jp-flu-regional-production.mk-career-planning.workers.dev

Registry code: d8e92db8959cc53c

api record

How much influenza is this Japanese prefecture reporting this week? Hosted, recorded daily.

from a public catalogue that lists it, not from the operator

endpoint
https://jp-flu-regional-production.mk-career-planning.workers.dev/mcp
protocol
http-sse ·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 jp-flu-regional live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is jp-flu-regional free to use?
Yes — the hub reached it with no key and no payment.
What tools does jp-flu-regional have?
4 tools: flu_region_history, flu_region_snapshot, get_receipt, catalog.
Is jp-flu-regional 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
1,449ms

last good check

priced tools
0

of 4 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • flu_region_history unknown 1h ago

    What changed in the recorded influenza figures for a Japanese region since a date? Versions this service recorded: new weeks (first_recorded) and revised values (revised, with the old value) of weekly per-sentinel figures, official statuses and school-closure counts, with observed_at, source URL and raw-file sha256, plus tracking_since and fetch gaps. From our own daily records; values the publisher later overwrote stay visible. Free: last 30 days of records. Descriptive statistics only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "prefecture",
        "since"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 300,
          "minimum": 1,
          "description": "Maximum number of events, 1-300 (default 100)."
        },
        "since": {
          "type": "string",
          "maxLength": 40,
          "description": "YYYY-MM-DD or ISO 8601 date-time with time zone; versions recorded after this time."
        },
        "dataset": {
          "enum": [
            "sentinel",
            "official_status",
            "school_closure"
          ],
          "type": "string",
          "description": "Optional filter: sentinel, official_status or school_closure (default all)."
        },
        "prefecture": {
          "type": "string",
          "maxLength": 40,
          "description": "JP for the national total, or a prefecture: ISO 3166-2 code (JP-33), 1-2 digit code (33), English (Okayama) or Japanese (岡山県) name."
        },
        "health_center": {
          "type": "string",
          "maxLength": 40,
          "description": "Optional health-center area (保健所管内) id or Japanese name, only for prefectures listed in coverage.prefectures_with_local_data."
        }
      }
    }
    arguments 40 lines
  • flu_region_snapshot unknown 1h ago

    What is the latest weekly flu count per sentinel for Japan, a prefecture or a covered health-center area? ISO week, value, recent weeks, official warning/advisory where announced (status_basis official), separate from a comparison with reference values (status_basis computed), school-closure counts by facility type and action where covered (no school names), tracking_since and receipts (url, fetched_at, sha256). Optional as_of date. Descriptive statistics only, no medical or travel advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "prefecture"
      ],
      "properties": {
        "as_of": {
          "type": "string",
          "maxLength": 10,
          "description": "Optional date YYYY-MM-DD: answer with what this service had recorded by the end of that day (UTC). Free window: the last 30 days; older dates return OUTSIDE_FREE_HISTORY_WINDOW."
        },
        "prefecture": {
          "type": "string",
          "maxLength": 40,
          "description": "JP for the national total, or a prefecture: ISO 3166-2 code (JP-33), 1-2 digit code (33), English (Okayama) or Japanese (岡山県) name."
        },
        "health_center": {
          "type": "string",
          "maxLength": 40,
          "description": "Optional health-center area (保健所管内) id or Japanese name, only for prefectures listed in coverage.prefectures_with_local_data."
        }
      }
    }
    arguments 24 lines
  • get_receipt unknown 1h ago

    Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "receipt_id"
      ],
      "properties": {
        "receipt_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "The receipt_id returned with a paid result (\"rcpt_\" + 64 hex characters)."
        }
      }
    }
    arguments 15 lines
  • catalog unknown never probed

    List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 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 d8e92db8959cc53c.

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

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.