Socket MCP
The official Socket MCP server scores the security of npm, PyPI, cargo and other dependencies inside an agent chat.
- 138 ★ on the repository
- Last commit
Extended access
Why this level
- Package names and queries go to the Socket service, and OAuth sign-in opens read access to organization data.
- When self-hosting, the `SOCKET_API_TOKEN` token sits in the client environment.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/socket-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Package names and queries go to the Socket service, and OAuth sign-in opens read access to organization data.
- When self-hosting, the `SOCKET_API_TOKEN` token sits in the client environment.
This is third-party code. Review the repository files before installing.
What it does
Socket MCP gives an agent package security scores from the socket.dev database and dependency metadata. The main tool `depscore` scores a package and version. The others (`organizations`, `alerts`, `threat_feed`, `package_files`, `package_file_contents`, `package_file_grep`) expose the organization, alerts, the threat feed and package files. Connect the server at `https://mcp.socket.dev/` with OAuth sign-in, or run the package yourself over stdio or HTTP with the token in `SOCKET_API_TOKEN`. An optional Socket hook for Claude Code guards package installs.
Who it is for. Developers and security teams who check dependencies without leaving the conversation with an agent.
Good fit when
- An agent suggests adding a package and its security score is needed before installing.
- Before a release, `package.json` is reviewed for risky dependencies.
- Scores for react, lodash and axios are compared in a single request.
- A team reads its Socket organization alerts and threat feed from chat.
Not a fit when
- Signing in to Socket is impossible: even a package score on the public server requires authorization.
- A CI report has to be produced without an agent.
- The client has no remote HTTP MCP support and a local bridge cannot be installed.
Example request
Check the security score for express 4.18.2 and review the dependencies in `package.json` for risky ones.MCP
- Transport
- http, stdio
- Authentication
- OAuth
Environment variables
SOCKET_API_TOKENsecret- Socket API token for self-hosting without OAuth.
Limitations
The hosted server requires Socket sign-in through OAuth for every call, including package scoring, and some clients need an explicit authorization step. Compatibility was verified only for the `organizations` and `depscore` tools and only on some clients; other tools and clients were not tested. Zed Agent sees timeouts after idle periods. Clients limited to stdio need the local `mcp-remote` bridge. The project is in early development and changes quickly.
How to disable. Remove the `socket-mcp` entry from the client settings (in Claude Code `claude mcp remove socket-mcp`), revoke access in Socket and stop your own instance if you ran one.
FAQ
Is an API key required?
Not for the hosted server: sign-in goes through the client's OAuth flow. The `SOCKET_API_TOKEN` token is needed when you self-host without OAuth.
How do I connect the server in Codex CLI?
Run `codex mcp add socket-mcp --url https://mcp.socket.dev/` and finish sign-in in the browser. If an `invalid_scope` page opens, wait for the automatic retry and authorize there.
Which tools are available?
`depscore` scores a package, `organizations` and `alerts` work with the organization, `threat_feed` reads the threat feed, and `package_files`, `package_file_contents` and `package_file_grep` read package files.
How do I run the server myself?
`socket-mcp` starts over stdio and `socket-mcp --http` serves HTTP on port 3000. Pass the token in `SOCKET_API_TOKEN`.
What does the Claude Code hook do?
The optional Socket hook guards package installs. Its setup is described in the commands and workflows section of the repository docs.
Discussion
No questions or reviews yet.
Related
MCP serversSecurity scanner for MCP servers that looks for hardcoded keys, tool poisoning and injection flaws in repository code.
MCP-Shield finds your MCP configs, connects to servers and scans tool descriptions for hidden commands, exfiltration channels and tool shadowing
Security scanner for coding agents: checks code, MCP servers, prompts and model-invented packages, and gives an A to F grade.
A scanner that finds leaked keys, dangerous access and connected models in MCP configs of Claude Desktop, Cursor and VS Code.
A gateway for MCP servers with plugins for masking known secret patterns in text responses, reputation checks and call logging
An MCP server that gives the agent vulnerability triage: NVD data, EPSS, the CISA KEV catalog, MITRE ATT&CK mapping and one-call CVE risk scoring
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Socket MCP (this card) | yes | OAuth | 138 | |
| Snyk Agent Scan | no | 3,217 | finds installed MCP servers and skills on a machine and checks them; Socket MCP answers about dependency package security | |
| SonarQube MCP Server | yes | API key | 679 | exposes quality and security issues from SonarQube; Socket MCP scores third-party packages |
README in short
Setup depends on the client: install links for VS Code and Cursor, commands for Claude Code and Codex, JSON for Windsurf and Factory. Stdio-only clients need the `mcp-remote` bridge, and self-hosting has its own documentation.