← Explore all mcp servers

SUPPLY-CHAIN SECURITY / Socket

Socket MCP Server

Exposes Socket supply-chain analysis so an assistant can check packages for vulnerabilities and suspicious behavior. It supports both local stdio and a hosted Streamable HTTP endpoint at the pinned revision.

“Socket MCP lets AI assistants query Socket's dependency security scores and metadata through the Model Context Protocol (MCP).”

01 / THE REASONING

Why this made the selection.

  • The README at this commit documents a hosted server at https://mcp.socket.dev/ that signs in through the client's OAuth flow, and a self-hosted stdio or HTTP mode that takes a Socket API token.
  • The README lists seven tools (depscore, organizations, alerts, threat_feed, package_files, package_file_contents, package_file_grep), each a query; lib/server.mts registers exactly those seven.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at 7ec4bfb5d1a5fa988ac022eeec460c09955713a7: install options, tool roster, authentication and troubleshooting
  • package.json at the same commit: name @socketsecurity/mcp, version 0.2.1, bin socket-mcp, node >=24
  • LICENSE at the same commit: MIT, Copyright (c) 2025 Socket Inc
  • lib/server.mts, lib/tool-depscore.mts, lib/tool-package-files.mts, lib/tool-logging.mts and lib/tool-audit.mts at the same commit

Our findings

  • The README documents stdio and an HTTP mode; lib/server.mts names stdio and Streamable HTTP as the transports it serializes for.
  • The tools query Socket analysis results; they do not install packages or alter manifests. depscore and the three package-file tools are annotated readOnlyHint: true in source.
  • Correction on 2026-10-13: the description quoted here until now ("Query Socket analysis for package vulnerabilities and supply-chain risk.") does not appear in the README at this commit and was replaced with its opening sentence. A claim that unauthenticated use is rate-limited had no source and was removed.
  • configExample is the README's Cursor block for the hosted server at this commit; it carries no credential because the hosted server uses OAuth.
  • lib/tool-logging.mts wraps every tool handler so each call, successful or not, emits an audit entry through lib/tool-audit.mts; a failed write is logged and does not stop the call.
  • Upstream on 2026-10-13: HEAD 3f72bfcc2b4e4527bc8df98688def8e73ce00122 is ahead of this pin; the repository is not archived, LICENSE is still MIT and package.json still names @socketsecurity/mcp 0.2.1.

Not established by this review

  • Server startup, authentication and tool execution were not tested.
  • The optional socket-gate Claude Code hook was not reviewed beyond the README.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

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

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. The command above is the README's Claude Code line for the hosted server. The client opens a browser to sign in to Socket on first connection; no API key is needed. It was not run.
  2. To self-host instead, the README installs @socketsecurity/mcp globally with pnpm and runs socket-mcp over stdio with SOCKET_API_TOKEN set, or with --http as a service.

Before you start

  • An MCP client that supports remote HTTP servers and OAuth, for the hosted server
  • Node.js 24 or later and a Socket API token with the packages:list scope, for self-hosting

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "socket-mcp": {
      "type": "http",
      "url": "https://mcp.socket.dev/"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/SocketDev/socket-mcp/blob/7ec4bfb5d1a5fa988ac022eeec460c09955713a7/README.md

    Supports: summary, upstreamDescription, install, compatibility, access, transports, whySelected, bestFor, limitations, configExample

  2. Repository licence ↗Checked

    https://github.com/SocketDev/socket-mcp/blob/7ec4bfb5d1a5fa988ac022eeec460c09955713a7/LICENSE

    Supports: license

  3. https://github.com/SocketDev/socket-mcp/blob/7ec4bfb5d1a5fa988ac022eeec460c09955713a7/package.json

    Supports: language, install, compatibility

  4. https://github.com/SocketDev/socket-mcp/blob/7ec4bfb5d1a5fa988ac022eeec460c09955713a7/lib/server.mts

    Supports: whySelected, transports, review

  5. https://github.com/SocketDev/socket-mcp/blob/7ec4bfb5d1a5fa988ac022eeec460c09955713a7/lib/tool-audit.mts

    Supports: limitations, access, review

  6. https://github.com/SocketDev/socket-mcp/blob/7ec4bfb5d1a5fa988ac022eeec460c09955713a7/lib/tool-package-files.mts

    Supports: bestFor, review

Evidence & Ask