Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/mlawsonking/MCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/mlawsonking/mcp/email-guard-mcp)<a href="https://agentmods.dev/mcp/mlawsonking/mcp/email-guard-mcp"><img src="https://agentmods.dev/badge/mcp/mlawsonking/mcp/email-guard-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/mlawsonking/mcp/email-guard-mcp"><img src="https://agentmods.dev/badge/mcp/mlawsonking/mcp/email-guard-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
email-guard-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"email-guard-mcp": {
"command": "npx",
"args": [
"-y",
"email-guard-mcp"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 10 lines scan A 5ade2a600b15
email-guard-mcp is an MCP server published in the GitHub repository mlawsonking/MCP (0 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
anytype-mcp
Official MCP server for Anytype API - your encrypted, local and collaborative wiki. Runs locally from the @anyproto/anytype-mcp npm package. Needs 1 environment variable to run.
stitchapi-docs
StitchAPI documentation search, running locally over MCP stdio. Bundled docs, no network calls per query — the offline/air-gapped counterpart to the hosted stitchapi.dev/api/mcp server. Runs locally from the @stitchapi/docs-mcp npm package.
hackmd-mcp
A Model Context Protocol server for integrating HackMD's note-taking platform with AI assistants. Runs locally from the hackmd-mcp npm package. Needs 2 environment variables to run.
yuna0x0-hackmd-mcp
Interact with your HackMD notes and teams seamlessly. Manage your notes, view reading history, and… Remote server at server.smithery.ai.
docker-gitlab-mcp-server
MCP server "docker-gitlab-mcp-server" as configured in sgaunet/gitlab-mcp. Runs in Docker (ghcr.io/sgaunet/gitlab-mcp:latest).
ibanforge
Pre-payout IBAN screening for AI agents: validation, sanctions, Swiss clearing, risk scoring. Runs locally from the ibanforge-mcp npm package. Needs 2 environment variables to run.