ContrastAPI MCP Server

https://api.contrastcyber.com/mcp Remote v1.35.2

Published by api.contrastcyber.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

29 security tools for AI agents — CVE, OSINT, threat intel, code security. No API key needed.

Trust grade
A
91/100
Last scanned get badge →
Trust
A · 91/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 94 − adoption risk = 91/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Suspicious external URL in tool metadata MTC-INJ-URL-1 exfiltration

2. Client adoption risk — 94 − 3 = 91. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

medium Open-world tool "email_verify" also reads sensitive dataMTC-CAP-004

Tool "email_verify" declares openWorldHint=true — it interacts with entities outside the trust boundary — while also reading sensitive data. That combination is a canonical lethal-trifecta indicator.

Fix: Separate outward-facing tools from sensitive-data reads; require confirmation between them.

Location: tool email_verify

medium Suspicious external URL in tool metadataMTC-INJ-URL-1

A hardcoded link to a request/paste/webhook sink (or raw IP) appears in the inputSchema.properties.url.description of tool "redirect_chain". Tool metadata pointing the model at a fixed external endpoint is a data-exfiltration channel — the classic "send the output to …" poisoning.

Evidence: https://bit.ly/3xyz

Fix: A legitimate tool takes its destination as a validated parameter; it does not hardcode a webhook/paste sink in its description.

Location: tool redirect_chain · inputSchema.properties.url.description

medium Unconstrained URL/host parameter "url" on "redirect_chain"MTC-CAP-007

Tool "redirect_chain" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool redirect_chain · inputSchema.properties.url

Tools 55

Each tool and what it can reach — enumerated from the running server.

  • brand_assetsingests untrusted input
  • check_headersingests untrusted input
  • contrast_scaningests untrusted input
  • email_verifyreads sensitive data
  • geo_auditingests untrusted input
  • hash_lookupingests untrusted input
  • ip_lookupingests untrusted input
  • redirect_chainingests untrusted input
  • robots_txtingests untrusted input
  • seo_auditingests untrusted input
Show 45 more tools ↓
  • sigma_rule_lookupingests untrusted input
  • asn_lookupno sensitive capability
  • atlas_case_study_lookupno sensitive capability
  • atlas_case_study_searchno sensitive capability
  • atlas_technique_lookupno sensitive capability
  • atlas_technique_searchno sensitive capability
  • audit_domainno sensitive capability
  • bulk_atlas_technique_lookupno sensitive capability
  • bulk_cve_lookupno sensitive capability
  • bulk_ioc_lookupno sensitive capability
  • bulk_sigma_rule_lookupno sensitive capability
  • calculate_risk_scoreno sensitive capability
  • check_dependenciesno sensitive capability
  • check_injectionno sensitive capability
  • check_secretsno sensitive capability
  • cve_leadingno sensitive capability
  • cve_lookupno sensitive capability
  • cve_searchno sensitive capability
  • cwe_lookupno sensitive capability
  • d3fend_attack_coverageno sensitive capability
  • d3fend_defense_for_attackno sensitive capability
  • d3fend_defense_lookupno sensitive capability
  • d3fend_defense_searchno sensitive capability
  • dns_lookupno sensitive capability
  • domain_reportno sensitive capability
  • email_disposableno sensitive capability
  • email_mxno sensitive capability
  • email_security_postureno sensitive capability
  • exploit_lookupno sensitive capability
  • get_cvss_detailsno sensitive capability
  • ioc_lookupno sensitive capability
  • kev_detailno sensitive capability
  • password_checkno sensitive capability
  • phishing_checkno sensitive capability
  • phone_lookupno sensitive capability
  • scan_headersno sensitive capability
  • ssl_checkno sensitive capability
  • subdomain_enumno sensitive capability
  • tech_fingerprintno sensitive capability
  • tech_stack_cve_auditno sensitive capability
  • threat_intelno sensitive capability
  • threat_reportno sensitive capability
  • username_lookupno sensitive capability
  • wayback_lookupno sensitive capability
  • whois_lookupno sensitive capability

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.35.2 latest A 91/100 3 1.10.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 91/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/api-contrastcyber-com/badge.svg)](https://mcptrustchecker.com/registry/api-contrastcyber-com)
HTML
<a href="https://mcptrustchecker.com/registry/api-contrastcyber-com"><img src="https://mcptrustchecker.com/registry/api-contrastcyber-com/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/api-contrastcyber-com/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://api.contrastcyber.com/mcp --online

Use the free API → How scoring works

More in Security & Testing