Emailchaser
REMOTE · APP.EMAILCHASER.COM · SCANNED SEP 29
Run cold email outbound from an AI agent: campaigns, leads, replies, sender accounts, autopilot.
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, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 15811 tokens (~156/item across 101 items; 101 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 observed for 17 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
- All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 102 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 Emailchaser MCP server?
Emailchaser is a hosted endpoint at https://app.emailchaser.com/api/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 · app.emailchaser.com
claude mcp add --transport http com-emailchaser-emailchaser 'https://app.emailchaser.com/api/mcp'
{
"mcpServers": {
"com-emailchaser-emailchaser": {
"url": "https://app.emailchaser.com/api/mcp"
}
}
} {
"servers": {
"com-emailchaser-emailchaser": {
"type": "http",
"url": "https://app.emailchaser.com/api/mcp"
}
}
} [mcp_servers.com-emailchaser-emailchaser] url = "https://app.emailchaser.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-emailchaser-emailchaser": {
"type": "remote",
"url": "https://app.emailchaser.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-emailchaser-emailchaser --url 'https://app.emailchaser.com/api/mcp' --transport streamable-http
mcp_servers:
com-emailchaser-emailchaser:
url: "https://app.emailchaser.com/api/mcp" {
"McpServers": {
"com-emailchaser-emailchaser": {
"Transport": "http",
"Url": "https://app.emailchaser.com/api/mcp"
}
}
} assistant mcp add com-emailchaser-emailchaser -t streamable-http -u 'https://app.emailchaser.com/api/mcp'
{
"mcpServers": {
"com-emailchaser-emailchaser": {
"type": "http",
"url": "https://app.emailchaser.com/api/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.
- 29 Sept 26 +1
- Tool “connect_sender_email” rewrote its description, which is the text the model reads security
- Tool “get_campaign” rewrote its description, which is the text the model reads security
- Tool “get_sender_email” rewrote its description, which is the text the model reads security
- Tool “get_sender_email_dns” rewrote its description, which is the text the model reads security
- Tool “get_sender_email_warmup” rewrote its description, which is the text the model reads security
- Tool “list_sender_emails” rewrote its description, which is the text the model reads security
- Tool “update_campaign” rewrote its description, which is the text the model reads security
- Tool “update_sender_email” rewrote its description, which is the text the model reads security
- Tool “update_sender_email_warmup” rewrote its description, which is the text the model reads security
- “create_campaign” added an optional parameter “minimumHealthScore” cosmetic
- “update_campaign” added an optional parameter “minimumHealthScore” cosmetic
- 28 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
- 26 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.
- 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 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.
- 23 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_dfy_order” rewrote its description, which is the text the model reads security
- “create_dfy_order” reworded the description of “domains” cosmetic
- “create_dfy_order” reworded the description of “mailboxes” cosmetic
- 22 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.
- 21 Sept 26 0
- New tool “cancel_email_verification_job” functional
- New tool “create_email_verification_job” functional
- New tool “get_email_verification_job” functional
- New tool “get_email_verification_rates” functional
- New tool “list_email_verification_jobs” functional
- New tool “list_email_verification_results” 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 29 Sept 2026 · Probed https://app.emailchaser.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.emailchaser.com | CN=YR1,O=Let's Encrypt,C=US | 23 Aug 2026 | 21 Nov 2026 | RSA 2048 | SHA256-RSA | 61021dee2caec2f53b2f84d9ba3be1caeeb |
| SANs: app.emailchaser.com | ||||||
| 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 app.emailchaser.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| emailchaser.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://app.emailchaser.com/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://app.emailchaser.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://app.emailchaser.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | No |
| Problem | metadata_http_error |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.emailchaser.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.emailchaser.com/api/mcp | HTTPS enforced | 308 | https://app.emailchaser.com/api/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 →
update_webhook Update webhook ~106
Updates a registered webhook's name, URL, event type or enabled state. Only the provided fields are changed. Disabling a webhook stops deliveries without deleting it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The numeric webhook ID (from list_webhooks) |
| isEnabled | boolean | – | Enable or disable deliveries without deleting the webhook |
| name | string | – | New display name |
| type | string | – | New event type |
| url | string | – | New HTTPS URL to receive events |
No output schema declared.
No examples provided.
What is the Emailchaser MCP server?
Emailchaser is an MCP server listed in the public MCP registry as com.emailchaser/emailchaser. Run cold email outbound from an AI agent: campaigns, leads, replies, sender accounts, autopilot. This page covers its hosted endpoint (https://app.emailchaser.com/api/mcp).
Is the Emailchaser MCP server safe to use?
Emailchaser scores 85 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 Emailchaser MCP server expose?
Emailchaser exposes 101 tools: confirm_connection, list_campaigns, create_campaign, get_campaign, update_campaign, and 96 more. Their descriptions and schemas cost roughly 15,569 tokens of context every time the server is loaded.
Does the Emailchaser MCP server require authentication?
Yes. Emailchaser 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 Emailchaser MCP server still maintained?
Emailchaser is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.