mailgun-smtp-server

mailgun-smtp-server likely provides an SMTP server implementation that forwards incoming emails through Mailgun (acting as a local SMTP relay compatible with Mailgun’s requirements).

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure email smtp mailgun relay integration infrastructure
⚙ Agent Friendliness
24
/ 100
Can an agent use this?
🔒 Security
38
/ 100
Is it safe for agents?
⚡ Reliability
5
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
30
Error Messages
0
Auth Simplicity
40
Rate Limits
0

🔒 Security

TLS Enforcement
40
Auth Strength
50
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
40

Security depends heavily on implementation details (TLS requirement, SMTP AUTH mechanisms, credential storage/rotation, logging of message headers/content). No concrete evidence was provided in the prompt.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
20
AF Security Reliability

Best When

You need an SMTP-compatible entry point that relays messages to Mailgun, and you can configure the server and credentials securely.

Avoid When

You cannot verify the server’s TLS/auth/error handling behavior or cannot operate/manage an SMTP service safely.

Use Cases

  • Receive outbound email from an application using SMTP and deliver through Mailgun
  • Simplify legacy systems that can only speak SMTP
  • Centralize email delivery control, logging, and forwarding via Mailgun

Not For

  • Receiving inbound email from Mailgun to your server (webhooks/IMAP are not implied)
  • Highly regulated environments without clear TLS/auth configuration details
  • Use cases requiring a fully featured Mail Transfer Agent beyond SMTP-to-Mailgun forwarding

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: SMTP AUTH (implied by being an SMTP server) Mailgun credentials for forwarding (API key / SMTP credentials depending on implementation)
OAuth: No Scopes: No

Auth method details (SMTP AUTH mechanism, Mailgun credential type, how credentials are stored) are not provided in the prompt, so these are inferred from the package name/typical patterns.

Pricing

Free tier: No
Requires CC: No

No pricing information is included for the repository/package itself; Mailgun usage costs (if any) would be governed by the Mailgun account.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • SMTP servers often require correct TLS configuration and allow/deny rules; missing guidance can cause delivery failures.
  • Email sending is not naturally idempotent; retries can lead to duplicate messages unless deduplication is implemented.
  • Agents may treat SMTP as REST-like; without explicit protocol/error semantics, automated retries may be unsafe.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mailgun-smtp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered