Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

uratori(ウラトリ)

REMOTE · URATORI.UTSUROI.TODAY · SCANNED SEP 24

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

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 589 tokens (~294/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the uratori(ウラトリ) MCP server?

uratori(ウラトリ) is a hosted endpoint at https://uratori.utsuroi.today/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · uratori.utsuroi.today

# add to Claude Code
claude mcp add --transport http today-utsuroi-uratori 'https://uratori.utsuroi.today/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "today-utsuroi-uratori": {
      "url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "today-utsuroi-uratori": {
      "type": "http",
      "url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.today-utsuroi-uratori]
url = "https://uratori.utsuroi.today/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "today-utsuroi-uratori": {
      "type": "remote",
      "url": "https://uratori.utsuroi.today/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add today-utsuroi-uratori --url 'https://uratori.utsuroi.today/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  today-utsuroi-uratori:
    url: "https://uratori.utsuroi.today/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "today-utsuroi-uratori": {
      "Transport": "http",
      "Url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add today-utsuroi-uratori -t streamable-http -u 'https://uratori.utsuroi.today/api/mcp'
// mcp.json
{
  "mcpServers": {
    "today-utsuroi-uratori": {
      "type": "http",
      "url": "https://uratori.utsuroi.today/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Sept 26 0
    • “research_vendor_certifications” reworded the description of “serviceUrl” cosmetic
    • “research_vendor_certifications” made “serviceUrl” optional cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 26 Aug 26 79
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://uratori.utsuroi.today/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.utsuroi.today CN=YR1,O=Let's Encrypt,C=US 26 Aug 2026 24 Nov 2026 RSA 2048 SHA256-RSA 62fb8f9ef8ad4b443bb784f9ebc77dff103
SANs: *.utsuroi.today, utsuroi.today
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of uratori.utsuroi.today. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
today. present 8164 8 Verified
utsuroi.today. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://accounts.google.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://*.supabase.co https://accounts.google.com https://api.pwnedpasswords.com; frame-src https://accounts.google.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://uratori.utsuroi.today/api/mcp Verified 200
http (plaintext) http://uratori.utsuroi.today/api/mcp HTTPS enforced 308 https://uratori.utsuroi.today/api/mcp
MCP tools · 2 exposed · ~414 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_status_definitions ~84

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

research_vendor_certifications ~330

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

NameTypeReqDescription
companyNamestringyes会社名(例: フリー株式会社)。正式な登記名称に近いほど正確
corporateNumberstring法人番号13桁(任意・推奨。同名別法人の取り違え防止)
serviceNamestringサービス名(任意。省略時は会社名を使用)
serviceUrlstring対象サービスまたは会社公式サイトのURL(任意・http(s))。入力すると名寄せと認証照合の精度が上がります

No output schema declared.

No examples provided.

Common questions

What is the uratori(ウラトリ) MCP server?

uratori(ウラトリ) is an MCP server listed in the public MCP registry as today.utsuroi/uratori. 日本企業の第三者認証(ISO 27001/Pマーク/ISMAP等)を公開情報から実調査し、5区分の判定と証跡URLを返す。未確認は未取得の断定ではない。 This page covers its hosted endpoint (https://uratori.utsuroi.today/api/mcp).

Is the uratori(ウラトリ) MCP server safe to use?

uratori(ウラトリ) scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the uratori(ウラトリ) MCP server expose?

uratori(ウラトリ) exposes 2 tools: research_vendor_certifications, get_status_definitions. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.

Does the uratori(ウラトリ) MCP server require authentication?

No. We connected to uratori(ウラトリ) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the uratori(ウラトリ) MCP server still maintained?

uratori(ウラトリ) is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.