fix connection refused error message

[nabuskey]

This PR makes the proxy server print "Connection refused" when the error message contains ECONNREFUSED only.

Motivation and Context

Currently, proxy server prints Connection refused. Is the MCP server running? under two circumstances:

1. Error message contains Error POSTing to endpoint (HTTP 404) OR
2. Error message contains ECONNREFUSED.

The term "Connection Refused" usually means it could not make connections at all.
I think it makes sense to print the error message in case of ECONNREFUSED because that's how node defines it.

I don't think it makes sense to print that when the connection was successful but a 404 was returned by the server.

fixes: #543

How Has This Been Tested?

1. Have a MCP running.
2. Open Inspector. Confirm it's accessible at /mcp.
3. Change endpoint to /mcp1, then attempt to connect

Breaking Changes

No breaking changes.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[cliffhall]

Hi @nabuskey!

We already have handlers for these conditions:

The reason the logic was put in place was to clean up the console output of useless stack traces and make it more understandable. In either case, an MCP connection was refused at the endpoint specified. A 404 and an ECONNREFUSED are functionally equivalent in this respect. You check your server and your URL and find that you've done something wrong.

If you feel strongly about it, please amend the PR to log the strings:

• "Connection refused. Is the MCP server running?" for ECONNREFUSED
• "Error accessing endpoint (HTTP 404)" for ANY message containing 404 (since it could be a GET, POST, or a DELETE)
• And only if it isn't one of those, "Error from MCP server:" plus the error and its attendant stacktrace.

[nabuskey]

Thanks for providing context! I understand where you are coming from now.

I will update this PR with your suggestions since I do think "connection refused" carries a specific meaning (the server was not listening on the port). It will help users troubleshoot issues faster.