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/exp78/telldone-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/exp78/telldone-mcp/telldone)<a href="https://agentmods.dev/mcp/exp78/telldone-mcp/telldone"><img src="https://agentmods.dev/badge/mcp/exp78/telldone-mcp/telldone/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/exp78/telldone-mcp/telldone"><img src="https://agentmods.dev/badge/mcp/exp78/telldone-mcp/telldone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
telldone 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
{
"telldone": {
"command": "npx",
"args": [
"-y",
"telldone-mcp"
],
"env": {
"TELLDONE_TOKEN": ""
}
}
}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 · 12 lines scan A 06b7f8b066da
telldone is an MCP server published in the GitHub repository exp78/telldone-mcp (0 stars, last pushed 2mo 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
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
raycast
Raycast workflow automation MCP server with 9 tools. Runs locally from the raycast-mcp-server npm package.
mailwarden
Native Gmail MCP server: search, labels, archive, trash, attachments, and snooze. Runs locally from the mailwarden npm package. Needs 4 environment variables to run.
habitica
MCP server "habitica" as configured in rodcordeiro/habitica-mcp. Runs ../../dist/index.js with node. Needs 3 environment variables to run.
pomodoro-ai-mcp
Pomodoro Ai MCP server. Tools: start session, stop session, get stats. Built by MEOK AI Labs. Runs locally from the pomodoro-ai-mcp Python package.
acuity-scheduling
Read appointments, types, calendars and availability; create, cancel or reschedule bookings. Remote server at acuity-scheduling.usefulapi.io.