Point the docs at the real API domain, mcp.nearle.ai.in

The deployment landed on mcp.nearle.ai.in, not the mcp.catalogue.nearle.ai.in
these references were written against. Only comments, README and .env.example
are affected - nothing reads the hostname at runtime - but a wrong host in the
connection snippet is a wrong host somebody pastes into an MCP client.

API_CORS_ORIGINS is unchanged: it takes the FRONTEND's origin
(catalogue.nearle.ai.in), not the API's, so moving the API does not affect it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

README.md

@@ -92,7 +92,7 @@ long-running client has to refresh. Raise the TTL if that is a problem.
   "mcpServers": {
     "nearle-catalogue": {
       "type": "http",
-      "url": "https://mcp.catalogue.nearle.ai.in/mcp",
+      "url": "https://mcp.nearle.ai.in/mcp",
       "headers": { "Authorization": "Bearer <token>" }
     }
   }