Before your agent changes a dependency, see what else relies on it.
A credential can look unused in the repo your agent is editing while another connected repo still uses it. Wirecheck shows the known consumers with file and line evidence, and what stays unresolved. Re-scan afterward to see what remains.
Regex and JSON parsing. No LLM is involved in detection.
Every relationship records the file and line of its first match.
A recognized reference with no matching declaration is reported, not dropped.
Verification reads the latest scans and lists what still references the target.
Your agent checks the repos it can reach. Wirecheck keeps a record of the ones you connect.
Agents can search several repos when they have access. The cost is doing it again for every change. Wirecheck scans connected repos for supported patterns, stores the results, and lets you query them before and after an edit.
Your agent wants to remove or change a credential or MCP server. Preflight lists the files in your connected repos that reference it.
Each finding carries the file and line behind it, so the agent can check why a reference exists before editing.
Re-scan, then verify which known or unresolved consumers remain.
The agent removed zendesk-mcp from one repo. Two others still reference it.
Test fixture: real CLI output from three small fixture repos, not customer data.
- AgentRemove zendesk-mcp.
- Edited repo, after the edit0 references left.
- Wirecheck, before the edit5 consumers in 3 connected repos, plus 1 scheduled job.
- After the edit and a re-scan4 known consumers remain in 2 repos.CONSUMERS_REMAIN
- support-agent: mcp.json:3WORKFLOW, MEDIUMRemoved
- support-agent: src/support-bot.ts:10AGENT, HIGHRemoved
- ops-jobs: config/mcp.json:3WORKFLOW, MEDIUMStill references it
- ops-jobs: jobs/nightly-ticket-sync.ts:11AGENT, HIGHStill references it
- ops-jobs: jobs/nightly-ticket-sync.ts:6SCHEDULE (node-cron), HIGHStill references it
- billing-tools: .mcp.json:3WORKFLOW, MEDIUMStill references it
A consumer is a file with a detected static reference. WORKFLOW is the default type for a file with no agent signal, not necessarily a CI workflow. Wirecheck does not know whether the code runs.
No known consumers is not the same as safe.
If a reference to an MCP server matches no declaration, Wirecheck marks the server UNKNOWN and lists its consumers as unresolved, not known. Patterns it does not recognize may not appear at all. See supported detections, or read when grep is enough.
Context before the change. Evidence after.
Your agent only uses Wirecheck if you tell it to. One instruction in CLAUDE.md or AGENTS.md has it run preflight first. See the setup.
wirecheck preflight zendesk-mcp --operation REMOVE5 direct, 1 indirect, 0 orphaned integrationsAffects: acme/billing-tools, acme/ops-jobs, acme/support-agentwirecheck verify retirement zendesk-mcp --operation REMOVECONSUMERS_REMAIN4 known consumers still reference this
Output trimmed, from the same test fixture. The CLI runs from the repository today and is not on npm yet. Setup.
Verification ends in one of three outcomes. See what each means.
Try it on real code. Keep it current as the code changes.
3 lifetime scans, up to 3 repositories.
No lifetime scan limit (50 per 24h), scheduled re-scans, up to 20 repositories, and the retirement queue.