Problem detail
GET/api/v1/problems/{source}/{id}Fetch a normalized problem record by platform source and problem ID.
View detailsQuery problem records, fetch daily challenges, search similar problems, and connect tool clients through MCP without switching between fragmented data sources.
The docs pages stay public. API, status, and MCP access depend on whether token auth is enabled for this deployment.
| Route | Auth Disabled | Auth Enabled |
|---|---|---|
/ |
Public | Public |
/health |
Public | Public |
/api/v1/* |
Public | Protected |
/status |
Public | Protected |
/mcp |
Public | Protected |
/api/v1/problems/{source}/{id}Fetch a normalized problem record by platform source and problem ID.
View details/api/v1/dailyFetch the current LeetCode daily challenge with the existing fallback behavior.
View details/api/v1/similarSearch related problems by free-text query against the public similarity index.
View detailsStart with a single problem-detail request to confirm auth, response shape, and source-key usage.
curl \
-H "Authorization: Bearer <token>" \
"http://127.0.0.1:7856/api/v1/problems/leetcode/1"
Review all ten public HTTP routes with paths, auth rules, inputs, response shapes, and examples.
See transport guidance, tool summaries, and examples for the five exposed MCP tools.