SendGrid Secure
PYPI · SENDGRID-MCP-SECURE · SCANNED AUG 20
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 →
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
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 5 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · sendgrid-mcp-secure
claude mcp add choppaaahh-sendgrid-mcp-secure -- uvx 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": {
"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.
- 17 Aug 26 0
- Security disclosure: unverified → pass ▲ functional
- 16 Aug 26 0
- Security disclosure: pass → unverified ▼ functional
- 14 Aug 26 65
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 20 Aug 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 |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
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.
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.