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/AutomateLab-tech/n8n-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/automatelab-tech/n8n-mcp/n8n)<a href="https://agentmods.dev/mcp/automatelab-tech/n8n-mcp/n8n"><img src="https://agentmods.dev/badge/mcp/automatelab-tech/n8n-mcp/n8n/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/automatelab-tech/n8n-mcp/n8n"><img src="https://agentmods.dev/badge/mcp/automatelab-tech/n8n-mcp/n8n.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
n8n 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- n8n — 100% identical, 0 lines differ
What it actually says
{
"n8n": {
"command": "npx",
"args": [
"-y",
"@automatelab/n8n-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.
- 1mo ago First seen · 9 lines scan A 0f075b7435e9
n8n is an MCP server published in the GitHub repository AutomateLab-tech/n8n-mcp (15 stars, last pushed 6d 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-30.
Other mcp servers, from other repositories
local-reddit-research-mcp
MCP server "local-reddit-research-mcp", hosted remotely at localhost, as configured in dialog-tools/reddit-research-mcp.
directory
Quality-ranked, cross-platform directory of AI coding skills, plugins and MCP servers. Remote server at skills.911fund.io.
figma-mcp-rust
Figma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools. Runs locally from the @alvinindra/figma-mcp-rust npm package.
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.5.2). Needs 6 environment variables to run.
apibase
MCP endpoint to APIbase catalog (https://apibase.pro/llms.txt). USDC: x402 Base, MPP Tempo. Runs locally from the apibase-mcp-client npm package.
umami
MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime. Runs locally from the @mikusnuz/umami-mcp npm package. Needs 4 environment variables to run.