claude-code - 💡(How to fix) Fix `claude mcp list` shows "Connected" even when the target port is not open — misleading status label [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46067Fetched 2026-04-11 06:29:51
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Error Message

  1. Call any tool from that server → immediate "connection refused" error
RAW_BUFFERClick to expand / collapse

Symptom

claude mcp list displays "Connected" for MCP servers regardless of whether the target port is actually open. The label implies a live connection, but it only means "the entry is registered."

How to reproduce

  1. Register an MCP server pointing to a port that has no process running (e.g., --browserUrl=http://127.0.0.1:9222 with no Chrome instance)
  2. Run claude mcp list
  3. Server shows "Connected"
  4. Call any tool from that server → immediate "connection refused" error

Expected behavior

  • "Connected" should mean the port is reachable and the server is responding
  • Or the label should be changed to "Registered" / "Configured" to accurately reflect that only the entry exists, not an active connection

Actual behavior

  • "Connected" is shown unconditionally after mcp add, with no port reachability check
  • Users assume the server is live and waste time debugging why tool calls fail

extent analysis

TL;DR

The claude mcp list command should be modified to accurately reflect the connection status of MCP servers, either by changing the label to "Registered" or by implementing a port reachability check.

Guidance

  • Verify the current implementation of the claude mcp list command to understand how it determines the connection status of MCP servers.
  • Consider adding a port reachability check before displaying the "Connected" label to ensure it accurately reflects the server's status.
  • Update the label to "Registered" or "Configured" if a reachability check is not feasible, to avoid misleading users.
  • Review the documentation and user interface to ensure that the new label or behavior is clearly explained to avoid user confusion.

Example

No code snippet is provided as the issue does not contain sufficient technical details about the implementation of the claude mcp list command.

Notes

The solution may require changes to the claude mcp command's implementation, and the approach may vary depending on the underlying technology and design of the system.

Recommendation

Apply a workaround by changing the label to "Registered" or "Configured" to accurately reflect the server's status, as this is a simpler and more straightforward solution that can be implemented quickly to avoid user confusion.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • "Connected" should mean the port is reachable and the server is responding
  • Or the label should be changed to "Registered" / "Configured" to accurately reflect that only the entry exists, not an active connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING