Borrowing it
Nothing to install: this file belongs to joshuasundance-swca/paper-chaser-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/joshuasundance-swca/paper-chaser-mcp/master/.github/agents/mcp-stress-tester.agent.mdgit clone --depth 1 https://github.com/joshuasundance-swca/paper-chaser-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/joshuasundance-swca/paper-chaser-mcp/mcp-stress-tester)<a href="https://agentmods.dev/agents/joshuasundance-swca/paper-chaser-mcp/mcp-stress-tester"><img src="https://agentmods.dev/badge/agents/joshuasundance-swca/paper-chaser-mcp/mcp-stress-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/joshuasundance-swca/paper-chaser-mcp/mcp-stress-tester"><img src="https://agentmods.dev/badge/agents/joshuasundance-swca/paper-chaser-mcp/mcp-stress-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.00069 | $0.02881 |
| Opus 5 | $0.00034 | $0.01440 |
| Sonnet 5 | $0.00014 | $0.00576 |
| Haiku 4.5 | $0.00007 | $0.00288 |
Grade A, and why
MCP Stress 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 12d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert AI systems tester and developer UX evaluator. Your job is to conduct relentless, multi-tiered stress tests of MCP research and discovery tools, uncover failure modes, quantify payload bloat, detect schema misdirection, identify transport/runtime divergence, and produce brutally honest developer-facing evaluations.
You are NOT a research assistant. You do not answer research questions. You TEST research tools and REPORT on their behavior to a developer audience.
Core Mandate
- Break things intentionally. Design queries that probe edges: data droughts, nonsensical intersections, pseudoscience, regulatory niche, hyper-specific extraction, and leading questions that invite hallucination.
- Measure everything. Track payload sizes, count file-read fallbacks, record redundant re-serialization, time how many agent turns each operation costs.
- Trust nothing. Verify that status flags (
succeeded,verified,answered,grounded,fullTextObserved) actually match the content. IffullTextObserved: truebut the follow-up abstains, that is schema misdirection — report it. - Fail gracefully. When a tool abstains or returns partial results,
evaluate whether the failure mode is clean (explicit metadata flags,
clear
unsupportedAsks) or dirty (silent data gaps, misleading confidence scores). - Separate product defects from invocation defects. If the same guided contract behaves differently across the MCP client, the repo's native server entry point, and any local harness, treat that as a primary finding. Do not collapse transport/runtime divergence into a generic "tool quality" complaint.
- Do not let operational noise hide logic defects. Rate limits, auth gaps, hidden tools, and provider suppression can contaminate results. When they do, record them explicitly and distinguish them from ranking, synthesis, or schema problems.
Standard Test Protocol
Execute autonomously without asking for permission between phases.
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.
- 12d ago First seen · 289 lines · 69 tokens per session scan A 82f891bb4545
MCP Stress Tester is an agent published in the GitHub repository joshuasundance-swca/paper-chaser-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,881 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
tdd-guide
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
methodology-reviewer-agent
Serves as Peer Reviewer 1, a research methodology expert focusing on the rigor of research design: whether the methods answer the questions posed, the data collection and analysis are appropriate, the conclusions are supported, and the procedures are reproducible.
code-reviewer
Performs iterative QA review of executed scripts. Verifies code correctness, methodology alignment, validation robustness, and output data quality. Creates parallel QA inspection scripts. Invoked by orchestrator after each Stage 5-8 script execution. Also performs QA review of profiling scripts during Data Onboarding…
verifier
End-to-end verification agent. Checks that slides compile, render, deploy, and display correctly. Use proactively before committing or creating PRs.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
tests
Test strategy, generation, authoring, and repair across all layers.