dns_security_check — AgentAegis MCP Tool
dns_security_check
(dns security check) 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 dns_security_check from your client
- Claude Code AgentAegis dns_security_check run in your project directory
- Claude Desktop AgentAegis dns_security_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AgentAegis dns_security_check ~/.cursor/mcp.json
- VS Code AgentAegis dns_security_check .vscode/mcp.json
- Zed AgentAegis dns_security_check ~/.config/zed/settings.json
- Windsurf AgentAegis dns_security_check ~/.codeium/windsurf/mcp_config.json
- Cline AgentAegis dns_security_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AgentAegis dns_security_check ~/.gemini/settings.json
- Grok AgentAegis dns_security_check .mcp.json (in your project root)
- ChatGPT AgentAegis dns_security_check Settings → Connectors → Advanced → Developer mode
- Claude.ai AgentAegis dns_security_check Settings → Connectors → Add custom connector
- LangChain AgentAegis dns_security_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentaegis https://agentaegis-mcp-production.up.railway.app/mcpOther tools on this server
- compliance_framework_check
- evidence_collect
- control_gap_analysis
- audit_report_generate
- policy_generate
- vuln_scan_network
- vuln_scan_web_app
- vuln_prioritize
- cve_lookup
- ssl_tls_audit
- sast_scan
- secret_scan
- dependency_audit
- incident_triage
- threat_intel_lookup
- 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.