hermes - 💡(How to fix) Fix MCP connectivity check resolves server config key as DNS hostname instead of using configured URL

Hermes version: 0.13.0

Describe the bug

When running an MCP server health/connectivity check from within a Hermes session, Hermes attempts to resolve the MCP server's config key name as a DNS hostname rather than using the configured url. For example, a server configured as:

mcp_servers:
  github:
    url: https://api.githubcopilot.com/mcp/
    headers:
      Authorization: Bearer \${COPILOT_GITHUB_TOKEN}

produces the error:

GitHub MCP: ❌ Connection timed out — the github host is unreachable.

The hostname github does not exist in DNS. The correct URL https://api.githubcopilot.com/mcp/ is reachable and responds with HTTP 200. The MCP connection itself functions correctly at runtime — only the diagnostic check is wrong.

Steps to reproduce

1. Configure an HTTP MCP server where the config key name is not a valid hostname (e.g. github, hindsight, searxng)
2. Ask Hermes to check the status/connectivity of its MCP servers
3. Hermes reports DNS resolution failure for the key name instead of testing the configured URL

Expected behavior

The connectivity check should use the url field from the MCP server config, not the key name.

Actual behavior

The check tries to resolve the config key (e.g. github) as a DNS hostname and reports failure even when the server is fully reachable via its configured URL.

Additional context

Verified via direct curl from inside the container:

curl -X POST \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -H "mcp-protocol-version: 2025-03-26" \
  -d '{"jsonrpc":"2.0","method":"initialize","id":1,"params":{"protocolVersion":"2025-03-26","capabilities":{}}}' \
  https://api.githubcopilot.com/mcp/
# → HTTP 200, valid MCP initialize response