Alex Llm Attack MCP Server vs 1Claw Vault
A side-by-side look at the Alex Llm Attack MCP Server and 1Claw Vault MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Alex Llm Attack MCP Server for security work over a hosted endpoint; choose 1Claw Vault for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Alex Llm Attack MCP Server when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
ATTACK_MCP_MODE, ATTACK_MCP_HOST, ATTACK_MCP_PORT, ATTACK_MCP_LOG_LEVEL, PORT, MCP_TRANSPORT, HOST. - You want tools like
technique_id, tech_name, results.
Choose 1Claw Vault when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ONECLAW_AGENT_API_KEY, ONECLAW_AGENT_TOKEN, ONECLAW_VAULT_ID, ONECLAW_LOCAL_ONLY, ONECLAW_LOCAL_VAULT, ONECLAW_DAEMON_SOCKET, MCP_TRANSPORT, PORT. - You want tools like
list_secrets, get_secret, put_secret.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 47/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | ATTACK_MCP_MODEATTACK_MCP_HOSTATTACK_MCP_PORTATTACK_MCP_LOG_LEVELPORTMCP_TRANSPORTHOST | ONECLAW_AGENT_API_KEYONECLAW_AGENT_TOKENONECLAW_VAULT_IDONECLAW_LOCAL_ONLYONECLAW_LOCAL_VAULTONECLAW_DAEMON_SOCKETMCP_TRANSPORTPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 3 | 37 |
| Full listing | View Alex Llm Attack MCP Server | View 1Claw Vault |
Tools & capabilities
Alex Llm Attack MCP Server tools 3
technique_idtech_nameresults
1Claw Vault tools 37
list_secretsList all secrets (metadata only — never values)get_secretFetch the decrypted value of a secret by path. Accepts optional `client_share` for MPC vaults.put_secretCreate or update a secret (creates a new version). Response includes `client_share` when the vault has MPC enabled.delete_secretSoft-delete a secret at a pathdescribe_secretGet metadata without fetching the valuerotate_and_storeStore a new value for an existing secret and return the versionrotate_generateServer-side secret rotation with generated value (length, charset configurable)list_versionsList all versions of a secret (version numbers, dates, disabled status)get_env_bundleFetch an env_bundle secret and parse it as KEY=VALUE JSONlist_child_agentsChild agents under a parent (own key/memory/policy, subset of the parent's access; vault ≥ 0.61.30)resolve_envResolve environment variables for a vault and environment (returns the final KEY=VALUE set with precedence applied). When the agent has `env_auto_resolve: true`, omit `environment` and the server uses the agent's tagged environment from the JWT.create_vaultCreate a new vault (auto-shared with the agent's human creator)- +25 more on 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.
Alex Llm Attack MCP Server
{
"mcpServers": {
"alex-llm-attack-mcp-server": {
"url": "http://127.0.0.1:8081/mcp"
}
}
}
1Claw Vault
{
"mcpServers": {
"1claw-vault": {
"command": "npx",
"args": [
"-y",
"@1claw/mcp"
],
"env": {
"ONECLAW_AGENT_API_KEY": "YOUR_ONECLAW_AGENT_API_KEY_HERE",
"ONECLAW_AGENT_TOKEN": "YOUR_ONECLAW_AGENT_TOKEN_HERE",
"ONECLAW_VAULT_ID": "YOUR_ONECLAW_VAULT_ID_HERE",
"ONECLAW_LOCAL_ONLY": "YOUR_ONECLAW_LOCAL_ONLY_HERE",
"ONECLAW_LOCAL_VAULT": "YOUR_ONECLAW_LOCAL_VAULT_HERE",
"ONECLAW_DAEMON_SOCKET": "YOUR_ONECLAW_DAEMON_SOCKET_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Alex Llm Attack MCP Server is categorized under Security and uses a remote HTTP/SSE transport. 1Claw Vault belongs to Security and uses a local stdio subprocess. Pick Alex Llm Attack MCP Server for security work and 1Claw Vault 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.
Alex Llm Attack MCP Server has no declared pricing — check the project's own site. 1Claw Vault has no declared pricing — check the project's own site. Auth: api key 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 alex-llm-attack-mcp-server and 1claw-vault as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Alex Llm Attack MCP Server has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 3 GitHub stars. 1Claw Vault has 61/100 (Good) with 4 views, 0 installs and 3 GitHub stars.