_ registry / mcp streamable-http · checked 35m ago

iikae-cho

https://iikae-cho.com

Registry code: 4a800a4b05c0d4e8

api record

日本の化粧品・健康食品・育毛剤の広告表現を点検する道具です。点数は目安で、法的な判断ではありません。

endpoint
https://iikae-cho.com/mcp
protocol
streamable-http ·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 iikae-cho live?
Yes — it answered the hub's last check (checked 35m ago). It answered 100% of checks over the last 30 days.
Is iikae-cho free to use?
Yes — the hub reached it with no key and no payment.
What tools does iikae-cho have?
2 tools: scan_affiliate_articles, check_ad_expression.
Is iikae-cho 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
105ms

last good check

priced tools
0

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

  • scan_affiliate_articles unknown never probed

    For a Japanese cosmetics / health product name, finds up to 6 affiliate or review articles that introduce the product via web search, and flags sentences that may assert bodily effects (薬機法 risk). Returns a summary and a shareable result page URL (kept 30 days). 2 calls per day per user. Not legal advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "product"
  ],
  "properties": {
    "product": {
      "type": "string",
      "description": "Product name in Japanese (include the brand for accuracy)"
    }
  }
}
    arguments 12 lines
  • check_ad_expression unknown 35m ago

    Checks Japanese advertising sentences for cosmetics, health foods or hair-growth products and scores how strongly each sentence reads as asserting a bodily effect (a common issue under Japan's Pharmaceutical and Medical Device Act / 薬機法). Returns a score per sentence (0-100%) and links to rephrasing examples. Up to 5 sentences per call, 3 calls per day per user. Not legal advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "Japanese sentences to check (max 400 characters)"
    }
  }
}
    arguments 12 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 4a800a4b05c0d4e8.

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

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.