Suzuri
REMOTE · SUZURI.DEV · SCANNED AUG 3
Semantic search across Japan's government white papers, in English or Japanese. Free beta.
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 Security46
- 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 1 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 308 tokens (~308/item across 1 items; 1 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 Management0
- Stability check failed: schema churn in the 8 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 · suzuri.dev
claude mcp add --transport http dev-suzuri-mcp https://suzuri.dev/mcp
[mcp_servers.dev-suzuri-mcp] url = "https://suzuri.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-suzuri-mcp": {
"type": "remote",
"url": "https://suzuri.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-suzuri-mcp --url https://suzuri.dev/mcp --transport streamable-http
mcp_servers:
dev-suzuri-mcp:
url: "https://suzuri.dev/mcp" {
"mcpServers": {
"dev-suzuri-mcp": {
"type": "http",
"url": "https://suzuri.dev/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.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 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
- Tool “search_japan_white_papers” rewrote its description, which is the text the model reads security
- 27 Jul 26 −1
- 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 60
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://suzuri.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=suzuri.dev | CN=WE1,O=Google Trust Services,C=US | 10 Jul 2026 | 8 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 3f971b147283d7980e4e298466233a28 |
| SANs: suzuri.dev, *.suzuri.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of suzuri.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| suzuri.dev. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://suzuri.dev/mcp | Verified | 200 | |
| http (plaintext) | http://suzuri.dev/mcp | Inconclusive | 405 |
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.
search_japan_white_papers ~308
Semantic search over Japan's official government white papers: the Ministry of Defense white paper (防衛白書, 2025 edition) and METI's trade white paper (通商白書, 2025 edition). Use this when the user asks about Japanese defense policy, the Self-Defense Forces, Japan's security environment, defense budgets or procurement programs, the Japan-US alliance, how Tokyo officially describes China, North Korea or Russia, or about Japan's trade strategy, global supply chain resilience, economic security, overdependence and economic coercion, or China's industrial policy and its effect on trade. One query searches both papers at once. Queries may be in English or Japanese — English queries are automatically translated before retrieval against the Japanese corpus. Returns ranked excerpts with paper name, chapter, page numbers and a source URL suitable for citation. Scope: the 2025 editions only. Not a source for breaking news, press conferences, statistical databases, export control regulations, tariff schedules, or documents from other ministries.
| Name | Type | Req | Description |
|---|---|---|---|
| min_score | number | — | Minimum cosine similarity threshold (default 0.25, range 0–1) |
| query | string | yes | A natural-language question or topic, in English or Japanese. Examples: "How does Japan describe China's military buildup?", "GCAP next-generation fighter", "経済安全保障 サプライチェーン". |
| top_k | number | — | Number of results to return (default 10, max 20) |
No output schema declared.
No examples provided.