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

jp-finance

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

Registry code: 59ea20dae2afae44

api record

Which JPY rate did Japan Customs publish for a date? Is a firm on an FSA list? Hosted. No advice.

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

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

last good check

priced tools
0

of 6 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 6 tools
6 never probed 0 of 6 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.

  • fsa_register_changes unknown never probed

    Which entries were added to, dropped from, changed in or returned to Japan FSA registers and warning lists since a date? From this service's own record of list versions (the FSA publishes only current lists). Each change has the list, registration number, name as published (personal names withheld), before/after fields, observed_at and the list as-of date. Reasons are not published or inferred. History starts at tracking_since; free window: last 30 days.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "since"
      ],
      "properties": {
        "list": {
          "type": "string",
          "maxLength": 20,
          "description": "Optional: one list id (fib, cae, epi, fts, ml, w_fib_dom, w_fib_ovs, w_fib_qii, w_cae_dom, w_cae_ovs) or registers / warnings; default all lists"
        },
        "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": [
            "added",
            "no_longer_listed",
            "details_changed",
            "relisted"
          ],
          "type": "string",
          "description": "Optional filter: added, no_longer_listed, details_changed or relisted"
        }
      }
    }
    arguments 35 lines
  • jp_customs_fx_batch unknown never probed

    Which JPY rates did Japan Customs publish for these 1-50 currency/date pairs? One call returns ordered per-item status, effective periods, JPY rates as published with base units (1 or 100), source URLs, retrieval and verification times and hashes, read from one dataset snapshot. Dates from 2021-08-15. Unpublished periods and unlisted currencies return unknown. Not charged if no item can be answered. No date selection, tax calculation, market or remittance rates, or forecasts.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "items"
      ],
      "properties": {
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "date": {
                "type": "string",
                "maxLength": 40,
                "description": "Calendar date YYYY-MM-DD, interpreted in Japan"
              },
              "currency": {
                "type": "string",
                "maxLength": 16,
                "description": "Uppercase ISO 4217 alpha-3 code, e.g. USD (current or historic codes; not auto-corrected)"
              }
            },
            "additionalProperties": {}
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "1 to 50 items {currency, date}; order kept, duplicates answered twice"
        }
      }
    }
    arguments 31 lines
  • jp_fsa_registry_lookup unknown 1h ago

    Is this business (name, registration or 13-digit corporate number) on a Japan FSA register or warning list? Exact match (optional domain) against: registered financial instruments, crypto-asset exchange, electronic payment instruments, funds transfer and money lending businesses, and FSA warnings to unregistered businesses. Returns matches, unconfirmed name candidates, domain links only when a list states them, and which lists were checked as of when. Absence does not mean safe; no advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "Business name as written, e.g. 株式会社SBI証券 or Bybit Fintech Limited"
        },
        "domain": {
          "type": "string",
          "maxLength": 300,
          "description": "Optional domain or URL, e.g. example.com"
        },
        "number": {
          "type": "string",
          "maxLength": 80,
          "description": "Registration number (e.g. 関東財務局長(金商)第44号) or 13-digit corporate number"
        }
      }
    }
    arguments 21 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
  • jp_customs_fx unknown 1h ago

    Which JPY rate did Japan Customs publish for this currency on this date? Input: ISO 4217 code and YYYY-MM-DD date. Returns status (valid/invalid/unknown), the inclusive effective period, the JPY rate as published with its base units (1 or 100), source URLs, retrieval and verification times and SHA-256 hashes. Dates from 2021-08-15. Unpublished periods and unlisted currencies return unknown. Reference for customs and bookkeeping only; not a market or remittance rate; no tax calculation.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "currency",
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "maxLength": 40,
          "description": "Calendar date YYYY-MM-DD (Japan), e.g. 2026-10-07"
        },
        "currency": {
          "type": "string",
          "maxLength": 16,
          "description": "Uppercase ISO 4217 alpha-3 code, e.g. USD"
        }
      }
    }
    arguments 20 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 59ea20dae2afae44.

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

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.