What is a ghost variable?

A ghost variable is a key that your application code tries to access but is not defined in your environment configuration files.

What is dead configuration?

Dead configuration refers to environment variables that are declared in your files but are never actually used by your code.

Which files can this MCP scan?

It can scan .env files, docker-compose.yml, Kubernetes ConfigMaps, and source code files like .js, .ts, and .py.

How do I use this with my AI client?

You connect to the MCP through Vinkius, and then your client can call the capabilities directly to perform audits or extractions.

Does this work with Kubernetes?

Yes, it can extract keys from Kubernetes ConfigMaps to ensure they match your code.

What files does the auditor scan for declarations?

It scans files like .env, .env.example, docker-compose.yml, and Kubernetes ConfigMaps using the extract_keys capability.

How can I find variables used in my TypeScript code?

Use the extract_used_keys capability by providing the contents of your .ts or .js files.

What does a 'missing' variable mean?

A missing variable is one that your code attempts to access (e.g., process.env.API_KEY) but which was not found in any of your declaration files.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Environment Variable Usage Auditor to your AI

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. Stop production crashes caused by mismatched configuration files.

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 Environment Variable Usage Auditor.

01
Audit consistency
This capability compares your declared environment variables against the keys actually used in your code to find mismatches.
02
Extract keys
This capability pulls variable keys directly from configuration files like .env, docker-compose.yml, or Kubernetes ConfigMaps.
03
Extract used keys
This capability scans your source code files, such as .js, .ts, or .py, to identify which environment variables are actually being called.

Real work

What teams actually run

Pre-deployment Audits

Run a check before pushing to production to ensure all required keys are present in your environment.

Docker Cleanup

Identify which variables in your docker-compose.yml are no longer needed by your application.

Kubernetes Sync

Verify that your ConfigMaps contain everything your application code is looking for.

Refactoring Support

Find old environment variables that were left behind after you renamed or removed code logic.

One connector, every AI

Environment Variable Usage Auditor 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 Environment Variable Usage Auditor 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

719ms average. Fast in production.

Environment Variable Usage Auditor is checked daily against the live service.

Daily averagePeak 807ms

Oct 3Today

Fastest day: 558ms
Slowest day: 807ms
14-day trend: Improving-10%

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 Environment Variable Usage Auditor, so you can see the experience inside your AI.

It does not authenticate your account with Environment Variable Usage Auditor. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Environment Variable Usage Auditor Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_Z2JEnF7s23UACpfnJgUdNSc7xX3d1ATvjzSLO4Je/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 — Environment Variable Usage Auditor capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "environment-variable-usage-auditor-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Z2JEnF7s23UACpfnJgUdNSc7xX3d1ATvjzSLO4Je/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 Environment Variable Usage Auditor in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Environment Variable Usage Auditor owners hand off.

This MCP is built for engineers who manage containerized applications and want to prevent deployment failures.

01
DevOps Engineers
They use it to verify that Kubernetes ConfigMaps and Docker Compose files match the application requirements.
02
Backend Developers
They use it to ensure new features don't break due to missing environment keys.
03
Site Reliability Engineers
They use it to audit environment parity across different deployment stages.

FAQ

Questions Environment Variable Usage Auditor owners ask.

01
What is a ghost variable?
A ghost variable is a key that your application code tries to access but is not defined in your environment configuration files.
02
What is dead configuration?
Dead configuration refers to environment variables that are declared in your files but are never actually used by your code.
03
Which files can this MCP scan?
It can scan .env files, docker-compose.yml, Kubernetes ConfigMaps, and source code files like .js, .ts, and .py.
04
How do I use this with my AI client?
You connect to the MCP through Vinkius, and then your client can call the capabilities directly to perform audits or extractions.
05
Does this work with Kubernetes?
Yes, it can extract keys from Kubernetes ConfigMaps to ensure they match your code.
06
What files does the auditor scan for declarations?
It scans files like .env, .env.example, docker-compose.yml, and Kubernetes ConfigMaps using the extract_keys capability.
07
How can I find variables used in my TypeScript code?
Use the extract_used_keys capability by providing the contents of your .ts or .js files.
08
What does a 'missing' variable mean?
A missing variable is one that your code attempts to access (e.g., process.env.API_KEY) but which was not found in any of your declaration files.

Explore

More in Security

Connect Environment Variable Usage Auditor 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

Audit consistency

Extract keys

Extract used keys

What teams actually run

Pre-deployment Audits

Docker Cleanup

Kubernetes Sync

Refactoring Support

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

Environment Variable Usage Auditor Connector

Claude Desktop

DevOps Engineers

Backend Developers

Site Reliability Engineers

What is a ghost variable?

What is dead configuration?

Which files can this MCP scan?

How do I use this with my AI client?

Does this work with Kubernetes?

What files does the auditor scan for declarations?

How can I find variables used in my TypeScript code?

What does a 'missing' variable mean?

Env Variable Config Validator AI Connector

Prompt Template Variable Injector Checker AI Connector

EPA Envirofacts (Environmental Data) AI Connector

Dotenv Parser Engine AI Connector

Suggestions

Vertiv Environet AI Connector

OpenMeter (Usage Metering for AI/Cloud Billing) AI Connector

Togai (Usage Metering & Pricing) AI Connector

Eurostat Environment — EU Green Data AI Connector