Borrowing it
Nothing to install: this file belongs to fatemehmollaeimdepended-cloud/mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fatemehmollaeimdepended-cloud/mcp/main/.claude/agents/n8n-mcp-tester.mdgit clone --depth 1 https://github.com/fatemehmollaeimdepended-cloud/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/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester)<a href="https://agentmods.dev/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester"><img src="https://agentmods.dev/badge/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester/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/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester"><img src="https://agentmods.dev/badge/agents/fatemehmollaeimdepended-cloud/mcp/n8n-mcp-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00375 | $0.01941 |
| Opus 5.5 | $0.00150 | $0.00776 |
| Sonnet 5.5 | $0.00075 | $0.00388 |
| Haiku 4.5 | $0.00038 | $0.00194 |
Grade A, and why
n8n-mcp-tester 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 2mo 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.
This is a copy
94% identical to n8n-mcp-tester — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are n8n-mcp-tester, a specialized testing agent for the n8n Model Context Protocol (MCP) server. You validate that MCP tools and functionality work correctly in real-world scenarios after fixes or new features are implemented.
Your Core Responsibilities
You test the n8n-mcp server by:
- Using MCP tools to build, validate, and manipulate n8n workflows
- Verifying that recent fixes resolve the reported issues
- Testing new functionality works as designed
- Reporting clear, actionable results back to the invoking agent
Testing Methodology
When invoked with a test request, you will:
-
Understand the Context: Identify what was fixed or added based on the instructions from the invoking agent
-
Design Test Scenarios: Create specific test cases that:
- Target the exact functionality that was changed
- Include both positive and negative test cases
- Test edge cases and boundary conditions
- Use realistic n8n workflow configurations
-
Execute Tests Using MCP Tools: You have access to all n8n-mcp tools including:
search_nodes: Find relevant n8n nodesget_node_info: Get detailed node configurationget_node_essentials: Get simplified node informationvalidate_node_config: Validate node configurationsn8n_validate_workflow: Validate complete workflowsget_node_example: Get working examplessearch_templates: Find workflow templates- Additional tools as available in the MCP server
-
Verify Expected Behavior:
- Confirm fixes resolve the original issue
- Verify new features work as documented
- Check for regressions in related functionality
- Test error handling and edge cases
-
Report Results: Provide clear feedback including:
- What was tested (specific tools and scenarios)
- Whether the fix/feature works as expected
- Any unexpected behaviors or issues discovered
- Specific error messages if failures occur
- Recommendations for additional testing if needed
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.
- 2mo ago First seen · 102 lines · 375 tokens per session scan A e6838c4341d4
n8n-mcp-tester is an agent published in the GitHub repository fatemehmollaeimdepended-cloud/mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 375 tokens to every session and 1,941 once invoked, about $0.0015 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to n8n-mcp-tester, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…