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/threadlinqs-cmd/intelthreadlinqs-mcp/threadlinqs-intelligencegit clone --depth 1 https://github.com/threadlinqs-cmd/intelthreadlinqs-mcpGrade A, and why
threadlinqs-intelligence 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 yesterday.
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
{
"threadlinqs-intelligence": {
"command": "npx",
"args": [
"-y",
"intelthreadlinqs-mcp@latest"
],
"env": {
"THREADLINQS_API_KEY": "${THREADLINQS_API_KEY}"
}
}
}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.
- yesterday First seen · 12 lines scan A 18409c72ff5d
threadlinqs-intelligence is an MCP server published in the GitHub repository threadlinqs-cmd/intelthreadlinqs-mcp (0 stars, last pushed 9d 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
threatintel-mcp
MCP server "threatintel-mcp" as configured in ChristianPresley/threatintel-mcp. Runs locally from the threatintel-mcp Python package.
huntable-cti-studio
MCP server "huntable-cti-studio" as configured in dfirtnt/Huntable-CTI-Studio. Launched with bash scripts/run_mcp_server.sh.
mcp-threatintel
Unified threat intel - OTX, AbuseIPDB, GreyNoise, abuse.ch, Feodo Tracker. Runs locally from the mcp-threatintel-server npm package. Needs 4 environment variables to run.
aegisforge
MCP server "aegisforge" as configured in sunilgentyala/AegisForge-MCP. Launched with cargo run --manifest-path mcp-server/Cargo.toml --release --. Needs 1 environment variable to run.
mcp-tool-security-inspector
MCP server "mcp-tool-security-inspector" as configured in danveil/mcp-security-inspector. Runs locally from the mcp-tool-security-inspector Python package.
hachiman
MCP server "hachiman" as configured in nidhish28guhan-netizen/hachiman-agent. Runs locally from the hachiman npm package.