vuln_scan_network — AgentAegis MCP Tool
vuln_scan_network
(vuln scan network) is one of 28 tools on the
AgentAegis
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call vuln_scan_network from your client
- Claude Code AgentAegis vuln_scan_network run in your project directory
- Claude Desktop AgentAegis vuln_scan_network ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentAegis vuln_scan_network ~/.cursor/mcp.json
- VS Code AgentAegis vuln_scan_network .vscode/mcp.json
- Zed AgentAegis vuln_scan_network ~/.config/zed/settings.json
- Windsurf AgentAegis vuln_scan_network ~/.codeium/windsurf/mcp_config.json
- Cline AgentAegis vuln_scan_network ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentAegis vuln_scan_network ~/.gemini/settings.json
- Grok AgentAegis vuln_scan_network .mcp.json (in your project root)
- ChatGPT AgentAegis vuln_scan_network Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentAegis vuln_scan_network Settings → Connectors → Add custom connector
- LangChain AgentAegis vuln_scan_network pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentaegis https://agentaegis-mcp-production.up.railway.app/mcp
Other tools on this server
- compliance_framework_check
- evidence_collect
- control_gap_analysis
- audit_report_generate
- policy_generate
- vuln_scan_web_app
- vuln_prioritize
- cve_lookup
- ssl_tls_audit
- sast_scan
- secret_scan
- dependency_audit
- incident_triage
- threat_intel_lookup
- dns_security_check
- email_security_audit
- access_review
- mfa_audit
- credential_check
- vet_endpoint
- scan_mcp_plugin
- scan_skill
- account_balance
- help
- agent_whoami
- agent_history
- agent_scan_get
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.