contrastapi
Related Servers
Alternatives to contrastapi
- AlicenseAqualityAmaintenanceMCP server for querying the Shodan API and Shodan CVEDB. This server provides tools for IP lookups, device searches, DNS lookups, vulnerability queries, CPE lookups, and more.7227165MIT
- AlicenseAqualityDmaintenanceA MCP server for querying the VirusTotal API. This server provides tools for scanning URLs, analyzing file hashes, and retrieving IP address reports.11301149MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceVulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.MIT
- AlicenseNot gradedqualityFmaintenanceProvides CVE search enriched with EPSS exploit likelihood and CISA KEV status, plus live IP/domain reputation and a real-time threat feed for AI agents.MIT
- AlicenseAqualityAmaintenanceDomain security reconnaissance for AI agents — 13 tools (DNS+DNSSEC, SSL/TLS, HTTP security headers, SPF/DKIM/DMARC email auth, port scan, ASN, RDAP/WHOIS) plus a one-shot security_scan returning a 0–100 Health Score (A–F). Free, no API key.15861MIT
- AlicenseNot gradedqualityDmaintenanceProvides multi-source vulnerability intelligence for AI-powered security operations, combining NVD CVSS, CISA KEV, and EPSS scores without requiring an API key.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time threat intelligence for AI agents, enabling checks on IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, and malicious AI-skill/MCP-tool definitions against a free database of 890K+ IOCs.-
- AlicenseNot gradedqualityCmaintenanceProvides real-time vulnerability intelligence including CVE lookup, EPSS exploit probability, and CISA KEV status from free APIs, enabling AI assistants to prioritize CVEs by real-world risk.MIT
TDQS
Scored across 55 tools
Most tools have distinct, well-scoped purposes (e.g., cve_lookup vs cve_search vs bulk_cve_lookup), but there is overlap between contrastapi functions like domain_report and audit_domain, and between ioc_lookup and threat_intel which both cover reputation data. The tech_stack_cve_audit tool is redundantly described as 'MCP-only' yet has no REST counterpart, creating mild confusion about the API surface.
The majority of tools follow a consistent `<domain>_<action>` convention (cve_lookup, cve_search, domain_report, asn_lookup, etc.), making the surface approachable. However, there are exceptions like contrastapi-specific names (contrastapi_get_domain) and some tools lack the clear action suffix (cve_search vs cve_lookup), introducing minor inconsistency.
55 tools is a large number but the domain (CVE/recon) is broad enough to warrant a substantial surface. There is some redundancy—for example, domain_report, audit_domain, and separate lookup tools overlap in functionality—but the count remains justified by the breadth of the security-recon domain.
The tool surface covers the full vulnerability-research workflow: discovery (cve_search, cve_lookup), enrichment (exploit_lookup, kev), and response (bulk_cve_lookup). There is comprehensive coverage of related domains including email verification, phone lookup, IP/ASN, URL scanning, malware scanning, and AI-related scanning (ai_* tools). The missing pieces would be things like a true Q&A-style chat loop, but for a security API, this is near-complete.