Is @crewhaus/mcp-host MCP safe to give an agent?
A factual risk summary built from @crewhaus/mcp-host’s real tool surface, execution model, and verification history — not a vibe. Trust score 41/100.
No tool handshake yet — capability surface unverified.
Runs on the vendor's infrastructure; you connect over the network. No untrusted code runs on your machine, but you grant the hosted service access.
Installs via npx (`npx -y @crewhaus/mcp-host`) — it pulls and executes third-party code; pin versions and review the source.
No auth scopes captured yet (scope extraction runs during the sandboxed handshake, gated until configured). Treat unconfirmed scopes as unknown, not as “none.”
Wrap @crewhaus/mcp-host in a governed Loadout — scoped permissions, approval rules on write/destructive tools, and audit logging — instead of handing your agent raw access.
Build a governed LoadoutSee also: full server page · setup · alternatives