io.github.CloudCorpRecords/mailsend
OCI · GHCR.IO/CLOUDCORPRECORDS/MAILSEND · 2 COMPONENTS
Send and manage email, domains, audiences, and API keys through the Resend API.
Available components
Last scanned (2 hours ago)
Scores higher than 42% of OCI servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 693 tokens (~46/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 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; "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 15 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 38
First indexed and scored.
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 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/mailsend@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
create_api_key ~80
Create a Resend API key, optionally scoped to one domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | – | The ID of the domain to scope this API key to. |
| name | string | yes | The name for the new API key. |
| permission | string | – | The permission level for the API key, such as 'full_access' or 'sending_access'. |
No output schema declared.
No examples provided.
create_audience ~29
Create an audience in Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name for the new audience. |
No output schema declared.
No examples provided.
create_contact ~91
Add a contact to an audience in Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | The ID of the audience to add the contact to. |
| string | yes | The contact's email address. | |
| first_name | string | – | The contact's first name. |
| last_name | string | – | The contact's last name. |
| unsubscribed | boolean | – | Whether the contact is unsubscribed from the audience. |
No output schema declared.
No examples provided.
create_domain ~54
Create a sending domain in Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The domain name to create as a sending domain. |
| region | string | – | The region to create the domain in, such as 'us-east-1'. |
No output schema declared.
No examples provided.
delete_api_key ~31
Delete a Resend API key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the API key to delete. |
No output schema declared.
No examples provided.
delete_domain ~31
Delete a sending domain from Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the sending domain to delete. |
No output schema declared.
No examples provided.
get_domain ~36
Get one sending domain by its ID, including its DNS records.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the sending domain to retrieve. |
No output schema declared.
No examples provided.
get_email ~31
Get one sent email by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the sent email to retrieve. |
No output schema declared.
No examples provided.
list_api_keys ~15
List Resend API keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_audiences ~16
List audiences in Resend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_contacts ~48
List contacts in an audience in Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | The ID of the audience whose contacts to list. |
| limit | integer | – | The maximum number of contacts to return. |
No output schema declared.
No examples provided.
list_domains ~15
List sending domains in Resend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_emails ~31
List emails sent through Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | The maximum number of sent emails to return. |
No output schema declared.
No examples provided.
send_email ~149
Send an email through Resend.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | array | – | Email addresses to blind-copy on the email (hidden recipients). |
| cc | array | – | Email addresses to copy on the email (carbon copy recipients). |
| from | string | yes | The sender email address, optionally in 'Name <email@example.com>' format. |
| html | string | – | The HTML body of the email. |
| reply_to | string | – | The email address replies to this email should be sent to. |
| subject | string | yes | The subject line of the email. |
| text | string | – | The plain-text body of the email. |
| to | array | yes | The recipient email addresses to send the email to. |
No output schema declared.
No examples provided.
verify_domain ~36
Start verification of a sending domain's DNS records.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the sending domain to start DNS verification for. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/mailsend MCP server?
io.github.CloudCorpRecords/mailsend runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/mailsend:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/mailsend
claude mcp add cloudcorprecords-mailsend -- docker run --rm -i ghcr.io/cloudcorprecords/mailsend:0.1.0
What is the io.github.CloudCorpRecords/mailsend MCP server?
io.github.CloudCorpRecords/mailsend is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/mailsend. Send and manage email, domains, audiences, and API keys through the Resend API. This page covers its container image (ghcr.io/cloudcorprecords/mailsend).
Is the io.github.CloudCorpRecords/mailsend MCP server safe to use?
io.github.CloudCorpRecords/mailsend scores 40 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.CloudCorpRecords/mailsend MCP server expose?
io.github.CloudCorpRecords/mailsend exposes 15 tools: send_email, list_emails, get_email, create_domain, list_domains, and 10 more. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/mailsend MCP server still maintained?
io.github.CloudCorpRecords/mailsend is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/mailsend MCP server under?
io.github.CloudCorpRecords/mailsend declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.