# io.github.CloudCorpRecords/dnsprobe (oci · ghcr.io/cloudcorprecords/dnsprobe)

DNS and email-security diagnostics via the keyless intodns.ai API: scans, SPF, DMARC, headers.

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/dnsprobe`: 69/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-dnsprobe/reneturcios-dnsprobe.md), [page](https://verifymcp.io/servers/cloudcorprecords-dnsprobe/reneturcios-dnsprobe)
- oci · `ghcr.io/cloudcorprecords/dnsprobe`: 41/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-dnsprobe/ghcr-io-cloudcorprecords-dnsprobe.md), [page](https://verifymcp.io/servers/cloudcorprecords-dnsprobe/ghcr-io-cloudcorprecords-dnsprobe)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/dnsprobe`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 908 tokens (~43/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/dnsprobe MCP server?

io.github.CloudCorpRecords/dnsprobe runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/dnsprobe:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-dnsprobe -- docker run --rm -i ghcr.io/cloudcorprecords/dnsprobe:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-dnsprobe": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dnsprobe:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-dnsprobe": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dnsprobe:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-dnsprobe -- docker run --rm -i ghcr.io/cloudcorprecords/dnsprobe:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-dnsprobe": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dnsprobe:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-dnsprobe:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/dnsprobe:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-dnsprobe": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dnsprobe:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-dnsprobe": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/dnsprobe:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 40)

First indexed and scored.

## MCP tools (21)

### `scan_domain` (~41 tokens)

Fast scan of a domain with grade, score, DNS/email/security results, issues, and recommendations.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `lookup_dns` (~96 tokens)

Look up DNS records for a domain (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV, PTR, DNSKEY, DS and more), optionally for one record type.

Input parameters:

- `domain` (string, required): Domain name to look up DNS records for.
- `type` (string): Single record type to return, such as A, MX, or TXT; omit to return all types.

### `validate_dnssec` (~41 tokens)

Validate the DNSSEC chain, DS/DNSKEY records, and signing algorithms for a domain.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `check_dns_propagation` (~35 tokens)

Check DNS propagation for a domain across global resolvers.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `whois_lookup` (~48 tokens)

WHOIS/RDAP lookup for a domain or IP: registrar, status, nameservers, dates, and abuse contact.

Input parameters:

- `query` (string, required): Domain name or IP address to look up.

### `check_spf` (~37 tokens)

Parse and validate a domain's SPF record, including its recursive lookup graph.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `flatten_spf` (~47 tokens)

Flatten a domain's SPF include/a/mx graph to literal ip4/ip6 addresses under the 10-lookup limit.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `discover_dkim` (~30 tokens)

Discover DKIM selectors for a domain.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `check_dmarc` (~35 tokens)

Parse and validate a domain's DMARC record and policy.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `parse_dmarc_report` (~58 tokens)

Parse a DMARC aggregate (RUA) XML report locally into structured sources, counts, and SPF/DKIM/DMARC results.

Input parameters:

- `xml` (string, required): DMARC aggregate (RUA) report XML content to parse.

### `check_bimi` (~43 tokens)

Check BIMI DNS, the hosted SVG/logo URL, and VMC/CMC readiness for a domain.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `check_mta_sts` (~39 tokens)

Validate MTA-STS DNS and the hosted policy file for a domain.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `check_blacklist` (~39 tokens)

Check a domain's mail servers, or a direct IP, against DNS blacklists.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `check_email_security` (~45 tokens)

Full email-security check for a domain: SPF, DKIM, DMARC, blacklist, score, and issues.

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `analyze_raw_email` (~40 tokens)

Analyze a pasted raw MIME email source locally: headers, authentication verdicts, and hops.

Input parameters:

- `raw` (string, required): Raw MIME email source to analyze.

### `analyze_security_headers` (~42 tokens)

Scan a live site's HTTP security headers and report which are present or missing.

Input parameters:

- `url` (string, required): URL of the live site whose HTTP response headers to scan.

### `generate_security_headers` (~63 tokens)

Generate a best-practice HTTP security-header set locally from a recommended, strict, or report-only preset.

Input parameters:

- `format` (string): Output format for the generated header set.
- `preset` (string): Header preset to generate: recommended, strict, or report-only.

### `get_health` (~24 tokens)

Get the health of the intodns.ai API, cache, and runtime.

### `get_stats` (~22 tokens)

Get public scan and check counters for the intodns.ai service.

### `get_pdf_report_link` (~41 tokens)

Build the direct PDF report URL for a domain ({base}/api/pdf/{domain}).

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

### `get_badge_link` (~42 tokens)

Build the direct SVG badge URL for a domain ({base}/api/badge/{domain}).

Input parameters:

- `domain` (string, required): Domain name this tool operates on.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-dnsprobe/ghcr-io-cloudcorprecords-dnsprobe#diagnostics

## Score history

- 2026-11-05: 41
- 2026-11-04: 41
- 2026-11-03: 40
- 2026-11-02: 40

## Common questions

### What is the io.github.CloudCorpRecords/dnsprobe MCP server?

io.github.CloudCorpRecords/dnsprobe is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/dnsprobe. DNS and email-security diagnostics via the keyless intodns.ai API: scans, SPF, DMARC, headers. This page covers its container image (ghcr.io/cloudcorprecords/dnsprobe).

### Is the io.github.CloudCorpRecords/dnsprobe MCP server safe to use?

io.github.CloudCorpRecords/dnsprobe scores 41 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/dnsprobe MCP server expose?

io.github.CloudCorpRecords/dnsprobe exposes 21 tools: scan_domain, lookup_dns, validate_dnssec, check_dns_propagation, whois_lookup, and 16 more. Their descriptions and schemas cost roughly 908 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/dnsprobe MCP server still maintained?

io.github.CloudCorpRecords/dnsprobe is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/dnsprobe MCP server under?

io.github.CloudCorpRecords/dnsprobe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/dnsprobe
- Repository: https://github.com/CloudCorpRecords/dnsprobe
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-dnsprobe/ghcr-io-cloudcorprecords-dnsprobe.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-dnsprobe/ghcr-io-cloudcorprecords-dnsprobe.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-dnsprobe/ghcr-io-cloudcorprecords-dnsprobe