ai.sendraven/mcp
REMOTE · MCP.SENDRAVEN.AI · 2 COMPONENTS · SCANNED SEP 20
Email infrastructure for AI agents: send, read replies as threads, campaigns, per-key limits.
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 Security89
- 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
- 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
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11278 tokens (~205/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability check failed: schema churn in the 18 days we've observed: 1 tool removals, 1 breaking changes, 0 auth/transport breaks, 11 additions. See how to fix → Fail
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% 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 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_email" implies "send" 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 55 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 ai.sendraven/mcp server?
ai.sendraven/mcp is a hosted endpoint at https://mcp.sendraven.ai/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.sendraven.ai
claude mcp add --transport http ai-sendraven-mcp 'https://mcp.sendraven.ai/mcp'
{
"mcpServers": {
"ai-sendraven-mcp": {
"url": "https://mcp.sendraven.ai/mcp"
}
}
} {
"servers": {
"ai-sendraven-mcp": {
"type": "http",
"url": "https://mcp.sendraven.ai/mcp"
}
}
} [mcp_servers.ai-sendraven-mcp] url = "https://mcp.sendraven.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-sendraven-mcp": {
"type": "remote",
"url": "https://mcp.sendraven.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-sendraven-mcp --url 'https://mcp.sendraven.ai/mcp' --transport streamable-http
mcp_servers:
ai-sendraven-mcp:
url: "https://mcp.sendraven.ai/mcp" {
"McpServers": {
"ai-sendraven-mcp": {
"Transport": "http",
"Url": "https://mcp.sendraven.ai/mcp"
}
}
} assistant mcp add ai-sendraven-mcp -t streamable-http -u 'https://mcp.sendraven.ai/mcp'
{
"mcpServers": {
"ai-sendraven-mcp": {
"type": "http",
"url": "https://mcp.sendraven.ai/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.
- 19 Sept 26 +1
- Tool “send_email” rewrote its description, which is the text the model reads security
- Tool “get_usage” rewrote its description, which is the text the model reads security
- Tool “decide_approval” rewrote its description, which is the text the model reads security
- Tool “send_template_email” rewrote its description, which is the text the model reads security
- Server version: 0.4.14 → 0.4.15 functional
- 17 Sept 26 +1
- Server version: 0.4.13 → 0.4.14 functional
- Server version: 0.4.12 → 0.4.13 functional
- “reply_to_message” added an optional parameter “scheduled_at” cosmetic
- “update_contact” added an optional parameter “last_active_at” cosmetic
- “add_contact” added an optional parameter “last_active_at” cosmetic
- 15 Sept 26 −1
- Stability: 0.40 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “list_api_keys” was removed ▼ security
- Tool “tag_contact” rewrote its description, which is the text the model reads security
- Tool “list_scheduled_emails” rewrote its description, which is the text the model reads security
- Tool “list_sending_domains” rewrote its description, which is the text the model reads security
- Tool “list_suppressions” rewrote its description, which is the text the model reads security
- Tool “list_templates” rewrote its description, which is the text the model reads security
- Tool “list_threads” rewrote its description, which is the text the model reads security
- Tool “list_webhook_deliveries” rewrote its description, which is the text the model reads security
- Tool “pick_broadcast_winner” rewrote its description, which is the text the model reads security
- Tool “remove_suppression” rewrote its description, which is the text the model reads security
- Tool “render_template” rewrote its description, which is the text the model reads security
- Tool “reply_to_message” rewrote its description, which is the text the model reads security
- Tool “resume_broadcast” rewrote its description, which is the text the model reads security
- Tool “send_broadcast” rewrote its description, which is the text the model reads security
- Tool “send_email” rewrote its description, which is the text the model reads security
- Tool “send_template_email” rewrote its description, which is the text the model reads security
- Tool “set_email_preferences” rewrote its description, which is the text the model reads security
- Tool “suppress_many” rewrote its description, which is the text the model reads security
- Tool “update_automation” rewrote its description, which is the text the model reads security
- Tool “update_contact” rewrote its description, which is the text the model reads security
- Tool “add_sending_domain” rewrote its description, which is the text the model reads security
- Tool “add_suppression” rewrote its description, which is the text the model reads security
- Tool “cancel_scheduled_email” rewrote its description, which is the text the model reads security
- Tool “create_automation” rewrote its description, which is the text the model reads security
- Tool “create_broadcast” rewrote its description, which is the text the model reads security
- Tool “decide_approval” rewrote its description, which is the text the model reads security
- Tool “emit_event” rewrote its description, which is the text the model reads security
- Tool “enroll_in_automation” rewrote its description, which is the text the model reads security
- Tool “find_contact” rewrote its description, which is the text the model reads security
- Tool “get_broadcast” rewrote its description, which is the text the model reads security
- Tool “get_usage” rewrote its description, which is the text the model reads security
- Tool “list_audiences” rewrote its description, which is the text the model reads security
- Tool “list_automations” rewrote its description, which is the text the model reads security
- Tool “list_broadcast_recipients” rewrote its description, which is the text the model reads security
- Tool “list_broadcasts” rewrote its description, which is the text the model reads security
- Tool “list_emails” rewrote its description, which is the text the model reads security
- Tool “list_pending_approvals” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “find_contact” changed the type of “limit”: number → integer ▼ functional
- Tool coverage: 46% → 72% ▲ functional
- Tool coverage: 46% → 71% ▲ functional
- Tool coverage: 46% → 53% ▲ functional
- Tool coverage: 46% → 51% ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.1.0 → 0.4.12 functional
- New tool “list_automation_enrollments” functional
- New tool “set_automation_status” functional
- New tool “get_automation” functional
- New tool “create_automation” functional
- New tool “update_automation” functional
- “list_scheduled_emails” added an optional parameter “cursor” cosmetic
- “list_suppressions” added an optional parameter “cursor” cosmetic
- “list_suppressions” added an optional parameter “email” cosmetic
- “list_threads” added an optional parameter “cursor” cosmetic
- “reply_to_message” added an optional parameter “idempotency_key” cosmetic
- “send_email” added an optional parameter “bcc” cosmetic
- “send_email” added an optional parameter “cc” cosmetic
- “send_email” added an optional parameter “idempotency_key” cosmetic
- “update_automation” added an optional parameter “reenrollment” cosmetic
- “update_contact” added an optional parameter “unsubscribed” cosmetic
- “send_template_email” added an optional parameter “idempotency_key” cosmetic
- “create_automation” added an optional parameter “reenrollment” cosmetic
- “find_contact” added an optional parameter “tag” cosmetic
- “list_audiences” added an optional parameter “cursor” cosmetic
- “list_audiences” added an optional parameter “limit” cosmetic
- “list_automations” added an optional parameter “cursor” cosmetic
- “list_automations” added an optional parameter “limit” cosmetic
- “list_broadcast_recipients” added an optional parameter “cursor” cosmetic
- “list_broadcasts” added an optional parameter “cursor” cosmetic
- “list_broadcasts” added an optional parameter “limit” cosmetic
- “list_emails” added an optional parameter “cursor” cosmetic
- “list_scheduled_emails” reworded the description of “limit” cosmetic
- “list_suppressions” reworded the description of “limit” cosmetic
- “list_threads” reworded the description of “awaiting_reply” cosmetic
- “list_threads” reworded the description of “limit” cosmetic
- “list_webhook_deliveries” reworded the description of “limit” cosmetic
- “remove_suppression” reworded the description of “scope” cosmetic
- “reply_to_message” reworded the description of “reply_to_message_id” cosmetic
- “send_broadcast” reworded the description of “scheduled_at” cosmetic
- “suppress_many” reworded the description of “reason” cosmetic
- “suppress_many” reworded the description of “scope” cosmetic
- “update_automation” reworded the description of “topic_key” cosmetic
- “add_sending_domain” reworded the description of “domain” cosmetic
- “add_suppression” reworded the description of “reason” cosmetic
- “add_suppression” reworded the description of “scope” cosmetic
- “create_automation” reworded the description of “topic_key” cosmetic
- “create_broadcast” reworded the description of “topic_key” cosmetic
- “decide_approval” reworded the description of “id” cosmetic
- “find_contact” reworded the description of “cursor” cosmetic
- “find_contact” reworded the description of “limit” cosmetic
- “find_contact” reworded the description of “q” cosmetic
- “list_broadcast_recipients” reworded the description of “id” cosmetic
- “list_broadcast_recipients” reworded the description of “limit” cosmetic
- “list_emails” reworded the description of “limit” cosmetic
- “list_emails” reworded the description of “status” cosmetic
- “send_template_email” reworded the description of “to” cosmetic
- “send_email” reworded the description of “to” cosmetic
- “reply_to_message” reworded the description of “to” cosmetic
- 14 Sept 26 0
- Tool “tag_contact” rewrote its description, which is the text the model reads security
- Tool “add_contact” rewrote its description, which is the text the model reads security
- Tool “enroll_in_automation” rewrote its description, which is the text the model reads security
- Tool “import_contacts” rewrote its description, which is the text the model reads security
- Tool “get_thread” rewrote its description, which is the text the model reads security
- “import_contacts” added an optional parameter “trigger_automations” cosmetic
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 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.
- 8 Sept 26 0
- Tool “verify_sending_domain” rewrote its description, which is the text the model reads security
- Tool “list_sending_domains” rewrote its description, which is the text the model reads security
- New tool “mark_thread_handled” functional
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 20 Sept 2026 · Probed https://mcp.sendraven.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.sendraven.ai | CN=YR1,O=Let's Encrypt,C=US | 31 Aug 2026 | 29 Nov 2026 | RSA 2048 | SHA256-RSA | 52d5abb3d816d721f8a5b5a5b022832c13d |
| SANs: mcp.sendraven.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.sendraven.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| sendraven.ai. | 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.sendraven.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.sendraven.ai/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.sendraven.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.sendraven.ai |
| Authorisation server | https://api.sendraven.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sendraven.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sendraven.ai/mcp | HTTPS enforced | 301 | https://mcp.sendraven.ai/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 →
suppress_many ~148
Stop sending to many addresses at once — the path for importing another provider's unsubscribe list before a first campaign. Without it, everyone who already opted out there gets mailed again here. Note the defaults differ from add_suppression: scope 'marketing' and reason 'list_hygiene'. Pass reason 'unsubscribe' for a list of opt-outs; that also cancels their queued scheduled sends and ends their automation enrolments. Addresses are de-duplicated; the response counts suppressed and duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | – |
| reason | string | – | Defaults to list_hygiene. unsubscribe also cancels queued mail and ends enrolments |
| scope | string | – | Defaults to marketing |
No output schema declared.
No examples provided.
tag_contact ~244
Add or remove tags on a contact. Tags are flat labels — vip, beta, churned — as opposed to custom properties, which are declared fields with a value. They are lower-cased and spaces become hyphens, so VIP and vip are the same tag. Tagging reaches the person across every audience they are on. Call list_tags first to see what the workspace already uses, rather than inventing a synonym for an existing tag. Adding a tag an automation exits on (e.g. customer), or removing one it requires (e.g. trial), ends the person's enrolment in it at once. Returns the contact, as get_contact does, with its tags after the change. To see which enrolments a tag change ended, call list_automation_enrollments with status 'canceled' and read each row's cancel_reason (exit_tag or required_tag_missing).
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | – | – |
| contact_id | string | yes | The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. Call find_contact with the address first if that is all you have. |
| remove | array | – | – |
No output schema declared.
No examples provided.
update_automation ~508
Change the rules that take someone out of a sequence (topic_key, exit_tags, required_tags, exit_on_reply), its reply_to, or its reenrollment. Steps and the trigger are fixed once created. A reenrollment change applies from the next enrolment; nobody already enrolled is touched. Fields left out keep their value; a null topic_key or reply_to, or an empty tag list, clears it. People already enrolled see the change from their next step, so a mistaken edit can be put back before it has ended anyone's sequence. Clear reply_to to have replies threaded in SendRaven again and stop the drip on their own. A topic_key that names no existing topic is refused with 422 unknown_topic, any field other than these is refused with 422 invalid_request, and an unknown automation_id answers 404 not_found.
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | The automation's id from list_automations (a UUID), not its name or slug |
| exit_on_reply | boolean | – | End the enrolment when the person replies. Defaults to true; turn off for dunning |
| exit_tags | array | – | Contact tags that end the sequence: nobody carrying one is enrolled, and adding one ends the enrolment. Tag someone 'customer' when they upgrade and a trial sequence stops |
| reenrollment | string | – | after_completion (the default): someone whose enrolment completed or was cancelled can be enrolled again. never: each person goes through it once, and a later enrolment answers enrolled: false with r… |
| reply_to | string|null | – | Where replies go instead of from, e.g. the founder's own inbox. Only set it when asked: SendRaven receives mail for its own domains only, so with a reply-to elsewhere a reply cannot stop the sequence… |
| required_tags | array | – | Tags a person must keep: only people carrying all of them are enrolled, and removing one ends the enrolment. Someone with no contact record has no tags, so is never enrolled |
| topic_key | – | – | Send every step under this topic (see list_topics). Its unsubscribe link then opts the person out of this kind of mail only, and opting out ends the sequence. Must be an existing topic's key; an unkn… |
No output schema declared.
No examples provided.
update_contact ~211
Update a contact. Attributes are merged, so sending one field does not clear the rest. unsubscribed: true is a real opt-out: it suppresses the address for marketing, cancels their pending sends and ends their automation enrolments. unsubscribed: false lifts a marketing unsubscribe — only do it when the person asked. Resubscribing someone who hard bounced or complained is refused with 409 invalid_state before anything in the request is written.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | – |
| first_name | string | – | – |
| id | string | yes | The contact's id (a UUID) from find_contact, add_contact or get_contact — not the email address. Call find_contact with the address first if that is all you have. |
| last_active_at | – | – | ISO 8601 time of their last activity in your product. Only moves forward; null clears it. |
| last_name | string | – | – |
| unsubscribed | boolean | – | true to opt them out of marketing, false to undo an unsubscribe |
No output schema declared.
No examples provided.
verify_sending_domain ~71
Re-check a domain's DNS records now instead of waiting for the background monitor. Also restarts bounce-path (mail_from) verification when SES gave up before the MX record existed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The sending domain's id from list_sending_domains (a UUID), not the domain name |
No output schema declared.
No examples provided.
What is the ai.sendraven/mcp server?
ai.sendraven/mcp is listed in the public MCP registry as ai.sendraven/mcp. Email infrastructure for AI agents: send, read replies as threads, campaigns, per-key limits. This page covers its hosted endpoint (https://mcp.sendraven.ai/mcp).
Is the ai.sendraven/mcp server safe to use?
ai.sendraven/mcp scores 81 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.sendraven/mcp server expose?
ai.sendraven/mcp exposes 55 tools: send_email, list_emails, get_email, cancel_scheduled_email, list_sending_domains, and 50 more. Their descriptions and schemas cost roughly 11,278 tokens of context every time the server is loaded.
Does the ai.sendraven/mcp server require authentication?
Yes. ai.sendraven/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 ai.sendraven/mcp server still maintained?
ai.sendraven/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.