Log inSubmit server

AiSOC vs Agent Security Scanner MCP

A side-by-side look at the AiSOC 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.

AiSOC logoAiSOCSecurity · Local subprocess (stdio)Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.59GoodAuth: no auth requiredAgent Security Scanner MCP logoAgent Security Scanner MCPSecurity · Local subprocess (stdio)Security layer for AI agents: blocks prompt injection, detects fake packages, scans vulnerabilities.68GreatAuth: not declared

Verdict: choose AiSOC 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?

AiSOC logoChoose AiSOC when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore AiSOC

Agent Security Scanner MCP logoChoose 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.
Explore Agent Security Scanner MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAiSOC logoAiSOCAgent Security Scanner MCP logoAgent Security Scanner MCP
CategorySecuritySecurity
Quality signal59/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,913124
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed23
Full listingView AiSOC View Agent Security Scanner MCP

Tools & capabilities

AiSOC tools

No tool names declared yet. Check the project README from 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 descriptions
  • check_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 detection
  • scan_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.

AiSOC

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "aisoc": {
      "command": "uvx",
      "args": [
        "aisoc-sandbox"
      ]
    }
  }
}

Agent Security Scanner MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-security-scanner-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agent-security-scanner-mcp"
      ]
    }
  }
}

Frequently asked questions

AiSOC is categorized under Security and uses a local stdio subprocess. Agent Security Scanner MCP belongs to Security and uses a local stdio subprocess. Pick AiSOC 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.

AiSOC is listed as free. Auth: no auth required. 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 aisoc and agent-security-scanner-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, AiSOC has a quality signal of 59/100 (Good) with 0 views, 0 installs and 2,913 GitHub stars. Agent Security Scanner MCP has 68/100 (Great) with 2 views, 0 installs and 124 GitHub stars.

Popular comparisons with AiSOC

Popular comparisons with Agent Security Scanner MCP