Categories › AI & Agents › Multi-agent, orchestration & workflows
MiCA Requirements: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...
Remote server: your requests and data go to micarequirements.com. Claude Code: claude mcp add --transport http site https://micarequirements.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
checker_start — The first question of the MiCA requirements checker decision guide.checker_answer — Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.checker_tree — Every question, option and verdict of the MiCA requirements checker guide, for reasoning end to end.enquiry_describe — Read first. States plainly what submit_enquiry does on MiCA Requirements: it starts an enquiry with human providers who quote directly. Nothenquiry_fields — Every field of the MiCA Requirements enquiry: key, label, type, whether required, help text and the allowed options where there are any. Passubmit_enquiry — Submits an enquiry to MiCA Requirements: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.