Intodns MCP Server

intodns-mcp npm v1.10.2 Source verified

Published by rosconl — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for IntoDNS.ai — complete DNS, email security, scan, BIMI, API, and citation tools for AI assistants

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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
Source
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 100 − adoption risk = 97/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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 45

Each tool and what it can reach — statically extracted from the published source.

  • check_dmarcingests untrusted input
  • read_llm_discoveryingests untrusted input
  • analyze_raw_emailno sensitive capability
  • analyze_security_headersno sensitive capability
  • cancel_deep_scanno sensitive capability
  • check_bimino sensitive capability
  • check_blacklistno sensitive capability
  • check_dns_propagationno sensitive capability
  • check_email_securityno sensitive capability
  • check_fcrdnsno sensitive capability
Show 35 more tools ↓
  • check_http3no sensitive capability
  • check_mta_stsno sensitive capability
  • check_sender_requirementsno sensitive capability
  • check_smtp_tlsno sensitive capability
  • check_spfno sensitive capability
  • check_tlsa_daneno sensitive capability
  • create_email_testno sensitive capability
  • create_report_snapshotno sensitive capability
  • discover_dkimno sensitive capability
  • explain_issueno sensitive capability
  • flatten_spfno sensitive capability
  • generate_dmarcno sensitive capability
  • generate_dns_fixno sensitive capability
  • generate_security_headersno sensitive capability
  • generate_spfno sensitive capability
  • generate_tlsano sensitive capability
  • get_badge_linkno sensitive capability
  • get_citation_guidanceno sensitive capability
  • get_deep_scan_statusno sensitive capability
  • get_email_testno sensitive capability
  • get_everything_reportno sensitive capability
  • get_hall_of_fameno sensitive capability
  • get_healthno sensitive capability
  • get_pdf_report_linkno sensitive capability
  • get_report_snapshotno sensitive capability
  • get_statsno sensitive capability
  • lookup_dnsno sensitive capability
  • nis2_quickscanno sensitive capability
  • parse_dmarc_reportno sensitive capability
  • poll_email_testno sensitive capability
  • scan_cspno sensitive capability
  • scan_domainno sensitive capability
  • start_deep_scanno sensitive capability
  • validate_dnssecno sensitive capability
  • whois_lookupno sensitive capability

What this scan could not see

Versions 3

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.10.2 latest A 97/100 0 1.13.0 2026-09-07
v1.10.1 A 97/100 0 1.13.0 2026-09-06
v1.9.0 A 97/100 0 1.12.1 2026-08-21

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 · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/intodns-mcp/badge.svg)](https://mcptrustchecker.com/registry/intodns-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/intodns-mcp"><img src="https://mcptrustchecker.com/registry/intodns-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/intodns-mcp/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 intodns-mcp --online

Use the free API → How scoring works

More in Security & Testing