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/10xtechnology/mytinytodo-mcp-serverWrote 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/10xtechnology/mytinytodo-mcp-server/mytinytodo-mcp)<a href="https://agentmods.dev/mcp/10xtechnology/mytinytodo-mcp-server/mytinytodo-mcp"><img src="https://agentmods.dev/badge/mcp/10xtechnology/mytinytodo-mcp-server/mytinytodo-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/10xtechnology/mytinytodo-mcp-server/mytinytodo-mcp"><img src="https://agentmods.dev/badge/mcp/10xtechnology/mytinytodo-mcp-server/mytinytodo-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mytinytodo-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 1mo 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
{ "mytinytodo-mcp": { "command": "uvx", "args": [ "mytinytodo-mcp" ] } }
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.
- 1mo ago First seen · 8 lines scan A 2e764ecbaad4
mytinytodo-mcp is an MCP server published in the GitHub repository 10xtechnology/mytinytodo-mcp-server (0 stars, last pushed 3mo 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
kanban
MCP server "kanban" as configured in kanban-rs/kanban. Launched with nix run .#kanban-mcp -- kanban.json.
mindwtr
Task and project automation for local and self-hosted Mindwtr Cloud data; read-only by default. Runs locally from the mindwtr-mcp npm package. Needs 3 environment variables to run.
omnifocus-mcp-cached
MCP server "omnifocus-mcp-cached" as configured in kip-d/omnifocus-mcp. Runs locally from the omnifocus-mcp-cached npm package.
noteplan-mcp
MCP server for NotePlan note and task management. Runs locally from the @noteplanco/noteplan-mcp npm package.
lunatask-mcp
MCP server "lunatask-mcp" as configured in tensorfreitas/lunatask-mcp. Runs locally from the lunatask-mcp Python package.
taskwarrior
MCP server "taskwarrior" as configured in KaiErikNiermann/taskwarrior-mcp. Launched with <INSTALL_DIR>/target/release/task-warrior-mcp.