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

mofa-overseas-safety

https://mofa-overseas-safety-production.mk-career-planning.workers.dev

Registry code: 2ebc33aeebbaf5fd

api record

Which danger level has Japan's MOFA set for a country and its regions? Hosted, change history kept.

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

endpoint
https://mofa-overseas-safety-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 mofa-overseas-safety live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mofa-overseas-safety free to use?
Yes — the hub reached it with no key and no payment.
What tools does mofa-overseas-safety have?
4 tools: catalog, mofa_country_levels, get_receipt, mofa_level_changes.
Is mofa-overseas-safety 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,079ms

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.

  • 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
  • mofa_country_levels unknown 1h ago

    Which danger level (1-4) does Japan's MOFA set now for this country, region by region? Look up by ISO 3166-1 alpha-2/alpha-3 or 4-digit MOFA code. Returns region-level entries in MOFA's Japanese text with English level labels, levels present, a derived max level (not a country-wide level), infectious disease danger notices, MOFA issue dates and URLs, previous levels from this service's own history (tracking_since), freshness and sources. Relays MOFA; no danger assessment or travel advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "maxLength": 16,
          "description": "ISO 3166-1 alpha-2 (TH), alpha-3 (THA), US-HI, or 4-digit MOFA country code (0066). US returns the mainland and Hawaii entries."
        }
      }
    }
    arguments 14 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
  • mofa_level_changes unknown 1h ago

    Which countries had their Japan MOFA danger or infectious disease danger levels (or region texts) change since a given time? From this service's own observation record: old and new levels, MOFA info ids and issue dates, when we observed the change and when we last saw the old state, plus polling gaps. Only changes since tracking_since, as observed at our polling times. Free window: last 30 days (an earlier since is clamped; see history_window). Relays MOFA; no advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "since"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Maximum number of changes, 1-200 (default 100)"
        },
        "since": {
          "type": "string",
          "maxLength": 40,
          "description": "ISO 8601 date or date-time with time zone, e.g. 2026-10-01T00:00:00Z"
        },
        "country": {
          "type": "string",
          "maxLength": 16,
          "description": "Optional filter: ISO alpha-2/alpha-3 or 4-digit MOFA code"
        },
        "include_notice_updates": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "enum": [
                "true",
                "false"
              ],
              "type": "string"
            }
          ],
          "description": "Also list re-issued notices with the same levels and region text (default false)"
        }
      }
    }
    arguments 40 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 2ebc33aeebbaf5fd.

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