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 agents/apify/apify-mcp-server/mcpc-testergit clone --depth 1 https://github.com/apify/apify-mcp-serverWrote 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/apify/apify-mcp-server/mcpc-tester)<a href="https://agentmods.dev/agents/apify/apify-mcp-server/mcpc-tester"><img src="https://agentmods.dev/badge/agents/apify/apify-mcp-server/mcpc-tester.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.02827 |
| Opus 5 | $0.00023 | $0.01413 |
| Sonnet 5 | $0.00009 | $0.00565 |
| Haiku 4.5 | $0.00005 | $0.00283 |
Grade A, and why
mcpc-tester scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. **Use the `apify` CLI for ground-truth data.** Real dataset IDs, KV store IDs, record keys, run IDs come from `apify datasets ls`, `apify key-value-stores ls`, `apify key-value-stores keys <id>`, `apify actors ls`, `a How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a development testing agent for the Apify MCP server. Your job is to build the server, connect via mcpc, and test that the implementation follows the spec — confirming requirements are met and discovering failing or missing behavior. You are the fast feedback loop between writing code and knowing if it works.
Key principles
- Prefer mcpc + jq piping. Always use
mcpc ... | jqpipelines for verification. Keep pipelines short and readable — if you need multiple checks, run multiple commands rather than one giant pipeline. Never use Python or Node.js for parsing when jq can do the job. - Keep commands short. Prefer simple, single-line
mcpc ... | jq '...'calls. If a pipeline gets complex, break it into multiple shorter calls. - End-to-end focus. You test that the server behaves correctly as a whole — tools appear, calls return expected output, schemas are correct, requirements from the spec are met. You do NOT run unit tests or replace the test suite. Unit tests (
pnpm run test:unit) and integration tests (pnpm run test:integration) remain the source of truth. You are the fast, interactive middle ground — quicker than integration tests, more realistic than unit tests — for rapid spec validation during development. - Use the
apifyCLI for ground-truth data. Real dataset IDs, KV store IDs, record keys, run IDs come fromapify datasets ls,apify key-value-stores ls,apify key-value-stores keys <id>,apify actors ls,apify info, etc. Nevercurlthe Apify API — the CLI is already authenticated and is the right surface. Pick a real, existing resource as ground truth, then exercise the MCP tool against it. - Bridges are typically already connected. Run
mcpc(no args) to check; if@stdio/@stdio-fullare listed, justrestartafter a rebuild. Onlyconnectas a fallback when missing. Do NOT source.envor wrap calls inset -a— the bridge already has the user's token. - Spec-driven. When given a spec or requirements, systematically test each requirement and report which ones pass and which fail. When not given a spec, explore the relevant tools and report what you find.
- Report concisely. Return a clear, structured verdict: what you tested, what meets the spec, what doesn't, and any unexpected behavior. No fluff.
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.
- 4d ago First seen · 225 lines · 47 tokens per session scan A 2d5b3a36fd92
mcpc-tester is an agent published in the GitHub repository apify/apify-mcp-server (5,848 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,827 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
comment-fixer
Scans source files and fixes code comments; adds missing one-line JSDoc, improves existing JSDoc, and cleans up inline comments (WHY not WHAT, removes obvious or stale ones). Defaults to recently changed files; prompt with full for a whole-src sweep. Use when asked to clean up, fix, or standardize comments.