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/tikhub/tikhub-plugin/tikhub-threadsgit clone --depth 1 https://github.com/TikHub/tikhub-pluginWrote 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/tikhub/tikhub-plugin/tikhub-threads)<a href="https://agentmods.dev/mcp/tikhub/tikhub-plugin/tikhub-threads"><img src="https://agentmods.dev/badge/mcp/tikhub/tikhub-plugin/tikhub-threads.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
tikhub-threads 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 4d 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
{
"tikhub-threads": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.tikhub.io/threads/mcp",
"--header",
"Authorization: Bearer ${TIKHUB_API_KEY}"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 12 lines scan A a6bdfde10395
tikhub-threads is an MCP server published in the GitHub repository TikHub/tikhub-plugin (6 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
reelminner
MCP server "reelminner" as configured in ilovekushgola/reelminner. Runs mcp_server.py with python. Needs 1 environment variable to run.
markifact
MCP server "markifact", hosted remotely at api.markifact.com, as configured in markifact/markifact-mcp.
eu-ai-act
MCP server "eu-ai-act", hosted remotely at mcp.lexbeam.com, as configured in lexbeam-software/eu-ai-governance-plugin.
viral-video-blueprint
MCP server "viral-video-blueprint" as configured in loveld322/viral-video-blueprint. Runs locally from the viral-video-blueprint Python package.
insta
MCP server "insta" as configured in lstunn25ai/mcp-insta. Runs locally from the mcp-insta npm package.
upload-post-mcp
MCP server "upload-post-mcp" as configured in MrSagarShah/upload-post-mcp. Runs locally from the upload-post-mcp npm package. Needs 1 environment variable to run.