Skip to main content
Glama
Sign In

site

by com.micarequirements
OverviewDiscussionsAdmin

Server Details

MiCA Requirements: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not...

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

The three checker_* tools are mostly distinct: checker_start and checker_answer drive step-by-step navigation while checker_tree dumps the full decision graph, though the overlap between walking the guide and reading the whole tree could cause misselection. The enquiry_* tools and submit_enquiry are clearly separated by role (describe vs. fields vs. submit).

Naming Consistency3/5

Two recognizable clusters exist (checker_* and enquiry_*), but the conventions differ: checker_start/checker_answer/checker_tree are noun-prefixed, while submit_enquiry uses a verb_noun form and enquiry_describe/enquiry_fields are noun_noun. It's readable but not a single predictable pattern.

Tool Count5/5

Six tools is well-scoped for a decision guide plus an enquiry flow. Each tool maps to a distinct step (navigate, inspect tree, describe, list fields, submit), with no filler.

Completeness4/5

The checker (start/answer/tree) and the enquiry lifecycle (describe/fields/submit with two-step confirmation) are covered end to end. Minor gaps remain, such as an enquiry status/withdrawal tool after submission, but core flows have no dead ends.

Available Tools

6 tools
checker_answerAnswer a question, get the next stepAInspect

Given a question id and the chosen option (its choice index), return the next question or the final verdict.

Inputs: choice (required), question (required).

checker_startStart: MiCA requirements checkerBInspect

The first question of the MiCA requirements checker decision guide.

Inputs: no named parameters.

checker_treeThe whole decision treeAInspect

Every question, option and verdict of the MiCA requirements checker guide, for reasoning end to end.

Inputs: no named parameters.

enquiry_describeWhat you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)AInspect

Read first. States plainly what submit_enquiry does on MiCA Requirements: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

Inputs: no named parameters.

enquiry_fieldsThe questions the enquiry asksAInspect

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_enquiry keyed by field key.

Inputs: no named parameters.

submit_enquirySubmit an ENQUIRY to human providers (two steps; not a purchase)AInspect

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 consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three relevant crypto regulatory advisers, chosen by MiCA Requirements, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Inputs: answers (required), consent (required), confirmation.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources