io.github.friendlygeorge/resend-mcp-server
NPM · @SUPERNOVA123/RESEND-MCP-SERVER
MCP server for Resend — transactional email API for AI assistants...
Available components
Last scanned (10 hours ago)
Scores higher than 51% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency39
- 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
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 541 tokens (~54/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 1 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 10 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 Nov 2026 · Analysed npm/@supernova123/resend-mcp-server@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~75
Create a new Resend API key (token is only returned once)
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | – | Restrict key to a specific domain (for sending_access) |
| name | string | yes | Friendly name for the key (e.g. 'production-server') |
| permission | string | – | Permission scope (default: full_access) |
No output schema declared.
No examples provided.
create_contact ~72
Add a new contact to a Resend audience
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | Audience ID |
| string | yes | Contact email address | |
| first_name | string | – | First name |
| last_name | string | – | Last name |
| unsubscribed | boolean | – | Whether the contact is unsubscribed |
No output schema declared.
No examples provided.
create_domain ~51
Create a new sending domain in Resend
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Domain name (e.g. 'mail.acme.com') |
| region | string | – | AWS region (default: us-east-1) |
No output schema declared.
No examples provided.
get_email ~35
Get details about a specific email by ID
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Email ID (from send_email or list_emails) |
No output schema declared.
No examples provided.
list_api_keys ~23
List all API keys in your Resend account (tokens are hidden)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_contacts ~50
List contacts in a Resend audience
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | Audience ID (e.g. from your Resend dashboard) |
| limit | number | – | Max contacts to return (default 20) |
No output schema declared.
No examples provided.
list_domains ~33
List all sending domains in your Resend account
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max domains to return (default 20) |
No output schema declared.
No examples provided.
list_emails ~32
List recent emails sent via Resend
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max emails to return (default 20) |
No output schema declared.
No examples provided.
send_email ~136
Send a transactional email via Resend
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | – | – | Bcc address(es) |
| cc | – | – | Cc address(es) |
| from | string | yes | Sender address (e.g. 'Acme <noreply@acme.com>') |
| headers | object | – | Custom headers as key/value pairs |
| html | string | – | HTML body |
| reply_to | – | – | Reply-To address(es) |
| scheduled_at | string | – | ISO 8601 datetime to schedule the email |
| subject | string | yes | Email subject line |
| text | string | – | Plain text body |
| to | – | yes | Recipient address(es) |
No output schema declared.
No examples provided.
verify_domain ~34
Trigger verification of a domain's DNS records
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | Domain ID (from create_domain or list_domains) |
No output schema declared.
No examples provided.
How do I install the io.github.friendlygeorge/resend-mcp-server server?
io.github.friendlygeorge/resend-mcp-server runs locally as an npm package, launched with npx -y @supernova123/resend-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @supernova123/resend-mcp-server
claude mcp add friendlygeorge-resend-mcp-server -- npx -y @supernova123/resend-mcp-server
What is the io.github.friendlygeorge/resend-mcp-server server?
io.github.friendlygeorge/resend-mcp-server is listed in the public MCP registry as io.github.friendlygeorge/resend-mcp-server. MCP server for Resend, transactional email API for AI assistants... This page covers its npm package (@supernova123/resend-mcp-server).
Is the io.github.friendlygeorge/resend-mcp-server server safe to use?
io.github.friendlygeorge/resend-mcp-server scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.friendlygeorge/resend-mcp-server server expose?
io.github.friendlygeorge/resend-mcp-server exposes 10 tools: send_email, list_emails, get_email, create_domain, list_domains, and 5 more. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Is the io.github.friendlygeorge/resend-mcp-server server still maintained?
io.github.friendlygeorge/resend-mcp-server 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.friendlygeorge/resend-mcp-server server under?
io.github.friendlygeorge/resend-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.friendlygeorge/resend-mcp-server server?
VerifyMCP ran 15 checks on io.github.friendlygeorge/resend-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.friendlygeorge/resend-mcp-server: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.