Keel vs Agent Security Scanner MCP
A side-by-side look at the Keel and Agent Security Scanner MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Keel for security work as a local process; choose Agent Security Scanner MCP 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 Keel when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
begin_engagement, draft_waves, execute_wave.
Choose Agent Security Scanner MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
scan_security, fix_security, record_security_outcome.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 49/100 · Fair | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 124 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 13 | 23 |
| Full listing | View Keel | View Agent Security Scanner MCP |
Tools & capabilities
Keel tools 13
begin_engagementRegister scope and traffic ceilingsdraft_wavesPropose reachability + template micro-waves; no trafficexecute_waveQueue one background jobwave_statusStage, progress, result; omit `job_id` to listcancel_waveStop a queued or running scannerquery_cardsPrioritized semantic cardssecond_lookRe-run only the originating Nuclei templateassess_exploitabilityCandidate impact, missing evidence, negative control, playbooksstate_impactRecord a hunter hypothesisdraft_proofAllowlisted proof plan; no trafficexecute_proofRun the GET-only playbookengagement_healthCooldowns, budgets, pending waves- +1 more on the listing page
Agent Security Scanner MCP tools 23
scan_securityScan a file for security vulnerabilities. Use verbosity='minimal' for counts only (~50 tokens), 'compact' (default) for actionable info (~200 tokens), 'full' for complete metadata.fix_securityScan a file and return fixes. Use verbosity='minimal' for summary only, 'compact' (default) for fix list, 'full' for complete fixed file content.record_security_outcomeRecord aggregate remediation outcomes after reviewing scanner findings. Sends counts only; never sends code, findings, paths, or rule IDs.list_security_rulesList all available security fix templates and their descriptionscheck_packageCheck if a package name is legitimate or potentially hallucinated (AI-invented)scan_packagesScan code for package imports and check for hallucinated (AI-invented) packages. Use verbosity='minimal' for counts, 'compact' (default) for flagged packages, 'full' for all details.list_package_statsList statistics about loaded package lists for hallucination detectionscan_agent_promptScan a prompt for malicious intent. Returns BLOCK/WARN/LOG/ALLOW. Use verbosity='minimal' for action only, 'compact' (default) for findings, 'full' for audit details.scan_git_diffScan git diff for new security vulnerabilities. Only reports issues on changed lines. Use for PR reviews.scan_projectScan an entire directory for security vulnerabilities with .gitignore support and security grading. Use verbosity='minimal' for grade + counts, 'compact' (default) for top issues, 'full' for all details.scan_agent_actionPre-execution security check for agent actions (bash, file_write, file_read, http_request, file_delete, cron, process_spawn, git, docker). Returns ALLOW/WARN/BLOCK.scan_mcp_serverScan an MCP server's source code for security vulnerabilities: overly broad permissions, missing input validation, data exfiltration, insecure patterns. Returns grade (A-F) and recommendations.- +11 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.
Keel
{
"mcpServers": {
"keel": {
"command": "uvx",
"args": [
"keel"
]
}
}
}
Agent Security Scanner MCP
{
"mcpServers": {
"agent-security-scanner-mcp": {
"command": "npx",
"args": [
"-y",
"agent-security-scanner-mcp"
]
}
}
}
Frequently asked questions
Keel is categorized under Security and uses a local stdio subprocess. Agent Security Scanner MCP belongs to Security and uses a local stdio subprocess. Pick Keel for security work and Agent Security Scanner 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.
Keel has no declared pricing — check the project's own site. Agent Security Scanner 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 keel and agent-security-scanner-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Keel has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Agent Security Scanner MCP has 68/100 (Great) with 2 views, 0 installs and 124 GitHub stars.