Check your dependencies in every Cursor chat.
Three steps, about a minute. No account, no key: the agent sends package names, never versions, and compares the answer with your lockfile.
- 01
Add the MCP server
One click opens Cursor and adds it. Or paste this in
~/.cursor/mcp.jsonfor every project, or.cursor/mcp.jsonfor this one.~/.cursor/mcp.jsonAdd to Cursor{ "mcpServers": { "patchwire": { "url": "https://patchwire.monowire.dev/mcp" } } } - 02
Add a project rule
Save this as
.cursor/rules/patchwire.mdc. WithalwaysApply: true, Cursor includes it in every Agent chat of the project; a plain.mdfile there is ignored..cursor/rules/patchwire.mdc--- description: Check dependencies against Patchwire alwaysApply: true --- At the start of each session, and before you install, upgrade or deploy: call Patchwire get_advisories with the dependency names from package.json, compare the returned ranges with the lockfile, and use latest_safe to pick a fixed version for anything affected.
- 03
Open the Agent chat
Ask for anything. With the rule in its context, the agent checks the packages in package.json against Patchwire first, and again before it installs, upgrades or ships. Rules apply to the Agent chat, not to Tab completions.
Claude Code. Set up in a minute.
One command adds the server, then a SessionStart hook: in every new session, Claude checks before it answers.
Open the Claude Code setupSet up? Now watch your stacks.
The dashboard shows every alert on the stacks you follow, read every hour from the source.
Open the dashboard