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/Saga-Labs/dora-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/saga-labs/dora-mcp/dora)<a href="https://agentmods.dev/mcp/saga-labs/dora-mcp/dora"><img src="https://agentmods.dev/badge/mcp/saga-labs/dora-mcp/dora/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/saga-labs/dora-mcp/dora"><img src="https://agentmods.dev/badge/mcp/saga-labs/dora-mcp/dora.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dora 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 2mo 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
{
"dora": {
"url": "https://doravideo.com/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.
- 2mo ago First seen · 5 lines scan A 2a7170d51efd
dora is an MCP server published in the GitHub repository Saga-Labs/dora-mcp (0 stars, last pushed 6d 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.
dora compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| doraSaga-Labs/dora-mcp | MCP server | 0 | 6d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| graphmindaouicher/graphmind | MCP server | 218 | 24d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| brightspaceRohanMuppa/brightspace-mcp-server | MCP server | 64 | yesterday | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| linkedin-mcpgtm-api/linkedin-mcp | MCP server | 68 | 2d ago | MIT | A | — | Claude Code |
| gtm-apigtm-api/linkedin-mcp | MCP server | 68 | 2d ago | MIT | A | — | Claude Code |
| trends-mcptrendsmcp-ai/Trends-MCP | MCP server | 47 | 5d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| competitor-trackingtrendsmcp-ai/Trends-MCP | MCP server | 47 | 5d ago | MIT | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |