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

jp-caa-actions

https://jp-caa-actions-production.mk-career-planning.workers.dev

Registry code: c10f3e8fff527049

api record

Japan CAA actions under the Specified Commercial Transactions Act, with head office and source.

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

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

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.

  • caa_action_list open 1h ago

    Which companies did the Japanese Consumer Affairs Agency act against under the Act on Specified Commercial Transactions since a date? One record per company and action, latest first, with action types, cited articles, head office as published, suspension period, source URL and retrieved_at, plus the changes this service observed (actions added, changed or removed from the CAA list). Optionally filter by action_type. National actions only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Maximum number of records, 1-200 (default 50)"
        },
        "since": {
          "type": "string",
          "maxLength": 10,
          "description": "Optional action date YYYY-MM-DD (default: 365 days ago)"
        },
        "action_type": {
          "enum": [
            "business_suspension_order",
            "instruction",
            "business_prohibition_order"
          ],
          "type": "string",
          "description": "Optional: business_suspension_order, instruction or business_prohibition_order"
        }
      }
    }
    arguments 26 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
  • caa_action_lookup unknown 1h ago

    Has the Japanese Consumer Affairs Agency published a national action under the Act on Specified Commercial Transactions against a company with this name? Give the name in Japanese and optionally the head office prefecture and municipality. Returns action date, types, articles, head office, suspension period, source URL, retrieved_at, page SHA-256. Status found, not_found_in_checked_records (with checked_scope) or unknown. Matched by name and location only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Company name in Japanese, e.g. 株式会社HOPE Group (full/half width, spaces and the position of 株式会社 are normalized)"
        },
        "prefecture": {
          "type": "string",
          "maxLength": 20,
          "description": "Optional head office prefecture in Japanese or English (東京都, Tokyo, 大阪府, Osaka)"
        },
        "municipality": {
          "type": "string",
          "maxLength": 50,
          "description": "Optional head office municipality or ward in Japanese (新宿区, 大阪市, 仙台市泉区)"
        }
      }
    }
    arguments 25 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 30 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
_ 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 c10f3e8fff527049.

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