com.blackveilsecurity/dns — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

DNS and email-domain security scanning

What we know

Scan SPF, DKIM, DMARC, DNSSEC, TLS and related domain-security posture. DNS & email security scanner — 51 tools for SPF, DMARC, DKIM, DNSSEC, SSL, and more.

Maintenance / activity evidence

72 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scan only domains you are authorized to assess; remediation must be independently validated. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Scan only domains you are authorized to assess; remediation must be independently validated.

Scan only domains you are authorized to assess; remediation must be independently validated.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 72 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package blackveil-dns; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have blackveil-dns permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Scan only domains you are authorized to assess; remediation must be independently validated.

Scan only domains you are authorized to assess; remediation must be independently validated.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

72 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/blackveil-dns

Exact implementation source: https://www.npmjs.com/package/blackveil-dns ↗
Reviewed resource type: MCP Server
Package identity: npm:blackveil-dns

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
blackveil-dns
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Hosted no-auth passive public DNS checks; OAuth optional operator-dependent
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Hosted no-auth passive public DNS checks; OAuth optional operator-dependent | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions
claude mcp add --transport http blackveil-dns https://dns-mcp.blackveilsecurity.com/mcp
Configure / authenticate
MCP100 setup guide
Hosted HTTP public endpoint requires no API key for baseline; optional operator OAuth/owner key is separate. Claude Desktop .mcpb option.
Check connection
Suggested check
`curl https://dns-mcp.blackveilsecurity.com/health` checks endpoint only; inspect tools for MCP.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `blackveil-dns`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove blackveil-dns

Official Documentation & Sources

What it does

Scan SPF, DKIM, DMARC, DNSSEC, TLS and related domain-security posture. DNS & email security scanner — 51 tools for SPF, DMARC, DKIM, DNSSEC, SSL, and more.

Capability: Security & Testing
Resource type: MCP Server
Industry: Cybersecurity
Best fit: DNS and email-domain security scanning

Representative uses

Run email authentication checks
Inspect DNS security findings

Limitations

Scan only domains you are authorized to assess; remediation must be independently validated.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Scan only domains you are authorized to assess; remediation must be independently validated.
Data handling: Scan only domains you are authorized to assess; remediation must be independently validated.
Cost: Not verified; check vendor terms
Risk and cautions: Scan only domains you are authorized to assess; remediation must be independently validated.

Access scope and cautions

Write actions: Not verified
Risk level: medium
Security notes: Scan only domains you are authorized to assess; remediation must be independently validated. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Run email authentication checks; Inspect DNS security findings.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Scan only domains you are authorized to assess; remediation must be independently validated.

What data-handling boundary should I consider?

Scan only domains you are authorized to assess; remediation must be independently validated.

What limitations and risks should I check before use?

Scan only domains you are authorized to assess; remediation must be independently validated. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.