Safetyreplay MCP vs Semgrep

A side-by-side look at the Safetyreplay MCP and Semgrep MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Safetyreplay MCP logoSafetyreplay MCPSecurity · Remote HTTP/SSEPaid remote MCP for safety replays, policy gates, eval receipts, and release evidence.49FairAuth: api key requiredSemgrep logoSemgrepSecurity · Local subprocess (stdio)Scan code for security vulnerabilities using Semgrep.48FairAuth: no auth required

Verdict: choose Safetyreplay MCP for security work over a hosted endpoint; choose Semgrep for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Safetyreplay MCP logoChoose Safetyreplay MCP when

  • You need dedicated capabilities in the Security domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You want tools like run_safety_replay, check_policy_gate, record_eval_receipt.
Explore Safetyreplay MCP

Semgrep logoChoose Semgrep when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Semgrep

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSafetyreplay MCP logoSafetyreplay MCPSemgrep logoSemgrep
CategorySecuritySecurity
Quality signal49/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthAPI key requiredNo auth required
PricingPaid serviceFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars017,253
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools5Not listed

Tools & capabilities

Safetyreplay MCP tools 5

  • run_safety_replay
  • check_policy_gate
  • record_eval_receipt
  • suggest_control_fix
  • export_release_evidence

Semgrep tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Safetyreplay MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "safetyreplay-mcp": {
      "url": "https://safetyreplay.clauxel.com/mcp"
    }
  }
}

Semgrep

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "semgrep-semgrep": {
      "command": "uvx",
      "args": [
        "semgrep"
      ]
    }
  }
}

Frequently asked questions

Safetyreplay MCP is categorized under Security and uses a remote HTTP/SSE transport. Semgrep belongs to Security and uses a local stdio subprocess. Pick Safetyreplay MCP for security work and Semgrep for security.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Safetyreplay MCP is listed as a paid service. Auth: api key required. Semgrep is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add safetyreplay-mcp and semgrep-semgrep as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Safetyreplay MCP has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Semgrep has 48/100 (Fair) with 1 views, 0 installs and 17,253 GitHub stars.