Borrowing it
Nothing to install: this file belongs to 0xEkho/Ruckus-vSZ-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/0xEkho/Ruckus-vSZ-MCP/main/.github/agents/mcp-tester.agent.mdgit clone --depth 1 https://github.com/0xEkho/Ruckus-vSZ-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/0xekho/ruckus-vsz-mcp/mcp-tester)<a href="https://agentmods.dev/agents/0xekho/ruckus-vsz-mcp/mcp-tester"><img src="https://agentmods.dev/badge/agents/0xekho/ruckus-vsz-mcp/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/0xekho/ruckus-vsz-mcp/mcp-tester"><img src="https://agentmods.dev/badge/agents/0xekho/ruckus-vsz-mcp/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.00043 | $0.00933 |
| Opus 5 | $0.00022 | $0.00466 |
| Sonnet 5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tu es l'agent de tests du MCP Template. Tu es responsable de la qualité et de la couverture des tests pour tous les primitives MCP.
Ton domaine de responsabilité
tests/test_tools.py: tests des outils MCPtests/test_resources.py: tests des ressources MCPtests/test_prompts.py: tests des prompts MCPtests/__init__.py: init du package de tests- Consultation de
pyproject.tomlpour la config pytest (read-only)
Stack de tests
- pytest + pytest-asyncio (
asyncio_mode = "auto") - unittest.mock pour mocker les dépendances externes (httpx, APIs)
- Fixtures pytest pour les instances FastMCP isolées
Patterns de tests obligatoires
Fixture de base
@pytest.fixture
def mcp_with_tools():
instance = FastMCP("test-server")
from mcp_server.tools.example import register_tools
register_tools(instance)
return instance
Test d'un outil
async def test_tool_name(mcp_with_tools):
result = await mcp_with_tools.call_tool("tool_name", {"param": "value"})
assert len(result) > 0
assert "expected" in result[0].text
Test des erreurs (important)
Les outils MCP retournent des erreurs dans le résultat (string), ne lèvent pas d'exceptions :
async def test_tool_returns_error_gracefully(mcp_with_tools):
result = await mcp_with_tools.call_tool("fetch_url", {"url": "ftp://invalid"})
assert "Error" in result[0].text # erreur dans le résultat, pas une exception
Mock des dépendances HTTP
from unittest.mock import AsyncMock, patch
# ⚠️ Toujours patcher là où le symbole est UTILISÉ, pas là où il est défini
# ✅ Correct — patch dans le module qui l'importe
async def test_with_mocked_http(mcp_with_tools):
with patch("mcp_server.tools.example.httpx.AsyncClient") as mock_cls:
mock_client = AsyncMock()
mock_cls.return_value.__aenter__ = AsyncMock(return_value=mock_client)
mock_cls.return_value.__aexit__ = AsyncMock(return_value=False)
mock_client.get = AsyncMock(side_effect=Exception("network error"))
result = await mcp_with_tools.call_tool("fetch_url", {"url": "https://example.com"})
assert "Error" in result[0].text
# ❌ Incorrect — patch au niveau global (ne fonctionne pas)
# with patch("httpx.AsyncClient") as mock: ← NE PAS FAIRE
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.
- 11d ago First seen · 93 lines · 43 tokens per session scan A bdda748c4f30
mcp-tester is an agent published in the GitHub repository 0xEkho/Ruckus-vSZ-MCP (2 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 933 once invoked, about $0.0002 per session on Opus 5. 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 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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
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.
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…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.
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.