Suriyakumarvijayanayagam 00216ae834 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>

2026-08-13 13:29:34 +05:30

..

api

Expose the catalog to AI clients over MCP at /mcp

2026-08-13 13:14:00 +05:30

core

Fix nutrition upload crash, persist runtime writes, serve API on its own domain

2026-08-13 12:30:45 +05:30

data/seed_catalogs

updates on the backend

2026-08-11 19:16:01 +05:30

infrastructure

Fix nutrition upload crash, persist runtime writes, serve API on its own domain

2026-08-13 12:30:45 +05:30

intelligence

Fix nutrition upload crash, persist runtime writes, serve API on its own domain

2026-08-13 12:30:45 +05:30

services

Fix nutrition upload crash, persist runtime writes, serve API on its own domain

2026-08-13 12:30:45 +05:30

__init__.py

updates on the backend

2026-08-11 19:16:01 +05:30

main.py

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

2026-08-13 13:29:34 +05:30

mcp_server.py

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

2026-08-13 13:29:34 +05:30