The handler now properly handles notifications (no 'id' field) by
returning 202 No Content instead of rejecting with method-not-found.
Fixes "sending notifications/initialized: Bad Request" error.
- Added notifications/initialized and notifications/cancelled handlers
- Unknown notifications silently ignored per JSON-RPC spec
- API route returns 202 for notifications
💘 Generated with Crush
Assisted-by: Crush:deepseek-v4-flash-free
Introduces an HTTP-based MCP handler (POST /mcp) that exposes polysearch's
search capabilities to AI agents via the Model Context Protocol. Supports
tools/list, tools/call (web_search, image_search), and initialize methods.
The endpoint shares the existing SearchRunner, proxy pool, and Bearer auth,
so no additional infrastructure or credentials are needed.
💘 Generated with Crush
Assisted-by: Crush:deepseek-v4-flash-free
