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

Email authentication checks: DMARC, SPF and DKIM, SPF building, bounce and report analysis.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/canarymail`
- 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-21.

- **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 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 801 tokens (~200/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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/canarymail MCP server?

io.github.CloudCorpRecords/canarymail runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/canarymail:0.1.0 mcp. 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-canarymail -- docker run --rm -i ghcr.io/cloudcorprecords/canarymail:0.1.0 mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

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

## 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-21 (score 43, +1)

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

### 2026-11-19 (score 42, +1)

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

### 2026-11-17 (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-15 (score 40)

First indexed and scored.

## MCP tools (4)

### `check_domain` (~166 tokens)

Check a domain's email authentication

Use this when someone asks whether a domain's email authentication is set up correctly, why mail from a domain fails DMARC, SPF or DKIM, or which DNS records to publish for it. Reads the domain's live DMARC, SPF and DKIM records and returns what is wrong with each, plus the records to add or change. Pass a DKIM selector when you know it. Without one, common selectors are tried. Takes a domain name only, not a mailbox address or an IP address.

Input parameters:

- `domain` (string, required): The domain to check, such as example.com. A URL is cut down to its host.
- `selector` (string): The DKIM selector, the s= value in a DKIM-Signature header. Leave it out to try common ones.

### `build_spf` (~305 tokens)

Build an SPF record

Use this when someone lists the services that send their email and wants the SPF record to publish, or wants a sender added to the SPF record they already have. Takes provider names such as Google Workspace or Mailchimp, include terms such as include:spf.example.com, or IP addresses, and returns one merged record with its count of DNS lookups against the limit of ten. Pass the domain when you know it, so the result includes the senders already in its published record.

Input parameters:

- `all` (string): How the record ends. A new record ends in ~all unless you pass -all. A record the domain already publishes keeps its own ending unless you pass one.
- `domain` (string): The domain the record is for. When given, the SPF record it publishes today is read and the senders are added to it, so nothing already in it is lost.
- `ip4` (array): IPv4 addresses or ranges that send this domain's mail directly, such as 192.0.2.10 or 192.0.2.0/24.
- `ip6` (array): IPv6 addresses or ranges that send this domain's mail directly, such as 2001:db8::1 or 2001:db8::/32.
- `senders` (array, required): The platforms that send this domain's mail: provider names such as Google Workspace or Mailchimp, or include terms such as include:spf.example.com.

### `explain_bounce` (~129 tokens)

Explain a bounce or SMTP error

Use this when someone pastes a bounce message, an SMTP reply such as 550 5.7.26, or an Authentication-Results header and asks what it means or how to fix it. Returns what the receiving server refused, what to change, when it clears, and the page that explains it. Works from the pasted text alone and reads no DNS records.

Input parameters:

- `text` (string, required): The bounce message, the SMTP reply or the Authentication-Results line, as pasted. When the bounce runs past 4,000 characters, pass the lines with the error code and the reason.

### `analyze_report` (~201 tokens)

Read a DMARC aggregate report

Use this when someone has a DMARC aggregate report and wants to know which senders passed and which failed. The report is the XML, .gz or .zip file that receivers such as Google and Yahoo email to the address in a domain's rua tag. In ChatGPT, pass the uploaded file. Elsewhere, pass the report XML as text. Returns totals per report and each sending IP address with its SPF, DKIM and DMARC results. The result gives a next step for the report's domain and a link to a live check of that domain's DNS records. Nothing from the report is stored.

Input parameters:

- `file` (object): The report file the user uploaded in ChatGPT: the .xml, .xml.gz or .zip a mailbox provider emailed them.
- `report_xml` (string): The report XML as text, from <feedback> to </feedback>. Use this when there is no uploaded file, or when the user pasted the XML.

## Diagnostics

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

## Score history

- 2026-11-21: 43
- 2026-11-20: 42
- 2026-11-19: 42
- 2026-11-18: 41
- 2026-11-17: 41
- 2026-11-16: 40
- 2026-11-15: 40

## Common questions

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

io.github.CloudCorpRecords/canarymail is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/canarymail. Email authentication checks: DMARC, SPF and DKIM, SPF building, bounce and report analysis. This page covers its container image (ghcr.io/cloudcorprecords/canarymail).

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

io.github.CloudCorpRecords/canarymail scores 43 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/canarymail MCP server expose?

io.github.CloudCorpRecords/canarymail exposes 4 tools: check_domain, build_spf, explain_bounce, analyze_report. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/canarymail is still listed as active in the MCP registry. We last reached this channel on 21 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/canarymail MCP server under?

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

### What did VerifyMCP test on the io.github.CloudCorpRecords/canarymail MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/canarymail, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/canarymail: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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