bhawnagaur

Hi, Thanks for responding so quick, Whenever i am trying to add connector i am getting this:

Hi RP Team,

Thank you for the detailed investigation and for explaining the suspected "2.0" → "2" conversion.

I have now reproduced the issue independently with a direct HTTP request to the Royal MCP endpoint, so the problem is not limited to ChatGPT/mcp-remote.

My site is:

https://ismartparentinghub.com

Royal MCP version: 1.4.39

I sent a direct POST request to:

/wp-json/royal-mcp/v1/mcp

using the X-Royal-MCP-API-Key header and a standard initialize JSON-RPC request.

The server returns HTTP 200 OK, but the raw response body is:

{"jsonrpc":"2","id":1000,"result":{"protocolVersion":"2025-11-25","serverInfo":{"name":"Royal MCP WordPress","version":"1.4.39"},"capabilities":{"tools":{}}}}

So the incorrect value "2" is present in the actual HTTP response before it reaches ChatGPT or mcp-remote.

I also performed the following tests:

1. LiteSpeed REST API Cache is OFF.
2. /wp-json/royal-mcp is explicitly excluded from LiteSpeed caching.
3. LiteSpeed cache was purged.
4. I repeated the request with cache-busting parameters and Cache-Control: no-cache.
5. I tested using Hostinger’s No Cache Preview, which bypasses the site’s cache.
6. The response still contains "jsonrpc":"2".
7. I temporarily disabled Autoptimize and repeated the test; the response still contains "jsonrpc":"2".
8. QUIC.cloud is disabled.
9. Hostinger has an active CDN, so I am also asking Hostinger to investigate whether their CDN/edge layer is modifying the response.

The relevant hosting environment is:

• Host: Hostinger
• Web server: LiteSpeed
• LiteSpeed server type: LITESPEED_SERVER_ADC
• PHP: 8.3
• WordPress: 7.0.3

The LiteSpeed environment report also confirms:

cache-rest = false

and:

cache-exc = array (
  0 => '/wp-json/easy-mcp-ai/*',
  1 => '/.well-known/*',
  2 => '^/wp-json/royal-mcp',
)

At this point, the most important observation is that the raw HTTP response itself contains "jsonrpc":"2", regardless of cache bypassing.

Could you please advise whether this is a known issue in Royal MCP 1.4.39 under PHP 8.3 / LiteSpeed, and whether the 1.4.40 patch mentioned in your previous reply is available for manual installation before it appears in the WordPress updater?

If 1.4.40 is not yet publicly available, I would be happy to test a development/hotfix build if you have one available.

I am also asking Hostinger to explicitly bypass /wp-json/royal-mcp/* from any CDN, WAF, response optimization, JSON normalization, or other response transformation.

Please let me know if there is anything else you would like me to test.

Thanks for your help!