SecKit MCP
Related Servers
Alternatives to SecKit MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query vulnerability management, security center, identity exposure, and cloud security data read-only, and to export Active Directory data from identity exposure into a BloodHound attack graph.MIT
- 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 read-only scans of local projects, Git history, GitHub Actions workflows, machines, and GitHub accounts for supply-chain malware indicators, and to access cleanup and recovery guidance.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform digital forensics analysis including memory analysis, file metadata inspection, and threat-intelligence lookups.8 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.-
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.