Shoot Email (powersurge01/shoot-email) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

C
Emerging
74/100

Shoot Email

An MCP server that provides AI agents with a persistent, agent-native email mailbox for sending, receiving, and managing emails through bounded-context retrieval, idempotent operations, and explicit acknowledgement.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

powersurge01

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: INBOUND_WEBHOOK_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: CLOUDFLARE_API_TOKEN, CLOUDFLARE_EMAIL_API_TOKEN, INBOUND_WEBHOOK_TOKEN, SHOOT_EMAIL_DEMO_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCLOUDFLARE_ACCOUNT_ID
🔐 secretCLOUDFLARE_API_TOKEN, because Wrangler reserves the generic name for its own
🔐 secretCLOUDFLARE_EMAIL_API_TOKEN. Do not name that application secret
configCLOUDFLARE_FROM_EMAILBy default, outbound mail uses the generated alias as from. Set only when you want to force a single default sender. The sender domain must be onboarded for Cloudflare Email Sending.
configCUSTOM_ALIAS_CHANGE_COOLDOWN_DAYS
configHOSTED_BACKEND_URL
configINBOUND_DOMAIN
🔐 secretINBOUND_WEBHOOK_TOKENwrangler secret put ; do not add it to the Wrangler
configMAIL_PROVIDERmock and OUTBOUND_SENDING_ENABLED=false. The hosted demo may
configMCP_ALLOW_DEV_IDENTITYmailbox. Do not set in production.
configMCP_DEV_OPENAI_ORGANIZATION
configMCP_DEV_OPENAI_SESSION
configMCP_DEV_OPENAI_SUBJECT
configOUTBOUND_GLOBAL_DAILY_LIMIT
configOUTBOUND_GLOBAL_HOURLY_LIMIT
configOUTBOUND_SENDING_ENABLEDMAIL_PROVIDER=mock and =false. The hosted demo may
configREMOTE_MCP_URL
configSHOOT_EMAIL_CONFIG_DIR
🔐 secretSHOOT_EMAIL_DEMO_TOKEN
configSHOOT_EMAIL_ENV
configTEST_DATABASE_URLIntegration tests use , defaulting to a database named
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// quality suggestions

Tool annotations

3/10 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

10/10 tools missing one or more hints — shoot_email.initialize_mailbox (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_service_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_mailbox_identity (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (INBOUND_WEBHOOK_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/powersurge01/shoot-email)](https://m8ven.ai/mcp/powersurge01/shoot-email)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 728a8c305a40bfdad54cc029a77d4a98ba5ad9ca
code hash: 55a5f3c7bd4497bac83a5403cd68be7f19e779ab7819bd18c53948786c1db40e
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client