Safeinstall vs Statewrightgate MCP

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

Safeinstall logoSafeinstallSecurity · Local subprocess (stdio)Local-first supply-chain security gate for npm/pnpm/bun: typosquat, release age, provenance checks41FairAuth: not declaredStatewrightgate MCP logoStatewrightgate MCPSecurity · Remote HTTP/SSEA paid remote MCP for Statewright, built to return verdicts, receipts, usage logs, and audit-ready J48FairAuth: not declared

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

Which MCP server should you choose?

Safeinstall logoChoose Safeinstall when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
Explore Safeinstall

Statewrightgate MCP logoChoose Statewrightgate MCP when

  • You need dedicated capabilities in the Security domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like check_state_transition, explain_blocked_action, suggest_next_states.
Explore Statewrightgate MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSafeinstall logoSafeinstallStatewrightgate MCP logoStatewrightgate MCP
CategorySecuritySecurity
Quality signal41/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars30
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listed4

Tools & capabilities

Safeinstall tools

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

Statewrightgate MCP tools 4

  • check_state_transition
  • explain_blocked_action
  • suggest_next_states
  • export_transition_receipt

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.

Safeinstall

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "safeinstall": {
      "command": "npx",
      "args": [
        "-y",
        "create-next-app"
      ]
    }
  }
}

Statewrightgate MCP

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

Frequently asked questions

Safeinstall is categorized under Security and uses a local stdio subprocess. Statewrightgate MCP belongs to Security and uses a remote HTTP/SSE transport. Pick Safeinstall for security work and Statewrightgate MCP 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.

Safeinstall has no declared pricing — check the project's own site. Statewrightgate MCP has no declared pricing — check the project's own site. 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 safeinstall and statewrightgate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Safeinstall has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 3 GitHub stars. Statewrightgate MCP has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.