Socket MCP server for Claude, Codex and Cursor

What your AI apps can do with Socket

Score package security and quality
Inspect package files and alerts

Socket MCP tools

7 tools, listed by Toolstile from the server itself on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does	Suggested rule
`depscore`	Look up Socket scores when evaluating or adding dependencies. Returns available 0-100 supply chain, quality, maintenance, vulnerability, and license scores, plus report links. Lower scores mean higher risk. Use exact versions; ^ and ~ are stripped. Use 'unknown' to let Socket …	Allow (read-only)
`organizations`	List the Socket organizations the authenticated user belongs to with the `organizations` tool. Use this to discover the `org_slug` values needed by other org-scoped tools (e.g. `alerts`, `threat_feed`), or when the user asks which organizations they have access to.	Allow (read-only)
`alerts`	List the latest security alerts for a Socket organization with the `alerts` tool. Requires `org_slug` — call the `organizations` tool first if you don't have it. Supports filtering by severity, category, status, artifact type/name, alert type, and repo. Use this to surface …	Allow (read-only)
`threat_feed`	Look up items in the Socket organization threat feed with the `threat_feed` tool. Requires `org_slug` — call the `organizations` tool first if you don't have it. Returns recently flagged packages (malware, typosquats, obfuscated code, etc.) along with a `nextPageCursor` for …	Allow (read-only)
`package_files`	List the files published in a package using the `package_files` tool from Socket. Returns a tree of file paths, each with its size and blob hash, for any package on a supported ecosystem (npm, pypi, gem, cargo, maven, golang, nuget, chrome, openvsx). Useful for inspecting what a …	Allow (read-only)
`package_file_contents`	Read a single file from a package using the `package_file_contents` tool from Socket. Pass the `hash` printed next to each entry in `package_files` output. Returns up to 1 MB of UTF-8 text; binary files return metadata only.	Allow (read-only)
`package_file_grep`	Search a single file from a package for lines matching a JavaScript regular expression. Pass the `hash` printed next to each entry in `package_files` output. The file is fetched from Socket once per session and cached, so repeated greps on the same hash skip the network. Returns …	Allow (read-only)

Suggested access for each AI app

7 tools marked read-only (depscore, organizations, alerts, threat_feed, package_files, package_file_contents, …). These are usually safe to allow.

These are hints the server reports about its own tools, not guarantees.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Socket connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Socket to a workspace (no sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Socket tool, give Cursor only the read tools, or keep Socket away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Socket MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Socket in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Socket endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http socket 'https://mcp.socket.dev/'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "socket": {
      "url": "https://mcp.socket.dev/"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Socket MCP documentation for what your client needs.

Before you connect

No account needed. Socket may rate limit anonymous use.

Server details

Detail	Value
Publisher	Socket
Endpoint	`https://mcp.socket.dev/`
Authentication	No sign-in
Categories	Development
Tool list	7 tools, observed 29 October 2026 (discovery)

Socket MCP documentation