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/vikrant82/tasksync-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/vikrant82/tasksync-mcp/tasksync-mcp-http)<a href="https://agentmods.dev/mcp/vikrant82/tasksync-mcp/tasksync-mcp-http"><img src="https://agentmods.dev/badge/mcp/vikrant82/tasksync-mcp/tasksync-mcp-http/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/vikrant82/tasksync-mcp/tasksync-mcp-http"><img src="https://agentmods.dev/badge/mcp/vikrant82/tasksync-mcp/tasksync-mcp-http.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tasksync-mcp-http 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
{ "tasksync-mcp-http": { "command": "npx", "args": [ "-y", "tasksync-mcp-http" ] } }
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 · 9 lines scan A 38c5b2225899
tasksync-mcp-http is an MCP server published in the GitHub repository vikrant82/tasksync-mcp (1 stars, last pushed 6mo 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
loomiomcp
Model Context Protocol server for Loomio. Lets Claude (Desktop, Code, or web Projects via Custom Connector) read and create Loomio discussions, polls, and comments, manage group memberships, and analyse member activity in plain English. Runs locally from the loomiomcp npm package.
mcp-b24
MCP server for Bitrix24 (wraps the Bitrix24 REST API — CRM, Tasks, IM, Disk, Calendar, HR, Smart processes, Mail, Telephony, Workflows, Open Lines, Bots, Document Generator). 43 tools: 870 actions, RU/EN natural-language support, webhook + OAuth 2.0, des. Runs locally from the mcp-b24 npm package.
linear
Linear's hosted MCP server: lets the agent read and update issues, projects and cycles. Remote server at mcp.linear.app.
asana
MCP server "asana", hosted remotely at mcp.asana.com, as configured in mikeprasad/aria-knowledge.
clickup
MCP server "clickup", hosted remotely at mcp.clickup.com, as configured in mikeprasad/aria-knowledge.
semaphore
MCP server "semaphore" as configured in alwh1te/agent-semaphore. Launched with asem mcp.