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

uratori

https://uratori.utsuroi.today

Registry code: 845308b59ebf2ad8

api record

uratori は日本の取引先の第三者認証(ISO/IEC 27001・プライバシーマーク・ISMAP・SOC 2 等)を公開情報から実調査するサービスです。結果は5区分+証跡URL+取得日で返ります。『公開情報では未確認』は未取得の断定ではありません。結果を安全/危険・合格/不合格の判定として扱わないでください。まず get_status_definitions で区分の意味を確認することを推奨します。本サービスは、国税庁法人番号システムWeb-API機能を利用して取得した情報をもとに作成していますが、サービスの内容は国税庁によって保証されたものではありません。

endpoint
https://uratori.utsuroi.today/api/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 uratori live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is uratori free to use?
Yes — the hub reached it with no key and no payment.
What tools does uratori have?
2 tools: research_vendor_certifications, get_status_definitions.
Is uratori 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
98.7%

90 days 99%· all time 99%

latency
994ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 288 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
security & compliance compliance & regulation
used for
  • check a japanese vendor's security certifications
  • get certification status definitions
takes → gives
text → data
tools
2 reads
_ 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 2 tools
1 open 1 never probed 1 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.

  • get_status_definitions reads open 1h ago

    uratori の判定5区分(verified_official / public_evidence / vendor_confirm_required / not_found / expired_or_negative)と、not_found の内訳4区分の定義、調査方法と限界を返す。research_vendor_certifications の結果を解釈する前に一度読むことを推奨。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • research_vendor_certifications reads unknown never probed

    日本の取引先(ベンダー)1社の第三者認証・監査レポート(ISO/IEC 27001, プライバシーマーク, ISMAP, SOC 2 等)の取得状況を、公開情報(公的レジストリ・企業公式サイト)から実調査して返す。判定は5区分(公式確認/公開記載=自己申告/要ベンダー確認/公開情報では未確認/失効・取消)で、各判定に証跡URLと取得日が付く。「未確認」は未取得の断定ではない。結果は参考情報であり、安全/危険の判定や認証の保証ではない。法人番号(13桁)を指定すると同名別法人との取り違えを防げる。無料・数十秒かかることがある。

    mcp-tool

    {
  "type": "object",
  "required": [
    "companyName"
  ],
  "properties": {
    "serviceUrl": {
      "type": "string",
      "description": "対象サービスまたは会社公式サイトのURL(任意・http(s))。入力すると名寄せと認証照合の精度が上がります"
    },
    "companyName": {
      "type": "string",
      "description": "会社名(例: フリー株式会社)。正式な登記名称に近いほど正確"
    },
    "serviceName": {
      "type": "string",
      "description": "サービス名(任意。省略時は会社名を使用)"
    },
    "corporateNumber": {
      "type": "string",
      "description": "法人番号13桁(任意・推奨。同名別法人の取り違え防止)"
    }
  }
}
    arguments 24 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 845308b59ebf2ad8.

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