io.github.magist-io/magist

Est-ce que io.github.magist-io/magist est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.magist-io/magist » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• compute_requirements≈ 546 tokens

  Run Magist’s deterministic compliance engine over a product description (features, target markets, audience age bands, optional business model) and return the regulations and Controls that may be triggered, a complexity tier with a numeric score, a blocker count, and a per-audience cohort breakdown. The call also creates or refreshes an idempotent public report URL for the receipt, retained for up to 90 days. Deterministic and reproducible: the same inputs always produce the same output, with no LLM in the path. Returns which obligations may apply for research purposes; it is not a determination that they do apply, and does not replace counsel. Consult a licensed attorney before relying on the result.

  Paramètres, retour & exemple (4)

  Paramètres

  • markets · array · requis
    Target market codes, e.g. ["eu","us","california","uk"]. Call list_feature_catalog for the full set of valid ids; an id outside the catalog is rejected with an actionable error.
  • features · array · requis
    Product feature ids from the closed catalog, e.g. ["account-creation","text-chat","iap","ai-content-gen"]. Call list_feature_catalog for the full set of valid ids; an id outside the catalog is rejected with an actionable error.
  • audiences · array · optionnel
    Audience age bands. Exactly these three ids exist.
  • businessModel · object · optionnel
    Optional business-model context (role, participants, transactionInvolvement, dataHandling). Validated server-side via the same allowlist as /api/compute-requirements.

  Exemple d'appel

  {"name": "compute_requirements", "arguments": {"markets": [], "features": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_controls≈ 200 tokens

  Given a regulation id, return the compliance Controls that may satisfy it, each with a priority signal (blocker / required / evaluate / best-practice) and a short summary of the work involved. Returns research information about typical control mappings, not a determination that a given product needs them. Consult counsel for scoping.

  Paramètres, retour & exemple (1)

  Paramètres

  • regulationId · string · requis
    Magist regulation id, e.g. "coppa".

  Exemple d'appel

  {"name": "find_controls", "arguments": {"regulationId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_counsel≈ 337 tokens

  Search Magist’s open counsel directory for law firms by jurisdiction and practice area. Returns an editorial / firm-claimed directory to help a user identify licensed attorneys to consult. Inclusion is not endorsement; verify bar status and conflicts independently before engaging.

  Paramètres, retour & exemple (3)

  Paramètres

  • language · string · optionnel
    Optional preferred language. Accepted for forward-compatibility; not yet a filter at launch.
  • jurisdiction · string · requis
    Jurisdiction code, e.g. "us", "us-ca", "eu", "uk". A country/region name ("Australia", "United States") is also accepted and resolved to its code; the code actually searched comes back as `resolvedJurisdiction`. A code matches itself and its sub-jurisdictions, never the reverse — a firm listed only for "us" is not returned for "us-mt".
  • practiceArea · string · optionnel
    Optional practice-area / compliance-domain id, e.g. "data-privacy", "age-verification".

  Exemple d'appel

  {"name": "find_counsel", "arguments": {"jurisdiction": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_vendors≈ 244 tokens

  Given a Control id, list third-party vendors and in-house approaches that may implement it, with effort/cost signals and a source-disclosure (editorial research vs vendor submission). Magist does not accept payment from vendors and does not rank or endorse them. Returns a neutral catalog for research; evaluate fit independently.

  Paramètres, retour & exemple (2)

  Paramètres

  • controlId · string · requis
    Magist Control id, e.g. "age-verification-process".
  • jurisdiction · string · optionnel
    Optional market/region filter, e.g. "eu". Applied only when a vendor declares supported regions.

  Exemple d'appel

  {"name": "find_vendors", "arguments": {"controlId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_enforcement≈ 339 tokens

  Return recent regulatory enforcement actions from Magist’s catalog, optionally filtered by regulation id and a since-date. Each action includes the penalty, authority, a primary-source link, and (where authored) a practitionerAnalysis: a hedged, third-person editorial note on what the action illustrates, informational context that never addresses a specific product. penaltyAmount is null when no monetary amount is recorded (pending, confidential, annulled, or non-monetary outcomes; the amount string carries the honest description). Returns historical facts about what regulators have done: informational context, not a prediction about a specific product.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max actions to return (default 10, max 50).
  • since · string · optionnel
    ISO date (YYYY-MM-DD) or year (YYYY). Returns actions on or after this date.
  • regulationId · string · optionnel
    Filter to actions related to this regulation id.

  Exemple d'appel

  {"name": "get_enforcement", "arguments": {"limit": 1, "since": "texte", "regulationId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_feature_catalog≈ 182 tokens

  Return Magist’s closed catalogs of valid product feature ids and target market ids, each with a short human-readable label -- the exact identifiers compute_requirements accepts as "features" and "markets". Use this to validate ids before calling compute_requirements; ids outside these catalogs are rejected with an actionable error. Deterministic and reproducible; this is reference data, not itself a regulatory determination.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_feature_catalog", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_regulation≈ 216 tokens

  Look up one regulation by its Magist id and return structured research information: title, citation, jurisdiction, status, review dates, a plain-language summary, and the Controls that may satisfy it. Returns facts about what a regulation says, not a determination of how it applies to a specific product. Consult counsel for situation-specific questions.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Magist regulation id, e.g. "gdpr", "coppa", "ai-act". Use search_regulations to discover ids.

  Exemple d'appel

  {"name": "lookup_regulation", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_regulations≈ 438 tokens

  Search Magist’s regulation corpus by keyword with optional filters (jurisdiction, domain, status, content-review status, coverage depth). Returns a paginated list of matching regulations with permanent citation URLs. Deterministic: the same query and filters return the same results every time. Returns research information for discovery, not a determination of which regulations apply to a specific product.

  Paramètres, retour & exemple (8)

  Paramètres

  • limit · integer · optionnel
    Page size (default 10, max 25).
  • query · string · optionnel
    Free-text keywords. Optional; omit to browse with filters only.
  • domain · array · optionnel
    Compliance domain ids, e.g. ["data-privacy","age-verification"].
  • offset · integer · optionnel
    Pagination offset (default 0).
  • status · string · optionnel
    Lifecycle status filter, e.g. "active", "proposed".
  • jurisdiction · array · optionnel
    Jurisdiction codes/names, e.g. ["EU","US"].
  • coverageDepth · string · optionnel · deep | standard | thin
    Filter by editorial coverage depth.
  • contentReviewStatus · string · optionnel · reviewed | draft
    Filter by practitioner-review state.

  Exemple d'appel

  {"name": "search_regulations", "arguments": {"limit": 1, "query": "texte", "domain": [], "offset": 1, "status": "texte", "jurisdiction": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_ai_answer≈ 295 tokens

  Verify a Magist grounding-proof token: the "groundingProof" field on a regulation or control record from the REST API (GET /api/v1/regulations/{id} or /api/v1/controls/{id}) when the server has signing enabled. MCP tool responses do not carry these tokens. Proves the citation was genuinely served by Magist's server for that exact atom at that exact corpus version; it does NOT verify legal correctness or that any obligation applies to a product. Returns valid:false with a reason when the token is missing, malformed, unsigned, or fails signature verification; this is expected when the record never carried a token (signing is an opt-in server setting).

  Paramètres, retour & exemple (1)

  Paramètres

  • token · object · requis
    The groundingProof object exactly as received on a prior response (carries alg, mgstId, corpusVersion, quoteHash, nonce, and the signature fields). Pass it back unmodified.

  Exemple d'appel

  {"name": "verify_ai_answer", "arguments": {"token": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://magist.io/api/mcp