uratori（ウラトリ）
REMOTE · URATORI.UTSUROI.TODAY · SCANNED AUG 3
日本企業の第三者認証(ISO 27001/Pマーク/ISMAP等)を公開情報から実調査し、5区分の判定と証跡URLを返す。未確認は未取得の断定ではない。
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 566 tokens (~283/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · uratori.utsuroi.today
claude mcp add --transport http today-utsuroi-uratori https://uratori.utsuroi.today/api/mcp
[mcp_servers.today-utsuroi-uratori] url = "https://uratori.utsuroi.today/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"today-utsuroi-uratori": {
"type": "remote",
"url": "https://uratori.utsuroi.today/api/mcp",
"enabled": true
}
}
} openclaw mcp add today-utsuroi-uratori --url https://uratori.utsuroi.today/api/mcp --transport streamable-http
mcp_servers:
today-utsuroi-uratori:
url: "https://uratori.utsuroi.today/api/mcp" {
"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.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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 62
First indexed and scored.
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 3 Aug 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 | 24 Jun 2026 | 22 Sept 2026 | RSA 2048 | SHA256-RSA | 595bd00d05e12911217654131b3045e708b |
| 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 |
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=() |
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 |
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.
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 ~307
日本の取引先(ベンダー)1社の第三者認証・監査レポート(ISO/IEC 27001, プライバシーマーク, ISMAP, SOC 2 等)の取得状況を、公開情報(公的レジストリ・企業公式サイト)から実調査して返す。判定は5区分(公式確認/公開記載=自己申告/要ベンダー確認/公開情報では未確認/失効・取消)で、各判定に証跡URLと取得日が付く。「未確認」は未取得の断定ではない。結果は参考情報であり、安全/危険の判定や認証の保証ではない。法人番号(13桁)を指定すると同名別法人との取り違えを防げる。無料・数十秒かかることがある。
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | yes | 会社名(例: フリー株式会社)。正式な登記名称に近いほど正確 |
| corporateNumber | string | — | 法人番号13桁(任意・推奨。同名別法人の取り違え防止) |
| serviceName | string | — | サービス名(任意。省略時は会社名を使用) |
| serviceUrl | string | yes | 対象サービスまたは会社公式サイトのURL(http(s)) |
No output schema declared.
No examples provided.