MCP initialization produces multiple "Unexpected token is not valid JSON" errors on every new chat

[SolarFab]

Description:
On every new chat session, Claude displays a flood of yellow warning notifications:

MCP n8n-local: Unexpected token 'r', " refCount: 1" is not valid JSON
MCP n8n-local: Unexpected token 'c', " clientVersion"... is not valid JSON
MCP n8n-local: Unexpected token 'v', " version: '"... is not valid JSON
MCP n8n-local: Unexpected token 'i', " isN8nClient"... is not valid JSON
MCP n8n-local: Unexpected token 'r', " reasoning:"... is not valid JSON
MCP n8n-local: Unexpected token 'r', " response: {"... is not valid JSON
MCP n8n-local: Unexpected token 'p', " protocolVersion"... is not valid JSON
MCP n8n-local: Unexpected token 'c', " capabilities"... is not valid JSON
MCP n8n-local: Unexpected token 's', " serverInfo"... is not valid JSON

Environment:

n8n-mcp version: 2.36.1 (latest)
Platform: macOS, Claude Desktop app
n8n version: 2.10.4 running on a remote Linux server
Connection: via Tailscale (HTTP, not HTTPS)
n8n connection itself works fine (health check returns success)

Expected behavior: MCP server initializes silently without errors.
Actual behavior: During the MCP handshake/initialization, the server sends non-JSON formatted metadata fields which Claude's interface cannot parse, resulting in multiple error notifications on every new chat.
Note: These errors are purely cosmetic — the connection works correctly after initialization.