MCP Risk

Directory / server

com.blackveilsecurity/dns

This directory entry reports an automated security scan of com.blackveilsecurity/dns, scanned 2026-07-28. Trust grade A rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via remote-tools-list

A 100/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as com.blackveilsecurity/dns. 1 finding
  • Registry entry: com.blackveilsecurity/dns ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 0 days ago
  • Stars: 8
  • License: NOASSERTION
  • Security policy (SECURITY.md): absent
INFO Published package is consistent and attested §1.3

No published package associated with this server (remote-only or non-npm/PyPI source).
PASS Tool surface is inspectable and proportionate §2.1–§2.4
80 tool(s) enumerated. Capabilities detected: network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 4 findings
  • Tools exposed: 80
  • list_brand_audit_watches: network-egress
  • register_brand_audit_watch: network-egress
  • Detected capabilities: network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://dns-mcp.blackveilsecurity.com/mcp
UNVERIFIABLE Authentication required §3.2

Endpoint rejected the probe (HTTP 400); whether it requires authentication could not be determined.
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://dns-mcp.blackveilsecurity.com
INFO No known vulnerabilities (OSV.dev) §4.1

No package to query (remote-only server).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 163 server-supplied text item(s).

Score history

DateGradeScore
2026-07-28A100/100
2026-07-28A100/100
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.