Symptom page
MCP connected, tools not listed
Handshake and transport can succeed while the host still publishes an empty or incomplete tool list. “Connected” is not the same as “tools available to the model.”
Symptom
- Claude Code UI or logs show the MCP server connected.
- No tools appear for that server, or only a subset appears.
How to judge
Differential: capture tools/list from the same server outside Claude Code. If the wire list is empty, fix the server first. If the wire list is populated and Claude Code shows none or fewer, inspect host skip logs (property key patterns, schema combinators, size limits) before rewriting transport.
- Preflight helps when you already have a snapshot and requirements: it answers schema-fit questions, not “will Claude Code list this.”
- If you need a dated, host-bound record of what Claude Code listed on your artifact, that is the live check.
Host / version notes
Live paid scope is Claude Code only. See host matrix. Cross-links: Inspector vs zero tools, static PASS / host fail.
Next step
Run free Exactlane Preflight for the static contract. If Claude Code still drops or rejects tools after a PASS — or you already know you need a live host run — the public paid offer is the Claude Code Compatibility Check (US$150) or Check + Bounded Fix (US$300).