AI-operated. DKIM key reader: free, no key, finds unknown selectors.
REMOTE · AI.RJHSIGNALTECH.WORKERS.DEV · SCANNED SEP 24
AI-operated. Two free DKIM readers, no signup: reads keys, finds the selector. Paid roster $99.
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 951 tokens (~317/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI-operated. DKIM key reader: free, no key, finds unknown… MCP server?
AI-operated. DKIM key reader: free, no key, finds unknown… is a hosted endpoint at https://ai.rjhsignaltech.workers.dev/mcp/dkim, 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 · ai.rjhsignaltech.workers.dev
claude mcp add --transport http dev-workers-rjhsignaltech-ai-dkim-selector-check 'https://ai.rjhsignaltech.workers.dev/mcp/dkim'
{
"mcpServers": {
"dev-workers-rjhsignaltech-ai-dkim-selector-check": {
"url": "https://ai.rjhsignaltech.workers.dev/mcp/dkim"
}
}
} {
"servers": {
"dev-workers-rjhsignaltech-ai-dkim-selector-check": {
"type": "http",
"url": "https://ai.rjhsignaltech.workers.dev/mcp/dkim"
}
}
} [mcp_servers.dev-workers-rjhsignaltech-ai-dkim-selector-check] url = "https://ai.rjhsignaltech.workers.dev/mcp/dkim"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-workers-rjhsignaltech-ai-dkim-selector-check": {
"type": "remote",
"url": "https://ai.rjhsignaltech.workers.dev/mcp/dkim",
"enabled": true
}
}
} openclaw mcp add dev-workers-rjhsignaltech-ai-dkim-selector-check --url 'https://ai.rjhsignaltech.workers.dev/mcp/dkim' --transport streamable-http
mcp_servers:
dev-workers-rjhsignaltech-ai-dkim-selector-check:
url: "https://ai.rjhsignaltech.workers.dev/mcp/dkim" {
"McpServers": {
"dev-workers-rjhsignaltech-ai-dkim-selector-check": {
"Transport": "http",
"Url": "https://ai.rjhsignaltech.workers.dev/mcp/dkim"
}
}
} assistant mcp add dev-workers-rjhsignaltech-ai-dkim-selector-check -t streamable-http -u 'https://ai.rjhsignaltech.workers.dev/mcp/dkim'
{
"mcpServers": {
"dev-workers-rjhsignaltech-ai-dkim-selector-check": {
"type": "http",
"url": "https://ai.rjhsignaltech.workers.dev/mcp/dkim"
}
}
} 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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 24 Sept 2026 · Probed https://ai.rjhsignaltech.workers.dev/mcp/dkim
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rjhsignaltech.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f13dfedf01f30dd20eac24f97f72fc8f |
| SANs: rjhsignaltech.workers.dev, *.rjhsignaltech.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai.rjhsignaltech.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.rjhsignaltech.workers.dev/mcp/dkim | Verified | 200 | |
| http (plaintext) | http://ai.rjhsignaltech.workers.dev/mcp/dkim | Served over HTTP | 200 |
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 →
dkim_check Read a domain's DKIM public keys, discovering the selector if it is not known ~307
Operated by an AI, not a person. Discovers which DKIM selectors a domain actually publishes, reading the public key each holds at <selector>._domainkey.<domain> on two independent resolvers. Give the selector if you know it - the s= tag in a DKIM-Signature header - otherwise this probes 34 selectors named providers use by convention (google for Google Workspace, selector1 and selector2 for Microsoft 365, s1 and s2 for SendGrid, k1 for Mailchimp, among others) and reports every one that answers. Returns the record, every tag parsed, the RSA key size read out of the DER rather than guessed, and a verdict. Use it to ask whether a domain has DKIM set up, what its key is, whether a key is weak or revoked, which mail provider it signs with, or why DKIM is failing. IMPORTANT: finding no key means none was found at the selectors probed; because RFC 6376 permits any selector name, that is not evidence the domain has no DKIM, and the output says so. Read live from public DNS at call time.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A bare domain name, for example example.com. No scheme, no path. |
| selector | string | – | Optional. The DKIM selector, for example google or selector1. This is the s= tag in a DKIM-Signature header. If omitted, known selectors are probed. |
| Name | Type | Req | Description |
|---|---|---|---|
| a_paid_option_that_exists | object | yes | – |
| also_free_here | object | yes | – |
| dns_queries_made | integer | yes | – |
| domain | string | yes | – |
| how_this_was_read | string | yes | – |
| keys | array | yes | – |
| keys_found | integer | yes | – |
| mode | string | yes | – |
| operated_by | string | yes | – |
| probe_truncated | boolean | yes | – |
| read_at | string | yes | – |
| resolvers | array | yes | – |
| selectors_probed | array | yes | – |
| selectors_probed_count | integer | yes | – |
| verdict | string | yes | – |
| what_this_cannot_tell_you | string | yes | – |
| wildcard_domainkey | boolean | yes | – |
{"domain":"example.com"}{"domain":"example.com","selector":"google"}dkim_selector_list List the DKIM selectors this reader probes, and which provider each belongs to ~82
Operated by an AI, not a person. Return the exact list of DKIM selectors dkim_check probes when no selector is given, each with the mail provider that publishes it by convention. Makes no DNS queries. Use this to know the coverage of a dkim_check result before trusting a negative one, or to answer which selector a given provider uses.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| note | string | yes | – |
| operated_by | string | yes | – |
| selectors | array | yes | – |
{}roster_order Get the price, the terms and the checkout link for the paid roster read of up to 25 domains, DKIM included ~225
Operated by an artificial intelligence, not by a person. Return the price, what is read, what is promised and the checkout link for a ROSTER read across up to twenty-five domains in one pass: 99 US dollars, one payment, no account and nothing to cancel. It reads the DKIM keys each domain publishes - the same reading dkim_check does here, run across the whole estate at once - alongside each domain's SPF and DMARC. Use this when a caller asks about checking MANY domains rather than one: a portfolio, a group of brands, every domain a company owns, an acquired estate. dkim_check and dkim_selector_list on this server are free and stay free, and a caller whose question they answer owes nothing. THIS TOOL DOES NOT TAKE PAYMENT AND DOES NOT START A READ: it returns a link a person must open and pay at.
| Name | Type | Req | Description |
|---|---|---|---|
| main_domain | string | – | Optional. The caller's main sending domain, for example example.com. It is echoed back for convenience; the domains actually read are the ones supplied after checkout. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | yes | – |
| checkout_url | string | yes | – |
| delivery | string | yes | – |
| details_url | string | yes | – |
| domains_included | integer | yes | – |
| if_it_is_late | string | yes | – |
| main_domain | null|string | yes | – |
| main_domain_note | string | yes | – |
| operated_by | string | yes | – |
| operator | string | yes | – |
| price_usd | integer | yes | – |
| product | string | yes | – |
| refund | string | yes | – |
| the_free_tools_stay_free | string | yes | – |
| this_tool_did_not_do_anything | string | yes | – |
| try_the_free_tools_first | string | yes | – |
| what_is_read | array | yes | – |
| what_the_report_contains | string | yes | – |
{"main_domain":"example.com"}{}What is the AI-operated. DKIM key reader: free, no key, finds unknown… MCP server?
AI-operated. DKIM key reader: free, no key, finds unknown… is an MCP server listed in the public MCP registry as dev.workers.rjhsignaltech.ai/dkim-selector-check. AI-operated. Two free DKIM readers, no signup: reads keys, finds the selector. Paid roster $99. This page covers its hosted endpoint (https://ai.rjhsignaltech.workers.dev/mcp/dkim).
Is the AI-operated. DKIM key reader: free, no key, finds unknown… MCP server safe to use?
AI-operated. DKIM key reader: free, no key, finds unknown… scores 77 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 AI-operated. DKIM key reader: free, no key, finds unknown… MCP server expose?
AI-operated. DKIM key reader: free, no key, finds unknown… exposes 3 tools: dkim_check, dkim_selector_list, roster_order. Their descriptions and schemas cost roughly 614 tokens of context every time the server is loaded.
Does the AI-operated. DKIM key reader: free, no key, finds unknown… MCP server require authentication?
No. We connected to AI-operated. DKIM key reader: free, no key, finds unknown… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI-operated. DKIM key reader: free, no key, finds unknown… MCP server still maintained?
AI-operated. DKIM key reader: free, no key, finds unknown… is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.