Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RuleDrift

NPM · RULE-DRIFT · SCANNED SEP 20

Test whether AI agents retain critical instructions as conversations grow.

Available components

0 this week 97 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ri7in/rule-drift). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 36 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 110 tokens (~55/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the RuleDrift MCP server?

RuleDrift runs locally as an npm package, launched with npx -y rule-drift. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · rule-drift

# add to Claude Code
claude mcp add ri7in-rule-drift -- npx -y rule-drift
// .cursor/mcp.json
{
  "mcpServers": {
    "ri7in-rule-drift": {
      "command": "npx",
      "args": [
        "-y",
        "rule-drift"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ri7in-rule-drift": {
      "command": "npx",
      "args": [
        "-y",
        "rule-drift"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ri7in-rule-drift -- npx -y rule-drift
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ri7in-rule-drift": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "rule-drift"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ri7in-rule-drift --command npx --arg -y --arg rule-drift
# ~/.hermes/config.yaml
mcp_servers:
  ri7in-rule-drift:
    command: "npx"
    args: ["-y", "rule-drift"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ri7in-rule-drift": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "rule-drift"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ri7in-rule-drift -t stdio -c npx -a -y rule-drift
// mcp.json
{
  "mcpServers": {
    "ri7in-rule-drift": {
      "command": "npx",
      "args": [
        "-y",
        "rule-drift"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 13 Sept 26 +1
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/rule-drift@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ri7in/rule-drift
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ri7in/rule-drift/.github/workflows/release.yml@refs/tags/v0.1.1
Rekor log index 2466730107
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:cc3e2f73e0cdfc713d20c7c51d721e1c475e4149b6a83cf71e0e4c6e876a8b1aa0e121597a6e451596ce4f5c2cb68fc3b0fb517b1b2cfcfcb043484c7

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~78 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
run_suite ~41

Run every configured conversation and isolated rule probe. Response bodies are omitted from the returned report.

NameTypeReqDescription
configPathstringConfiguration path inside the MCP workspace root.
NameTypeReqDescription
configPathstringyes
passRatenumber|nullyes
probesintegeryes
probesPassedintegeryes
reportobjectyes
statusstringyes
suitestringyes

No examples provided.

validate_suite ~37

Validate a RuleDrift configuration without calling its model or command adapter.

NameTypeReqDescription
configPathstringConfiguration path inside the MCP workspace root.
NameTypeReqDescription
configPathstringyes
rulesintegeryes
scenariosintegeryes
suitestringyes
validbooleanyes

No examples provided.

Common questions

What is the RuleDrift MCP server?

RuleDrift is an MCP server listed in the public MCP registry as io.github.ri7in/rule-drift. Test whether AI agents retain critical instructions as conversations grow. This page covers its npm package (rule-drift).

Is the RuleDrift MCP server safe to use?

RuleDrift scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the RuleDrift MCP server expose?

RuleDrift exposes 2 tools: validate_suite, run_suite. Their descriptions and schemas cost roughly 78 tokens of context every time the server is loaded.

Is the RuleDrift MCP server still maintained?

RuleDrift is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the RuleDrift MCP server under?

RuleDrift declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.