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.

SendGrid MCP by usefulapi

REMOTE · SENDGRID.USEFULAPI.IO

Send email and read templates, marketing contacts, lists, stats, bounces and unsubscribes.

−59 this week 18 Trust /100

Last scanned (3 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 2 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “add_or_update_marketing_contacts” functional
    • New prompt “check_delivery_bounce_and_spam_numbers_for_a_period” functional
    • New prompt “check_our_marketing_contacts_and_lists” functional
    • New prompt “list_bounced_and_unsubscribed_addresses” functional
    • New prompt “review_our_email_templates” functional
    • New prompt “send_an_email_or_a_template_email” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 0
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 26 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.

  • 25 Oct 26 0
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
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 · Probed https://sendgrid.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sendgrid.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sendgrid.usefulapi.io/mcp Redirected 302 https://usefulapi.io/sendgrid/
http (plaintext) http://sendgrid.usefulapi.io/mcp Inconclusive 302 http://sendgrid.usefulapi.io/mcp
MCP tools · 11 exposed · ~1,173 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
sendgrid_add_or_update_contacts ~101

UPSERTS marketing contacts (creates new ones, updates existing ones by email) and optionally adds them to lists. This is an ASYNC job — returns { job_id } you can poll. SendGrid: PUT /v3/marketing/contacts.

NameTypeReqDescription
contactsarrayyesContacts to add or update (each needs an `email`; custom fields pass through).
list_idsarray–List ids to add these contacts to.

No output schema declared.

No examples provided.

sendgrid_get_contact_count ~46

Get the total number of Marketing Campaigns contacts on your account. Returns { contact_count, billable_count }. SendGrid: GET /v3/marketing/contacts/count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sendgrid_get_stats ~137

Get global email statistics over a date range (delivered, opens, clicks, bounces, spam reports, etc.). Returns an array of { date, stats: [{ metrics: {...} }] }. SendGrid: GET /v3/stats.

NameTypeReqDescription
aggregated_bystring–How to group the returned statistics.
end_datestring–End date in YYYY-MM-DD format (defaults to today).
limitinteger–Number of results to return.
offsetinteger–Number of results to skip (for pagination).
start_datestringyesStart date in YYYY-MM-DD format (required).

No output schema declared.

No examples provided.

sendgrid_get_template ~59

Get a single transactional email template by id, including its versions (subject + content). SendGrid: GET /v3/templates/{template_id}.

NameTypeReqDescription
template_idstringyesThe template id (dynamic template ids start with "d-").

No output schema declared.

No examples provided.

sendgrid_list_bounces ~134

List bounced email addresses (the bounce suppression list). Returns an array of { created, email, reason, status }. SendGrid: GET /v3/suppression/bounces.

NameTypeReqDescription
emailstring–Filter to a specific bounced email address.
end_timeinteger–End of the time range, as a Unix timestamp (seconds).
limitinteger–Number of bounces to return (1–500).
offsetinteger–Number of bounces to skip (for pagination).
start_timeinteger–Start of the time range, as a Unix timestamp (seconds).

No output schema declared.

No examples provided.

sendgrid_list_global_unsubscribes ~118

List globally-unsubscribed email addresses (the global suppression list). Returns an array of { created, email }. SendGrid: GET /v3/suppression/unsubscribes.

NameTypeReqDescription
end_timeinteger–End of the time range, as a Unix timestamp (seconds).
limitinteger–Number of records to return.
offsetinteger–Number of records to skip (for pagination).
start_timeinteger–Start of the time range, as a Unix timestamp (seconds).

No output schema declared.

No examples provided.

sendgrid_list_marketing_lists ~91

List your Marketing Campaigns contact lists, each with its id, name, and contact_count. Returns { result: [...], _metadata }. SendGrid: GET /v3/marketing/lists.

NameTypeReqDescription
page_sizeinteger–Number of lists per page (1–1000, default 100).
page_tokenstring–Pagination token from a previous response's _metadata.

No output schema declared.

No examples provided.

sendgrid_list_templates ~106

List your transactional email templates (Dynamic and/or Legacy). Returns { result: [...], _metadata } — use _metadata.next / page_token to paginate. SendGrid: GET /v3/templates.

NameTypeReqDescription
generationsstring–Which template generation(s) to return (default: dynamic).
page_sizeinteger–Number of templates per page (1–200, default 50).
page_tokenstring–Pagination token from a previous response's _metadata.

No output schema declared.

No examples provided.

sendgrid_ping ~38

Health check — verifies the API key works and returns the scopes (permissions) granted to it. SendGrid: GET /v3/scopes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sendgrid_search_contacts_by_email ~78

Look up marketing contacts by exact email address (a read-only lookup — mutates nothing). Returns { result: { "<email>": { contact: {...} } } }. SendGrid: POST /v3/marketing/contacts/search/emails.

NameTypeReqDescription
emailsarrayyesOne or more exact email addresses to look up.

No output schema declared.

No examples provided.

sendgrid_send_mail ~265

SENDS A REAL EMAIL immediately via SendGrid. Provide `from_email` and one or more `to` recipients, plus EITHER a subject + content OR a `template_id` (dynamic template ids start with "d-", pass values via dynamic_template_data). Returns { status: "accepted", message_id }. SendGrid: POST /v3/mail/send.

NameTypeReqDescription
bccarray–BCC recipient email addresses.
ccarray–CC recipient email addresses.
contentstring–The email body. Required unless template_id is provided.
content_typestring–MIME type of the body content (default text/html).
dynamic_template_dataobject–Key/value data merged into a dynamic template's handlebars variables.
from_emailstringyesSender email address (must be a verified sender/domain).
from_namestring–Sender display name.
reply_tostring–Reply-To email address.
subjectstring–Email subject line. Required unless a template_id supplies it.
template_idstring–A template id to render (dynamic template ids start with "d-"). When set, `content` is omitted.
toarrayyesOne or more recipient email addresses.

No output schema declared.

No examples provided.

Install

How do I install the SendGrid MCP by usefulapi server?

SendGrid MCP by usefulapi is a hosted endpoint at https://sendgrid.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · sendgrid.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-sendgrid 'https://sendgrid.usefulapi.io/mcp'
Common questions

What is the SendGrid MCP by usefulapi server?

SendGrid MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sendgrid. Send email and read templates, marketing contacts, lists, stats, bounces and unsubscribes. This page covers its hosted endpoint (https://sendgrid.usefulapi.io/mcp).

Is the SendGrid MCP by usefulapi server safe to use?

SendGrid MCP by usefulapi scores 18 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 SendGrid MCP by usefulapi server expose?

SendGrid MCP by usefulapi exposes 11 tools: sendgrid_ping, sendgrid_list_templates, sendgrid_get_template, sendgrid_list_marketing_lists, sendgrid_get_contact_count, and 6 more. Their descriptions and schemas cost roughly 1,173 tokens of context every time the server is loaded.

Does the SendGrid MCP by usefulapi server require authentication?

Its publisher declares no required credentials for SendGrid MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the SendGrid MCP by usefulapi server still maintained?

SendGrid MCP by usefulapi 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.