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/XTND-DYNAMICS/xtnd-mcp-oneWrote 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/xtnd-dynamics/xtnd-mcp-one/mcp-one)<a href="https://agentmods.dev/mcp/xtnd-dynamics/xtnd-mcp-one/mcp-one"><img src="https://agentmods.dev/badge/mcp/xtnd-dynamics/xtnd-mcp-one/mcp-one.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-one 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 7d 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
{ "mcp-one": { "command": "npx", "args": [ "-y", "@xtnd-dynamics/mcp-one" ] } }
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.
- 7d ago First seen · 9 lines scan A 96a79c145218
mcp-one is an MCP server published in the GitHub repository XTND-DYNAMICS/xtnd-mcp-one (0 stars, last pushed 10d ago), 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
mcp-server-imap
Email tools for any IMAP/SMTP provider: list, read, search, send, and manage messages. Runs locally from the @aiwerk/mcp-server-imap npm package. Needs 6 environment variables to run.
proton-mail-mcp
Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAP. Runs locally from the proton-mail-mcp npm package. Needs 15 environment variables to run.
email-mcp
IMAP/SMTP email MCP server — 47 tools, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.
pylos-mcp
Read-focused, prompt-injection-hardened email MCP server for any IMAP provider. Runs locally from the pylos-mcp npm package. Needs 5 environment variables to run.
readndraft
MCP server "readndraft" as configured in LeoPhoenixT/readNdraft-imap-mcp. Launched with uv tool run [email protected] mcp.
mcp
Email for AI agents: inboxes, send/reply/forward, search, threads, webhooks — 21 SentFromAI tools. Runs locally from the sentfromai-mcp npm package. Needs 2 environment variables to run.