What exactly is 'config drift' in this context?

Config drift means an agent's live operational parameters—like its system prompt or allowed permissions—have changed from the version that was originally approved and secured. It's a security and stability risk.

Does this MCP check the agent's actual code, or just its settings?

It focuses on the configuration parameters, not the underlying source code. It uses hashing to verify the integrity of the defined settings, like prompts and capability lists.

How does the SHA-256 hashing help?

SHA-256 creates a unique digital fingerprint for the entire configuration. If even one character changes in one field, the resulting hash changes completely, immediately alerting you to the drift.

What kind of information does the drift report provide?

The report gives a detailed comparison, showing the field name, the type of change (addition, deletion, modification), and the specific old and new values.

Is this capability useful for detecting malicious changes?

Yes. Because it requires a known good baseline, any unauthorized modification, whether malicious or accidental, will cause the hash to fail the integrity check.

How does the drift detection work?

The server computes a deterministic SHA-256 hash of critical configuration sections and compares it against a stored baseline. If the hashes differ, it performs a deep inspection to find the exact changed fields.

What is considered a high-severity drift?

Changes to 'permissions' are considered the highest risk, followed by modifications to the 'system_prompt'.

Can I use this with Cursor or Claude Desktop?

Yes, this MCP server can be connected to Cursor, Claude Desktop, VS Code, Windsurf, and any other MCP-compatible client via Vinkius Edge.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Agent Config Drift Detector to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Keep your LLM agents running exactly as intended.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through Agent Config Drift Detector.

01
Evaluate risk level
This capability calculates the severity of a detected drift. It takes the nature of the configuration changes and outputs a risk score, helping you prioritize fixes.
02
Get drift report
Use this capability to get a detailed breakdown of configuration differences. It provides a clear, field-by-field comparison between two versions of an agent's setup.
03
Check config integrity
This capability determines if the agent's current configuration has deviated from its authorized baseline. It returns a simple yes/no answer regarding integrity.

Real work

What teams actually run

Post-Deployment Audit

After a major release, run the MCP to confirm that all production agents still match the secure baseline configuration.

Permission Change Review

When a developer updates an agent's allowed capabilities or permissions, use the MCP to verify the change hasn't introduced a security gap.

Incident Response

If an agent starts behaving erratically, use the MCP to check for configuration drift as a primary cause before investigating code changes.

Compliance Reporting

Generate audit logs proving that critical agent parameters have remained within defined, secure boundaries over time.

One connector, every AI

Agent Config Drift Detector works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Agent Config Drift Detector to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

904ms average. Fast in production.

Agent Config Drift Detector is checked daily against the live service.

Daily averagePeak 1132ms

Oct 3Today

Fastest day: 736ms
Slowest day: 1132ms
14-day trend: Improving-12%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Agent Config Drift Detector, so you can see the experience inside your AI.

It does not authenticate your account with Agent Config Drift Detector. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Agent Config Drift Detector Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_nCSg5c2fIbvLAVJJFLRFF3DWB4M0DjzgJpK3LTAA/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Agent Config Drift Detector capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "agent-config-drift-detector-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_nCSg5c2fIbvLAVJJFLRFF3DWB4M0DjzgJpK3LTAA/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Agent Config Drift Detector in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Agent Config Drift Detector owners hand off.

This MCP is built for teams responsible for production AI systems. If you manage agents that run critical business logic, you need to know when their underlying code or parameters change without your team knowing. It gives you immediate visibility into configuration security.

01
ML Ops Engineer
Uses the MCP to audit agent deployments and ensure that production models haven't drifted from the approved training configuration.
02
Security Analyst
Runs checks to detect unauthorized changes to system prompts or access permissions, flagging potential security breaches.
03
DevOps Engineer
Integrates the MCP into CI/CD pipelines to automatically validate agent configurations before deployment.

FAQ

Questions Agent Config Drift Detector owners ask.

01
What exactly is 'config drift' in this context?
Config drift means an agent's live operational parameters—like its system prompt or allowed permissions—have changed from the version that was originally approved and secured. It's a security and stability risk.
02
Does this MCP check the agent's actual code, or just its settings?
It focuses on the configuration parameters, not the underlying source code. It uses hashing to verify the integrity of the defined settings, like prompts and capability lists.
03
How does the SHA-256 hashing help?
SHA-256 creates a unique digital fingerprint for the entire configuration. If even one character changes in one field, the resulting hash changes completely, immediately alerting you to the drift.
04
What kind of information does the drift report provide?
The report gives a detailed comparison, showing the field name, the type of change (addition, deletion, modification), and the specific old and new values.
05
Is this capability useful for detecting malicious changes?
Yes. Because it requires a known good baseline, any unauthorized modification, whether malicious or accidental, will cause the hash to fail the integrity check.
06
How does the drift detection work?
The server computes a deterministic SHA-256 hash of critical configuration sections and compares it against a stored baseline. If the hashes differ, it performs a deep inspection to find the exact changed fields.
07
What is considered a high-severity drift?
Changes to 'permissions' are considered the highest risk, followed by modifications to the 'system_prompt'.
08
Can I use this with Cursor or Claude Desktop?
Yes, this MCP server can be connected to Cursor, Claude Desktop, VS Code, Windsurf, and any other MCP-compatible client via Vinkius Edge.

Explore

More in Security

Connect Agent Config Drift Detector to Claude, Cursor, ChatGPT & more

Your AI does the work. We keep it safe and sound.

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-03

Evaluate risk level

Get drift report

Check config integrity

What teams actually run

Post-Deployment Audit

Permission Change Review

Incident Response

Compliance Reporting

Building your own app? The connector is yours to use.

Agent Config Drift Detector Connector

Claude Desktop

ML Ops Engineer

Security Analyst

DevOps Engineer

What exactly is 'config drift' in this context?

Does this MCP check the agent's actual code, or just its settings?

How does the SHA-256 hashing help?

What kind of information does the drift report provide?

Is this capability useful for detecting malicious changes?

How does the drift detection work?

What is considered a high-severity drift?

Can I use this with Cursor or Claude Desktop?

Oppo Game Open Platform AI Connector

LLM Output Format Drift Detector AI Connector

Claude Conversation Drift Detector AI Connector

zrok (Open-Source Tunnel) AI Connector

Suggestions

LangSmith (LLM Observability & Hub) AI Connector

Langfuse (LLM Tracing & Evals) AI Connector

Open-Meteo AI Connector

Socket.dev (Dependency Security) AI Connector