2 findingsStatic scanned
Adds Storybook component and story documentation tools to an MCP server you run yourself.
9.4M installs/moMIT
Email Guard MCP
mlawsonking · MCP server
Email Guard MCP gives an agent that reads and sends email three tools. The inbound scan looks for injection and hijack patterns, compares sender headers, checks the sender domain in DNS and RDAP and scores links. The outbound scan finds secrets and personal data, returns a redacted copy and flags deliverability problems. A domain check reports SPF, DMARC, MX and domain age. The injection check is pattern matching, not a classifier, and rules update about once a day unless run offline.
Written by ooruby from the README of email-guard-mcp 1.4.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can check an email for hijack attempts before acting on it, and check its own draft for leaked secrets before sending.
What you could do with it
- Have your agent scan an incoming message for hidden instructions and spoofed sender details before it acts on it.
- Run a draft through the outbound scan to find API keys or card numbers and get a redacted copy back.
- Check whether a sender's domain has weak or enforced email authentication and how old the domain is.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- eval (core/engines/code.js:19)
- dynamic Function constructor (core/engines/code.js:20)
- eval (core/engines/code.js:23)
- python subprocess (core/engines/code.js:24)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Licence and provenance
- finding
- no LICENCE file at the root (.)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
MCP server: email safety for AI agents: scan inbound email for 'AI agent phishing' (prompt-injection/spoof) before acting, and outbound email for secret/PII leaks + deliverability before sending. Deterministic, free, no LLM.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 1.4.0, the file with digest sha512-EuLkFiEBco0H4B0BN81N9kGgSkC79gzXT5o7/gJ114B8ri49WBwrYOpZ+h+4+9Kf6qtd5+2yGRgQenTGeTQZag==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"email-guard-mcp": {
"command": "npx",
"args": [
"-y",
"email-guard-mcp@1.4.0"
]
}
}
}Or run it directly.
npx -y email-guard-mcp@1.4.0Pinned to 1.4.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- email-guard-mcp
- Version read
- 1.4.0
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/email-guard-mcp)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-07
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.