# MCP health report

**URL:** https://{api_host}/mcp
**Checked:** 2026-09-21T08:10:51.349Z
**Verdict:** FAIL (score 50/100, issues 2, warnings 0)

## Checks
- ❌ 接続できない(タイムアウト/DNS/TLS)
- ❌ 2回目の接続も失敗

## Raw
| probe | HTTP |
|---|---|
| initialize (MCP-Protocol-Version) | n/a |
| initialize (legacy, no header) | n/a |
| tools/list (no auth) | n/a |
| tools/call (no auth) | n/a |



## How to fix
1. **Open discovery, lock execution.** Answer `initialize` and `tools/list` without credentials; keep `tools/call` behind auth. (Measured: every healthy server in a 110-server sample exposes tools; most unhealthy ones expose none.)
2. **Never reject a legacy handshake.** Directory health checks identify as legacy clients and omit `MCP-Protocol-Version`. Rejecting it is what kept our own server unhealthy for three days.
3. **On 401, always send `WWW-Authenticate: Bearer realm="…"`.** A 401 without it looks broken to crawlers.
4. **Optionally advertise `resource_metadata`** (RFC 9728) in that header and serve the document at that URL.

Generated by https://mcp-health.rowu.workers.dev