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

jp-exam-schedules

https://jp-exam-schedules-production.mk-career-planning.workers.dev

Registry code: 0728c148b21141ae

api record

Japanese national exam and result dates as published by MHLW, with tracked date changes.

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

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

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

_ what it can do 4 tools
1 open 3 never probed 1 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.

  • exam_schedule_lookup open 2h ago

    When is this Japanese national exam held and when are results announced, as published on MHLW's list page, and did the dates change? Give exam (exam_id like nurse, or the name in Japanese or English); omit it to list exams, optionally by category. Returns next_events and all events with ISO dates, revision_status, revisions (before and after), possibly_stale, retrieved_at and source. Application periods are not covered. Confirm on the official exam page.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "exam": {
          "type": "string",
          "maxLength": 100,
          "description": "exam_id (e.g. nurse, pharmacist, certified-social-worker) or exam name in Japanese (看護師国家試験, 看護師) or English"
        },
        "limit": {
          "type": "integer",
          "maximum": 120,
          "minimum": 1,
          "description": "Maximum number of exams when listing, 1-120 (default 50)"
        },
        "category": {
          "enum": [
            "medical",
            "occupational_safety",
            "beauty_health",
            "welfare_care"
          ],
          "type": "string",
          "description": "Optional filter when listing: medical (Medical, pharmaceutical, health and food sanitation), occupational_safety (Technical, occupational safety and health), beauty_health (Beauty and health), welfare_care (Welfare and long-term care)"
        },
        "include_undated": {
          "anyOf": [
            {
              "type": "boolean"
            },
            {
              "enum": [
                "true",
                "false"
              ],
              "type": "string"
            }
          ],
          "description": "When listing, also include exams for which the page gives no dates (default false)"
        }
      }
    }
    arguments 42 lines
  • exam_schedule_changes unknown 2h ago

    Which exam dates on MHLW's list page of national qualification exams changed, appeared or left the list since a date (this service's own record of page versions; MHLW keeps none)? Each change has before and after as published and the time this service first read it. Optional exam and change_type filters. Free window: last 30 days.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "since"
      ],
      "properties": {
        "exam": {
          "type": "string",
          "maxLength": 100,
          "description": "Optional: exam_id or exact exam name"
        },
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Maximum number of changes, 1-500 (default 100)"
        },
        "since": {
          "type": "string",
          "maxLength": 40,
          "description": "ISO 8601 date or date-time with time zone, e.g. 2026-10-01 or 2026-10-01T00:00:00Z"
        },
        "change_type": {
          "enum": [
            "exam_added",
            "exam_reappeared",
            "exam_removed",
            "exam_details_changed",
            "event_added",
            "event_date_changed",
            "event_details_changed",
            "event_removed"
          ],
          "type": "string",
          "description": "Optional filter: exam_added, exam_reappeared, exam_removed, exam_details_changed, event_added, event_date_changed, event_details_changed, event_removed"
        }
      }
    }
    arguments 39 lines
  • get_receipt unknown 2h 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 0728c148b21141ae.

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