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/TadMSTR/vikunja-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/tadmstr/vikunja-mcp/vikunja-mcp)<a href="https://agentmods.dev/mcp/tadmstr/vikunja-mcp/vikunja-mcp"><img src="https://agentmods.dev/badge/mcp/tadmstr/vikunja-mcp/vikunja-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/tadmstr/vikunja-mcp/vikunja-mcp"><img src="https://agentmods.dev/badge/mcp/tadmstr/vikunja-mcp/vikunja-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vikunja-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 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.
This is a copy
88% identical to novyx-mcp — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "vikunja-mcp": { "command": "uvx", "args": [ "vikunja-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 · 8 lines scan A 65210993a172
vikunja-mcp is an MCP server published in the GitHub repository TadMSTR/vikunja-mcp (3 stars, last pushed 3d 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. It is 88% identical to novyx-mcp, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
stdio-full
MCP server "stdio-full" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
stdio
MCP server "stdio" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
dev
MCP server "dev", hosted remotely at localhost, as configured in apify/apify-mcp-server.
apify-mcp-server
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡. Remote server at mcp.apify.com.
monday.com
MCP server for monday.com integration. Remote server at mcp.monday.com.
monday
MCP server "monday", hosted remotely at mcp.monday.com, as configured in mondaycom/mcp.