com.rattlesnakesbymail/rattlesnakesbymail
REMOTE · RATTLESNAKESBYMAIL.COM · SCANNED OCT 5
Dated, sourced claims about AI crawlers and agents, offered as MCP tools.
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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
- Tool/resource definitions use about 582 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 com.rattlesnakesbymail/rattlesnakesbymail MCP server?
com.rattlesnakesbymail/rattlesnakesbymail is a hosted endpoint at https://rattlesnakesbymail.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 · rattlesnakesbymail.com
claude mcp add --transport http com-rattlesnakesbymail-rattlesnakesbymail 'https://rattlesnakesbymail.com/mcp'
{
"mcpServers": {
"com-rattlesnakesbymail-rattlesnakesbymail": {
"url": "https://rattlesnakesbymail.com/mcp"
}
}
} {
"servers": {
"com-rattlesnakesbymail-rattlesnakesbymail": {
"type": "http",
"url": "https://rattlesnakesbymail.com/mcp"
}
}
} [mcp_servers.com-rattlesnakesbymail-rattlesnakesbymail] url = "https://rattlesnakesbymail.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rattlesnakesbymail-rattlesnakesbymail": {
"type": "remote",
"url": "https://rattlesnakesbymail.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-rattlesnakesbymail-rattlesnakesbymail --url 'https://rattlesnakesbymail.com/mcp' --transport streamable-http
mcp_servers:
com-rattlesnakesbymail-rattlesnakesbymail:
url: "https://rattlesnakesbymail.com/mcp" {
"McpServers": {
"com-rattlesnakesbymail-rattlesnakesbymail": {
"Transport": "http",
"Url": "https://rattlesnakesbymail.com/mcp"
}
}
} assistant mcp add com-rattlesnakesbymail-rattlesnakesbymail -t streamable-http -u 'https://rattlesnakesbymail.com/mcp'
{
"mcpServers": {
"com-rattlesnakesbymail-rattlesnakesbymail": {
"type": "http",
"url": "https://rattlesnakesbymail.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.
- 5 Oct 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.
- 3 Oct 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.
- 1 Oct 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.
- 29 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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 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.
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 5 Oct 2026 · Probed https://rattlesnakesbymail.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rattlesnakesbymail.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1d72054d6b774d45134c66165b4a9887 |
| SANs: rattlesnakesbymail.com, w2yioj83niwpvj1e.rattlesnakesbymail.com, *.w2yioj83niwpvj1e.rattlesnakesbymail.com | ||||||
| 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 rattlesnakesbymail.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rattlesnakesbymail.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rattlesnakesbymail.com/mcp | Verified | 200 | |
| http (plaintext) | http://rattlesnakesbymail.com/mcp | HTTPS enforced | 301 | https://rattlesnakesbymail.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 →
ask Ask A Question ~100
Match a free-text question against the claims published on Rattlesnakes By Mail, and return the matching claims, or no match when no published claim covers the question. Every question sent to ask is recorded, and a recorded question may be published on the public questions page at Rattlesnakes By Mail. Do not send private or identifying text to ask.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | A free-text question about crawlers, agents, or claims. |
No output schema declared.
No examples provided.
identify_user_agent Identify A User Agent ~74
Match an unrecognized raw User-Agent header against the crawlers documented on Rattlesnakes By Mail, and return the matched crawler plus instructions for verifying the request. Use identify_user_agent when the crawler behind the User-Agent header is not yet known.
| Name | Type | Req | Description |
|---|---|---|---|
| user_agent | string | yes | A raw User-Agent header string. |
No output schema declared.
No examples provided.
list_changes List Changes ~115
List recorded changes to claims on Rattlesnakes By Mail, newest first, with the change date and the affected crawler. Filter by date with since, by crawler with entity, or by both. Use list_changes to detect crawler policy updates published after a given date.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | An entity slug to filter changes to one crawler. |
| limit | integer | – | Maximum rows to return, up to 200. |
| since | string | – | An ISO date; only changes on or after this date are returned. |
No output schema declared.
No examples provided.
lookup_crawler Look Up A Crawler ~94
Look up a documented crawler on Rattlesnakes By Mail by name, slug, or user-agent string, and return identity fields, current claims, publication dates, and evidence URLs. Use lookup_crawler when the crawler is already named, or when the user agent is already known to belong to a documented crawler.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_ua | string | yes | A crawler name, slug, or full user-agent string. |
No output schema declared.
No examples provided.
submit_note Submit A Note ~144
Submit a correction or note about a claim, an entity, or a question on Rattlesnakes By Mail. Requires a client token issued out of band by the publisher. Every note is stored as pending, and an editor reviews every pending note before publication.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The note text, up to 2000 characters. |
| target_id | string | yes | The id or slug of the claim or entity, or the id or hash of the question, the note is about. |
| target_type | string | yes | The kind of record the note is about. |
| token | string | yes | A client token issued by Rattlesnakes By Mail. |
No output schema declared.
No examples provided.
What is the com.rattlesnakesbymail/rattlesnakesbymail MCP server?
com.rattlesnakesbymail/rattlesnakesbymail is an MCP server listed in the public MCP registry as com.rattlesnakesbymail/rattlesnakesbymail. Dated, sourced claims about AI crawlers and agents, offered as MCP tools. This page covers its hosted endpoint (https://rattlesnakesbymail.com/mcp).
Is the com.rattlesnakesbymail/rattlesnakesbymail MCP server safe to use?
com.rattlesnakesbymail/rattlesnakesbymail scores 78 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 com.rattlesnakesbymail/rattlesnakesbymail MCP server expose?
com.rattlesnakesbymail/rattlesnakesbymail exposes 5 tools: lookup_crawler, identify_user_agent, list_changes, ask, submit_note. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
Does the com.rattlesnakesbymail/rattlesnakesbymail MCP server require authentication?
No. We connected to com.rattlesnakesbymail/rattlesnakesbymail without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.rattlesnakesbymail/rattlesnakesbymail MCP server still maintained?
com.rattlesnakesbymail/rattlesnakesbymail is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.