dev.exactlane/preflight

Est-ce que dev.exactlane/preflight est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.exactlane/preflight » 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 1 outils

• check_mcp_capability≈ 1115 tokens

  Before relying on an MCP capability, answer one question about it: does this exact revision satisfy the requirements your workflow declares? Call it for new work, after a dependency changes, after your own requirements change, or when an integration has already failed and you need to know whether the capability is why (the public triggers are NEW_WORK, DEPENDENCY_CHANGE, REQUIREMENTS_CHANGE, INTEGRATION_FAILURE, OTHER_REAL_WORK). You supply both sides: a capability snapshot you already hold and your workflow requirements. Nothing is fetched and no endpoint is probed, so the answer is reproducible from what you sent and is only ever as good as that snapshot. You get back a verdict with per-check results, coverage, and the limits of the check itself. That is evidence, not an instruction: the caller owns CONTINUE, UPDATE_INTEGRATION, and HOLD, and no verdict maps to any of them. Optional previous (an earlier snapshot and its finished report) adds a revision_receipt comparing that conclusion with this revision. Budget before calling: a Preview grant allows three checks, while POST /v0/snapshot-lint validates argument and requirements shape with no credential and no quota, so start there when unsure. This tool never writes usage-events (usage_event_created is always false) and never discloses the internal Preview bearer; attest your own decision afterwards on a finished owned check.

  Paramètres, retour & exemple (6)

  Paramètres

  • previous · object · optionnel
    Optional. Makes this a revision-aware check (POST /v0/revision-checks semantics). Send the snapshot and finished report from an earlier check of the same capability_key with identical requirements. Exactlane re-evaluates them instead of trusting the report and never looks up earlier calls. Omit for the ordinary check.
  • snapshot · object · requis
    Caller-provided MCP capability snapshot. No live endpoint is accepted.
  • requirements · object · requis
    Caller workflow requirements using a supported mcp-consumer-fit schema
  • capability_key · string · requis
    Opaque caller capability key; same contract as POST /v0/capabilities
  • revision_label · string · optionnel
    Optional revision label; defaults to mcp-adapter
  • profile_version · string · optionnel · 0.1 | 0.2 | 0.3
    Optional mcp-consumer-fit version; inferred from requirements when omitted

  Exemple d'appel

  {"name": "check_mcp_capability", "arguments": {"snapshot": {}, "requirements": {}, "capability_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": {}, "decision_note": "texte", "revision_receipt": {}, "usage_event_created": true, "caller_owns_operational_decision": true}}

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://exactlane.dev/mcp