Bring Supply Chain Security
to Cursor
Learn how to connect Socket.dev (Dependency Security) to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Socket.dev (Dependency Security) MCP Server?
Connect Socket.dev to your AI agent to proactively defend against supply chain attacks. This MCP server allows you to analyze open-source packages, scan manifest files, and monitor for malicious dependencies without leaving your development environment.
What you can do
- Package Analysis — Get deep security scores and identify issues for specific packages using PURLs (e.g., npm, PyPI, Go).
- Dependency Scanning — Upload manifest files like
package.jsonorrequirements.txtto create comprehensive security scans. - Report Management — List and retrieve detailed security reports, including policy compliance and alert data.
- Threat Intelligence — Access a real-time feed of malicious packages detected by Socket's analysis engine.
- Organization Oversight — Manage scans across different organizations and monitor your API usage quotas.
How it works
- Subscribe to this server
- Enter your Socket.dev API Token
- Start auditing your dependencies directly from Claude, Cursor, or any MCP-compatible client
Stop guessing if a package is safe. Let your AI agent use Socket's industry-leading telemetry to catch typosquatting, backdoors, and telemetry before they enter your codebase.
Who is this for?
- Security Engineers — Automate the review of new dependencies and monitor organizational security posture.
- Developers — Check package safety scores instantly before running
npm installorpip install. - DevOps Teams — Integrate dependency scanning into the conversation to quickly triage security reports.
Built-in capabilities (10)
Provide manifest files data (e.g., package.json, requirements.txt). Create a new scan by uploading manifest files
Delete a scan
g., pkg:npm/babel). Get issues/alerts for a specific package
g., pkg:npm/babel). Get the security score for a specific package
Check remaining API quota
Get detailed report data
Get scan metadata and status
Access the real-time threat feed
List organizations the token has access to
List reports
Why Cursor?
Cursor's Agent mode turns Socket.dev (Dependency Security) into an in-editor superpower. Ask Cursor to generate code using live data from Socket.dev (Dependency Security) and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Socket.dev (Dependency Security) in Cursor
Socket.dev (Dependency Security) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Socket.dev (Dependency Security) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Socket.dev (Dependency Security) in Cursor
The Socket.dev (Dependency Security) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Socket.dev (Dependency Security) for Cursor
Every tool call from Cursor to the Socket.dev (Dependency Security) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I check if a specific npm package is safe to use?
You can use the get_package_score tool by providing the Package URL (PURL), such as pkg:npm/lodash. The agent will return a security score and risk assessment.
Can I scan my entire project's dependencies at once?
Yes! Use the create_scan tool and provide the content of your manifest files (like package.json). Socket will analyze all dependencies and generate a report.
How do I see the specific security issues found in a package?
Use the get_package_issues tool with the package's PURL. It will list all alerts, such as telemetry, install scripts, or known vulnerabilities associated with that package.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
TimezoneDB
5 toolsManage global time — audit timezones and offsets via AI.
Nue.io Revenue
10 toolsManage the revenue lifecycle via Nue.io — track product catalogs, price tags, and revenue workflows directly from your AI agent.
GitScrum Time Tracking
28 toolsTrack time and budgets via GitScrum — start timers, log hours, analyze productivity, monitor burn-down, and review standup summaries directly from any AI agent.
NCDC Climate Data Online
10 toolsAccess authoritative historical weather and climate data via NCDC — track datasets, stations, and climate records directly from your AI agent.