io.github.dmarc-examiner/mcp
REMOTE · MCP.DMARC-EXAMINER.COM · 2 COMPONENTS · SCANNED SEP 27
Read your own DMARC aggregate and forensic reports: sources, alignment, alerts, CSV export.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 919 tokens (~43/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_domain" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.dmarc-examiner/mcp server?
io.github.dmarc-examiner/mcp is a hosted endpoint at https://mcp.dmarc-examiner.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.dmarc-examiner.com
claude mcp add --transport http dmarc-examiner-mcp 'https://mcp.dmarc-examiner.com/mcp'
{
"mcpServers": {
"dmarc-examiner-mcp": {
"url": "https://mcp.dmarc-examiner.com/mcp"
}
}
} {
"servers": {
"dmarc-examiner-mcp": {
"type": "http",
"url": "https://mcp.dmarc-examiner.com/mcp"
}
}
} [mcp_servers.dmarc-examiner-mcp] url = "https://mcp.dmarc-examiner.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dmarc-examiner-mcp": {
"type": "remote",
"url": "https://mcp.dmarc-examiner.com/mcp",
"enabled": true
}
}
} openclaw mcp add dmarc-examiner-mcp --url 'https://mcp.dmarc-examiner.com/mcp' --transport streamable-http
mcp_servers:
dmarc-examiner-mcp:
url: "https://mcp.dmarc-examiner.com/mcp" {
"McpServers": {
"dmarc-examiner-mcp": {
"Transport": "http",
"Url": "https://mcp.dmarc-examiner.com/mcp"
}
}
} assistant mcp add dmarc-examiner-mcp -t streamable-http -u 'https://mcp.dmarc-examiner.com/mcp'
{
"mcpServers": {
"dmarc-examiner-mcp": {
"type": "http",
"url": "https://mcp.dmarc-examiner.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +65
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Stability: unverified → 0.97 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Sept 26 −64
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.90 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://mcp.dmarc-examiner.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dmarc-examiner.com | CN=YE2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6ef8b508a33e4561dea5eac117752c2a716 |
| SANs: api.dmarc-examiner.com, app.dmarc-examiner.com, dmarc-examiner.com, mcp.dmarc-examiner.com, ws.dmarc-examiner.com, www.dmarc-examiner.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.dmarc-examiner.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dmarc-examiner.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.dmarc-examiner.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.dmarc-examiner.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Protected resource metadata
| Document | https://mcp.dmarc-examiner.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.dmarc-examiner.com |
| Authorisation server | https://mcp.dmarc-examiner.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.dmarc-examiner.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.dmarc-examiner.com/mcp | HTTPS enforced | 301 | https://mcp.dmarc-examiner.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_dmarc ~63
Inspect the public DMARC record at _dmarc.<domain>. The domain does not need to belong to your organization. Returns parsed policy and rua/ruf addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to inspect — does not need to belong to your organization. |
No output schema declared.
No examples provided.
create_domain ~68
Add a new domain to the organization. Response includes the reporting_email and dmarc_record values to publish in DNS. May return 402 if the plan domain limit has been reached.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Domain name to monitor (e.g. "example.com"). Stored lowercased. |
No output schema declared.
No examples provided.
create_webhook ~59
Create a new webhook endpoint. URL must start with https://. Returns 422 if the organization has reached its webhook limit.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Human-readable label |
| url | string | yes | HTTPS URL events will be POSTed to |
No output schema declared.
No examples provided.
delete_domain ~33
Remove a domain from monitoring. Soft-deletes; historical reports remain accessible.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | Domain UUID |
No output schema declared.
No examples provided.
delete_webhook ~26
Delete a webhook endpoint permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | Webhook UUID |
No output schema declared.
No examples provided.
dismiss_alert ~22
Dismiss a specific alert
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | – |
No output schema declared.
No examples provided.
export_report_csv ~25
Export a DMARC report as CSV
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_domain ~25
Get details of a specific domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | Domain UUID |
No output schema declared.
No examples provided.
get_forensic_report ~44
Get the full detail of a forensic (RUF) report by UUID, including the raw failed message envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | Forensic report UUID |
No output schema declared.
No examples provided.
get_forensic_reports_statistics ~36
Aggregated forensic-report counters grouped by auth failure type, delivery result, source IP (with geolocation) and reported domain.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_forensic_reports_summary ~28
Summary of forensic activity in the last 7 days — useful for daily digest views.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_report ~25
Get details of a specific DMARC report
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
get_report_statistics ~26
Get statistics for a specific DMARC report
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
list_alerts ~37
List alerts for your organization
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | – |
| per_page | number | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_domains ~31
List all monitored domains in your organization
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | – |
| per_page | number | – | – |
No output schema declared.
No examples provided.
list_forensic_reports ~113
List DMARC RUF (forensic) reports with optional filtering and pagination. Returns 403 if the plan does not include forensic reports (Pro plan and above).
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Inclusive lower bound on arrival_date (ISO 8601 / "YYYY-MM-DD HH:MM:SS") |
| date_to | string | – | Inclusive upper bound on arrival_date |
| domain_id | string | – | Filter by domain UUID |
| page | number | – | – |
| per_page | number | – | – |
No output schema declared.
No examples provided.
list_reports ~54
List DMARC reports for your organization
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| domain | string | – | – |
| page | number | – | – |
| per_page | number | – | – |
No output schema declared.
No examples provided.
list_webhooks ~34
List webhook endpoints configured for the organization. Returns 403 if the plan does not include advanced alerting (Pro and above).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
test_webhook ~51
Send a synchronous webhook.test event to verify connectivity. Returns the delivery status. Test events do NOT update last_triggered_at, last_status or failure_count.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | Webhook UUID |
No output schema declared.
No examples provided.
update_webhook ~76
Update a webhook. Any combination of url, name and is_active may be provided; URL must remain HTTPS.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Enable/disable delivery without losing config |
| name | string | – | New label |
| url | string | – | New HTTPS URL |
| webhook_id | string | yes | Webhook UUID |
No output schema declared.
No examples provided.
verify_domain ~43
Re-check a domain's DNS to confirm the DMARC record contains the organization's reporting email. Updates status to verified on success.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | Domain UUID |
No output schema declared.
No examples provided.
What is the io.github.dmarc-examiner/mcp server?
io.github.dmarc-examiner/mcp is listed in the public MCP registry as io.github.dmarc-examiner/mcp. Read your own DMARC aggregate and forensic reports: sources, alignment, alerts, CSV export. This page covers its hosted endpoint (https://mcp.dmarc-examiner.com/mcp).
Is the io.github.dmarc-examiner/mcp server safe to use?
io.github.dmarc-examiner/mcp scores 91 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.dmarc-examiner/mcp server expose?
io.github.dmarc-examiner/mcp exposes 21 tools: list_domains, get_domain, check_dmarc, create_domain, verify_domain, and 16 more. Their descriptions and schemas cost roughly 919 tokens of context every time the server is loaded.
Does the io.github.dmarc-examiner/mcp server require authentication?
Yes. io.github.dmarc-examiner/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.dmarc-examiner/mcp server still maintained?
io.github.dmarc-examiner/mcp is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.