SendGrid Secure
PYPI · SENDGRID-MCP-SECURE · SCANNED OCT 4
Security-first SendGrid MCP server: dry-run default, recipient allowlists, rate caps, audit log.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- 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 35 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 619 tokens (~56/item across 11 items; 11 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 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 11 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 SendGrid Secure MCP server?
SendGrid Secure runs locally as a PyPI package, launched with uvx sendgrid-mcp-secure. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sendgrid-mcp-secure
claude mcp add choppaaahh-sendgrid-mcp-secure -- uvx sendgrid-mcp-secure
{
"mcpServers": {
"choppaaahh-sendgrid-mcp-secure": {
"command": "uvx",
"args": [
"sendgrid-mcp-secure"
]
}
}
} {
"servers": {
"choppaaahh-sendgrid-mcp-secure": {
"command": "uvx",
"args": [
"sendgrid-mcp-secure"
]
}
}
} codex mcp add choppaaahh-sendgrid-mcp-secure -- uvx sendgrid-mcp-secure
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"choppaaahh-sendgrid-mcp-secure": {
"type": "local",
"command": [
"uvx",
"sendgrid-mcp-secure"
],
"enabled": true
}
}
} openclaw mcp add choppaaahh-sendgrid-mcp-secure --command uvx --arg sendgrid-mcp-secure
mcp_servers:
choppaaahh-sendgrid-mcp-secure:
command: "uvx"
args: ["sendgrid-mcp-secure"] {
"McpServers": {
"choppaaahh-sendgrid-mcp-secure": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"sendgrid-mcp-secure"
]
}
}
} assistant mcp add choppaaahh-sendgrid-mcp-secure -t stdio -c uvx -a sendgrid-mcp-secure
{
"mcpServers": {
"choppaaahh-sendgrid-mcp-secure": {
"command": "uvx",
"args": [
"sendgrid-mcp-secure"
]
}
}
} 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 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- Provenance: unverified → fail ▼ security
- 29 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 28 Sept 26 +12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 4 Oct 2026 · Analysed pypi/sendgrid-mcp-secure@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 | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
add_suppression ~54
Add an address to a suppression list (default: global unsubscribes). Suppressing is the SAFE direction — it stops future sends to the address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| kind | string | – | – |
No output schema declared.
No examples provided.
check_suppression ~49
Check whether an address appears on any suppression list. Run this before drafting mail to someone — sending to suppressed addresses hurts deliverability and may violate consent.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – |
No output schema declared.
No examples provided.
get_domain_auth ~29
List authenticated sending domains and their DNS validity — the first thing to check when deliverability drops.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_email_stats ~68
Global email stats (requests/delivered/opens/clicks/bounces/spam) from start_date (YYYY-MM-DD). aggregated_by: day|week|month.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregated_by | string | – | – |
| end_date | string | – | – |
| start_date | string | yes | – |
No output schema declared.
No examples provided.
get_template ~28
Fetch one template with its versions (subject + content preview).
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | – |
No output schema declared.
No examples provided.
list_suppressions ~45
List a suppression list: unsubscribes|bounces|blocks|spam_reports|invalid_emails.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_templates ~17
List transactional email templates (dynamic + legacy).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_email ~137
Validate and render an email WITHOUT sending it. Returns the exact payload that would go to SendGrid plus a single-use confirm_token (valid 10 minutes). Sending requires passing that token to send_email — there is no direct-send path. BCC is not accepted by design.
| Name | Type | Req | Description |
|---|---|---|---|
| body_html | string | – | – |
| body_text | string | – | – |
| cc | – | – | – |
| from_email | string | yes | – |
| from_name | string | – | – |
| reply_to | string | – | – |
| subject | string | – | – |
| template_data | – | – | – |
| template_id | string | – | – |
| to | array | yes | – |
No output schema declared.
No examples provided.
remove_suppression ~80
Remove an address from a suppression list. DANGEROUS direction — it re-enables sending to someone who bounced or unsubscribed, which can be a compliance violation. Requires confirm=true, is rate-limited, and audited.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| string | yes | – | |
| kind | string | yes | – |
No output schema declared.
No examples provided.
send_email ~71
Send the email previously rendered by preview_email. Accepts ONLY a confirm token — the payload cannot be altered between preview and send. Tokens are single-use and expire after 10 minutes. In dry-run mode (the default) this simulates and audits but sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | yes | – |
No output schema declared.
No examples provided.
server_status ~41
This server's security posture: mode, rate-limit remaining, allowlist, caps, audit-log path, and whether an API key is present (never the key).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the SendGrid Secure MCP server?
SendGrid Secure is an MCP server listed in the public MCP registry as io.github.Choppaaahh/sendgrid-mcp-secure. Security-first SendGrid MCP server: dry-run default, recipient allowlists, rate caps, audit log. This page covers its PyPI package (sendgrid-mcp-secure).
Is the SendGrid Secure MCP server safe to use?
SendGrid Secure scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. 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 SendGrid Secure MCP server expose?
SendGrid Secure exposes 11 tools: preview_email, send_email, add_suppression, remove_suppression, list_templates, and 6 more. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Is the SendGrid Secure MCP server still maintained?
SendGrid Secure is still listed as active in the MCP registry. We last reached this channel on 4 October 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 SendGrid Secure MCP server under?
SendGrid Secure declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.