mcpbeat

uratori（ウラトリ） MCP Server

today.utsuroi/uratori
not responding

uratori（ウラトリ） is listed as active in the registry but did not answer our last check. It exposes 2 tools.

日本企業の第三者認証(ISO 27001/Pマーク/ISMAP等)を公開情報から実調査し、5区分の判定と証跡URLを返す。未確認は未取得の断定ではない。

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 92 checks
2
Tools
read from the server
314 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add uratori --transport http https://uratori.utsuroi.today/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "uratori": {
      "url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.uratori]
url = "https://uratori.utsuroi.today/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "uratori": {
      "url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "uratori": {
      "url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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

Endpoints

URLTransportStateLatencyChecked
https://uratori.utsuroi.today/api/mcp streamable-http answering 314 ms 3 min ago

uratori（ウラトリ） — questions

Answers built from our own checks of this server.

What can uratori（ウラトリ） do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_status_definitions, research_vendor_certifications. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is uratori（ウラトリ） working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 314 ms. The bar chart above shows every period we have measured.
The registry lists uratori（ウラトリ） as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect uratori（ウラトリ）?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does uratori（ウラトリ） need an API key?
No. uratori（ウラトリ） completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.