jp-sanctions
https://jp-sanctions-production.mk-career-planning.workers.dev
Registry code: c4be27495a2edb1f
Is this name on Japan's MOF asset-freeze list? Hosted, list-change history kept. Reference only.
from a public catalogue that lists it, not from the operator
- endpoint
- https://jp-sanctions-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 jp-sanctions live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is jp-sanctions free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does jp-sanctions have?
- 4 tools: catalog, get_receipt, sanctions_list_changes, sanctions_screen_name.
- Is jp-sanctions 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_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.
{ "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 linessanctions_list_changes unknown 1h ago
What was added to, removed from or modified in the Japan MOF asset-freeze list since a date? From this service's own record of list versions (MOF publishes only the current list). Each change has the entry id, names, program, before/after fields and the versions compared. History starts at tracking_since; nothing earlier was observed. Free window: last 30 days (an earlier since is clamped; see history_window). Reference relay only.
{ "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-01 or 2026-10-01T00:00:00Z" }, "entry_id": { "type": "string", "maxLength": 20, "description": "Optional filter: MOF list number, e.g. 029-000001" }, "change_type": { "enum": [ "added", "removed", "modified" ], "type": "string", "description": "Optional filter: added, removed or modified" } } }arguments 34 linessanctions_screen_name unknown 1h ago
Does this person or entity name (Latin or Japanese) appear on the Japan MOF asset-freeze list under the Foreign Exchange Act? Returns exact_match, candidates (similar names, not matches), no_match_in_checked_list or unknown (stale/unavailable), with entry ids, all name forms, program, notice dates, list version, freshness and attribution. Reference relay only: not a compliance determination or a statement that a transaction is permitted.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 200, "description": "Name of a person or entity in Latin letters or Japanese (katakana, hiragana or kanji), e.g. 'Vladimir Putin' or 'ウラジーミル・プーチン'" }, "max_candidates": { "type": "integer", "maximum": 25, "minimum": 1, "description": "Maximum number of similar-name candidates to return, 1-25 (default 10)" } } }arguments 20 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc4be27495a2edb1f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c4be27495a2edb1f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c4be27495a2edb1f?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.