SecKit MCP
Related Servers
Alternatives to SecKit MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to perform cybersecurity tasks including hash analysis, CVE lookup, HTTP header auditing, WHOIS/OSINT, payload decoding, password strength evaluation, and threat report generation.7MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to perform defensive security tasks such as vulnerability detection, CVE lookup, phishing/link safety checks, and security report generation via MCP tools.23-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform digital forensics analysis including memory analysis, file metadata inspection, and threat-intelligence lookups.3 npmISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform cybersecurity analysis including RDAP lookup, DNS analysis, SSL inspection, security header detection, and more, returning structured security reports.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose projects, deployments, releases, runbooks, tasks, tenants, Kubernetes resources, machines, certificates, accounts, and interruptions, with optional write operations and read-only safeguards.266 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to ask Purple AI hunting questions, run PowerQueries over the Singularity Data Lake, and read alerts, vulnerabilities, misconfigurations and asset inventory from a SentinelOne console, plus VirusTotal and public CVE lookups. It is read-only and accepts per-request console credentials, making it stateless and multi-tenant.Apache 2.0
TDQS
Scored across 9 tools
Each tool maps to a clearly distinct operation: threat-intel lookups (lookup_cve, explain_mitre_technique, search_mitre), IOC handling (defang_iocs/refang_iocs), log parsing, hashing, and password breach checks. The only near-pair, search_mitre vs explain_mitre_technique, is explicitly differentiated (ranked matches vs full details). An agent can select tools confidently.
All nine tools follow a consistent snake_case verb_noun pattern (check_password_breach, lookup_cve, parse_log_line, defang_iocs, hash_text, etc.). The defang/refang pair even signals their inverse relationship through naming.
Nine tools is well within the ideal 3-15 range and every tool earns its place by covering a distinct security-analysis task. No redundant or filler tools are present.
The surface covers core SOC workflows: vulnerability and ATT&CK intel, IOC defang/refang, log parsing, event-id explanation, and hashing. Minor gaps exist (e.g. no hash/URL/IP reputation lookup, no encode/decode or base64 tools), but the core lifecycle is solid and workable.