Statewrightgate MCP vs Safeinstall

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

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

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

Which MCP server should you choose?

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

Safeinstall logoChoose Safeinstall when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStatewrightgate MCP logoStatewrightgate MCPSafeinstall logoSafeinstall
CategorySecuritySecurity
Quality signal48/100 · Fair41/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars03
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools4Not listed

Tools & capabilities

Statewrightgate MCP tools 4

  • check_state_transition
  • explain_blocked_action
  • suggest_next_states
  • export_transition_receipt

Safeinstall 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.

Statewrightgate MCP

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

Safeinstall

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

Frequently asked questions

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

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

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