site

Crypto Licence Costs: the site's own MCP server — calculator, enquiry (enquiry = a human...

Sollte ich dies verwenden

Qualität und Sicherheit

B
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
56%
Qualität der Benennung
88%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~720Tokens (Tool-Definitionen)
~823 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.56% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "site": {
      "url": "https://cryptolicencecosts.com/mcp"
    }
  }
}

Remote-Endpunkte

https://cryptolicencecosts.com/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (5)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢calculator_describe

The inputs this calculator takes (with units, ranges and defaults), the outputs it returns, and the assumptions and tables behind it.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢calculate(jurisdiction, serviceClass, services)

Run the Crypto licence cost calculator calculator: Published regulator fees, year one; Published regulator fees, year one; How this regulator charges; MiCA minimum capital you must hold (Annex IV). Missing inputs fall back to their documented defaults.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "jurisdiction": {
      "type": "string",
      "enum": [
        "mt",
        "fr",
        "ie",
        "de",
        "nl"
      ],
      "description": "Where are you applying?",
      "default": "mt"
    },
    "serviceClass": {
      "type": "string",
      "enum": [
        "1",
        "2",
        "3"
      ],
      "description": "Highest class of service you will provide",
      "default": "2"
    },
    "services": {
      "type": "number",
      "minimum": 1,
      "maximum": 10,
      "description": "How many of the ten crypto-asset services will the authorisation cover?",
      "default": 3
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_describe

Read first. States plainly what submit_enquiry does on Crypto Licence Costs: 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.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡enquiry_fields

Every field of the Crypto Licence Costs 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.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟡submit_enquiry(answers, consent, confirmation)

Submits an enquiry to Crypto Licence Costs — 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: "Happy for my details to go to a relevant crypto licensing adviser, who'll contact me directly."

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "answers": {
      "type": "object",
      "additionalProperties": {
        "type": [
          "string",
          "number",
          "boolean"
        ]
      },
      "description": "the person's answers, keyed by field key"
    },
    "consent": {
      "type": "boolean",
      "description": "true only when the person has agreed to: Happy for my details to go to a relevant crypto licensing adviser, who'll contact me directly."
    },
    "confirmation": {
      "type": "string",
      "description": "the confirmation token from step 1, after the person has approved the summary"
    }
  },
  "required": [
    "answers",
    "consent"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet5 Tools
verifiziertVersion nicht aufgezeichnet5 Tools