Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.friendlygeorge/resend-mcp-server

NPM · @SUPERNOVA123/RESEND-MCP-SERVER

MCP server for Resend — transactional email API for AI assistants...

0 this week 75 Trust /100

Last scanned (6 hours ago)

Scores higher than 50% of npm servers

Category Communication

Trust breakdown (7 categories)

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
Changelog

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.

Diagnostics

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 →

MCP tools · 10 exposed · ~541 tokens

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 →

Tool Tokens
create_api_key ~75

Create a new Resend API key (token is only returned once)

NameTypeReqDescription
domain_idstring–Restrict key to a specific domain (for sending_access)
namestringyesFriendly name for the key (e.g. 'production-server')
permissionstring–Permission scope (default: full_access)

No output schema declared.

No examples provided.

create_contact ~72

Add a new contact to a Resend audience

NameTypeReqDescription
audience_idstringyesAudience ID
emailstringyesContact email address
first_namestring–First name
last_namestring–Last name
unsubscribedboolean–Whether the contact is unsubscribed

No output schema declared.

No examples provided.

create_domain ~51

Create a new sending domain in Resend

NameTypeReqDescription
namestringyesDomain name (e.g. 'mail.acme.com')
regionstring–AWS region (default: us-east-1)

No output schema declared.

No examples provided.

get_email ~35

Get details about a specific email by ID

NameTypeReqDescription
email_idstringyesEmail 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

NameTypeReqDescription
audience_idstringyesAudience ID (e.g. from your Resend dashboard)
limitnumber–Max contacts to return (default 20)

No output schema declared.

No examples provided.

list_domains ~33

List all sending domains in your Resend account

NameTypeReqDescription
limitnumber–Max domains to return (default 20)

No output schema declared.

No examples provided.

list_emails ~32

List recent emails sent via Resend

NameTypeReqDescription
limitnumber–Max emails to return (default 20)

No output schema declared.

No examples provided.

send_email ~136

Send a transactional email via Resend

NameTypeReqDescription
bcc––Bcc address(es)
cc––Cc address(es)
fromstringyesSender address (e.g. 'Acme <noreply@acme.com>')
headersobject–Custom headers as key/value pairs
htmlstring–HTML body
reply_to––Reply-To address(es)
scheduled_atstring–ISO 8601 datetime to schedule the email
subjectstringyesEmail subject line
textstring–Plain text body
to–yesRecipient address(es)

No output schema declared.

No examples provided.

verify_domain ~34

Trigger verification of a domain's DNS records

NameTypeReqDescription
domain_idstringyesDomain ID (from create_domain or list_domains)

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add friendlygeorge-resend-mcp-server -- npx -y @supernova123/resend-mcp-server
Common questions

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.