Skills/npm/mcp-server

mcp-server@2.3.1

VERIFIED· not started

Publisher claims: "An MCP server that gives AI agents a practical interface to Mailgun workflows for sending, diagnosing deliverability, and taking account actions safely." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher mailgun · publishing for 278 daysInstalls 11,451Last detonated 3d ago
$claude mcp add mcp-server -- npx -y @mailgun/mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MAILGUN_API_KEYConfiguration, not credentials: MAILGUN_API_HOSTNAME, MAILGUN_API_REGION, TOOL_ID_PATTERN
Where it talks to
mailgun.com (its own)
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for MAILGUN_API_KEY and talks to mailgun.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets MAILGUN_API_KEY=mailgun.com -- npx -y @mailgun/mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 95/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 8 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.9sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-oATjbq/task/home/.npm/_logs/2026-11-11T12_37_33_113Z-debug-0.log
7.9sclaimednot started: dependency install failed (exit 1); the server itself was not observed
7.9sprocessscript backend runs setup only
7.9sprocessno install scripts to re-run

Static findings

No findings across 2,594 lines in 42 files.

Cost to the agent

Instructions loaded
≈75 tok
1 file · 42 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @mailgun/mcp-server@2.3.1 as of 3d ago. This is the package itself, not its dependencies.