# Micarequirements Site MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.micarequirements%2Fsite
Registry id: `mcp-registry/com.micarequirements/site`
Status: live (checked 2026-10-26T19:11:06.234Z)

## Measurements (30 days)

- Uptime: 99.16%
- Checks: 3239
- Outages (90 days): 58

## Install

```json
{
  "mcpServers": {
    "micarequirements-site-mcp-server": {
      "type": "http",
      "url": "https://micarequirements.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http micarequirements-site-mcp-server https://micarequirements.com/mcp
```

## Tools (6)

- `checker_answer`: Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.
- `checker_start`: The first question of the MiCA requirements checker decision guide.
- `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. Nothing is bought, order
- `enquiry_fields`: Every field of the MiCA Requirements enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_
- `submit_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 enquiry_fields) and con

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
