io.github.mrpkk/drift

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

Au dernier audit MCP Hub, le serveur MCP « io.github.mrpkk/drift » 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 3 outils

• drift_check≈ 752 tokens

  Check ONE proposed action against a signed agent mandate BEFORE it happens. Returns {"verdict": "ALLOW"|"DENY", "rule": <name>} plus a report with a ledger fingerprint. Six rules run in a fixed order, so a refusal names the most important reason rather than an incidental one: amount, payee, audience, currency, window, intent. Anything unclassified is DENY. Use immediately before any action that spends money, moves a credential or changes state on someone else's behalf. Do NOT use to: verify mandate signatures (AP2 does that, and this server runs after signature verification), execute the action (it only decides), or certify that an intent is truthful — "intent" arrives from the agent and is untrusted input. An agent that lies within its limits still leaves a ledger entry; proving what really happened is attest's job, not this one's. Amounts are integer minor units (cents), never floats. Window bounds are inclusive. Fully idempotent: the same inputs always give the same verdict and the mandate is never mutated.

  Paramètres, retour & exemple (2)

  Paramètres

  • action · object · requis
    The action being proposed.
  • mandate · object · requis
    The signed authority being enforced. Treat as read-only input.

  Exemple d'appel

  {"name": "drift_check", "arguments": {"action": {}, "mandate": {}}}

  Exemple de retour

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

• drift_explain≈ 206 tokens

  Return the six enforcement rules in the exact order they are applied, each with a plain-language reason it exists. Takes no mandate and no action. Use when a refusal did not make sense, or before explaining a denial to someone whose mandate was rejected. A refusal you cannot explain is one nobody will trust. Do NOT use it to check an action — it performs no check, and cannot predict which rule will fire, only the order they are tried in. Constant output, fully idempotent, opens no files, contacts no host.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "drift_explain", "arguments": {}}

  Exemple de retour

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

• drift_session≈ 282 tokens

  Check a SEQUENCE of proposed actions against one mandate. Returns {submitted, allowed, denied, breach_by_rule, fingerprint}. Use for a whole plan or batch, not a single action — use drift_check for that. The fingerprint is the point: rewriting or reordering any earlier decision changes the hash, so tampering with history becomes visible instead of silent. Do NOT use it to execute the actions, or as evidence of what actually happened. It reports what was PROPOSED against a mandate you supply. Read-only. Idempotent for a fixed action list. Amounts in integer minor units, as in drift_check.

  Paramètres, retour & exemple (2)

  Paramètres

  • actions · array · requis
    Proposed actions in order. Order affects the fingerprint.
  • mandate · object · requis
    Same shape as in drift_check.

  Exemple d'appel

  {"name": "drift_session", "arguments": {"actions": [], "mandate": {}}}

  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://drift.rta.lat/mcp