MCP server

Use other LLMs with ReviewOS

The c07-evidence-mcp-server exposes the evidence-review prototype to any MCP client — Claude Desktop, VS Code, or any MCP client — as 4 read-only tools. It calls the live Next.js API first and falls back to the deterministic checker when the app is offline, so the demo never breaks.

Live deployment: https://dail.ysfff.online — point C07_BASE_URL at it and no local server is needed. Note: this preview URL is behind Vercel login, so remote clients get the deterministic fallback (same verdicts, source shown as deterministic) — run the app locally for live-LLM mode.

4 tools, one workflow

c07_list_applicationsList applications with completion %. Start here to get valid APP-xxx ids.
c07_get_applicationFull record + evidence excerpts for one id, e.g. APP-102.
c07_analyze_evidenceLive POST /api/analyze with deterministic fallback. Returns status + issues.
c07_draft_applicant_requestLive POST /api/draft-request with template fallback. Drafts text, sends nothing.

Connect in under 5 minutes

Claude Desktop

Add to claude_desktop_config.json, replacing the path with your checkout. It points at the live deployment, so no local server is needed — swap in http://localhost:3000 to use your own dev server instead.

claude_desktop_config.json
{
  "mcpServers": {
    "c07-evidence": {
      "command": "node",
      "args": ["/absolute/path/to/dail-hackathon/mcp-server/dist/index.js"],
      "env": { "C07_BASE_URL": "https://dail.ysfff.online" }
    }
  }
}
Remote HTTP

Streamable HTTP endpoint for web clients and shared demos — paste the URL straight into your MCP client:

MCP server URL
https://dail.ysfff.online/api/mcp
client config (remote)
{
  "c07-evidence-remote": {
    "url": "https://dail.ysfff.online/api/mcp"
  }
}

Running the app yourself? Use http://localhost:3000/api/mcp instead.

Example walkthrough
example tool calls
1. c07_list_applications → {} → see APP-101 / 102 / 103
2. c07_get_application → {"id": "APP-102"} → spot the org-name mismatch
3. c07_analyze_evidence → {"id": "APP-102"} → needs_clarification
4. c07_draft_applicant_request → {"id": "APP-102"} → copy the draft
5. Finally: c07_analyze_evidence → {"id": "APP-103"} → review_ready