# MCP health report

**URL:** https://rx.agentlookups.ai/mcp
**Checked:** 2026-09-21T08:12:06.806Z
**Verdict:** WARN (score 90/100, issues 0, warnings 1)

## Checks
- ✅ モダンなinitializeに応答
- ✅ ヘッダ無しのレガシー initialize も通る
- ✅ tools/list が無認証で読める(ツール数 1)
- ⚠️ tools/call が無認証で通る。濫用・課金リスク

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

**tools exposed:** 1


## 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