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.
npx agentmods add mcp/infraspecdev/tesseract/clickupgit clone --depth 1 https://github.com/infraspecdev/tesseractGrade A, and why
clickup 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 2d 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
{
"clickup": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.clickup.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.
- 2d ago First seen · 10 lines scan A 13e37feae7c1
clickup is an MCP server published in the GitHub repository infraspecdev/tesseract (5 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
amazing-marvin-complete-mcp
MCP server for Amazing Marvin with complete public-API coverage (34 tools). Runs locally from the amazing-marvin-complete-mcp Python package. Needs 3 environment variables to run.
port-eu
MCP server "port-eu", hosted remotely at mcp.port.io, as configured in port-labs/port-skills.
autonomous-sdlc-command-center
MCP server "autonomous-sdlc-command-center" as configured in Senpai-Sama7/autonomous-sdlc-command-center. Runs locally from the autonomous-sdlc-command-center Python package.
jira-product-discovery-mcp
MCP server for Jira Cloud REST APIs, native Jira Product Discovery Insights, and supporting attachments. Runs locally from the @enterpret/jira-product-discovery-mcp npm package.
jira
A comprehensive Model Context Protocol server for Jira integration with issue management, board operations, time tracking, and project management capabilities. Runs locally from the @orengrinker/jira-mcp-server npm package. Needs 3 environment variables to run.
mcp-server-rt
MCP server for RT (Request Tracker). Runs locally from the mcp-server-rt npm package. Needs 2 environment variables to run.