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/tosin2013/pytest-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/mcp/tosin2013/pytest-mcp-server/pytest-mcp-server)<a href="https://agentmods.dev/mcp/tosin2013/pytest-mcp-server/pytest-mcp-server"><img src="https://agentmods.dev/badge/mcp/tosin2013/pytest-mcp-server/pytest-mcp-server/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/tosin2013/pytest-mcp-server/pytest-mcp-server"><img src="https://agentmods.dev/badge/mcp/tosin2013/pytest-mcp-server/pytest-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pytest-mcp-server 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.
What it actually says
{ "pytest-mcp-server": { "command": "npx", "args": [ "-y", "pytest-mcp-server" ] } }
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 46275e6c042c
pytest-mcp-server is an MCP server published in the GitHub repository tosin2013/pytest-mcp-server (1 stars, last pushed 1y 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-31.
Other mcp servers, from other repositories
smartbear-mcp
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, API Hub, PactFlow. Runs locally from the @smartbear/mcp npm package. Needs 10 environment variables to run.
podium
Mobile + canvas automation MCP for AI agents — one stdio server, 60 tools: iOS (simulator + real) & Android control, native UI automation, Maestro E2E flows, evidenced oracle-ladder assertions, React Native/Metro debugging, WebView DOM + network capture. Runs locally from the podium-mcp npm package.
podium-mcp
Mobile E2E MCP (51 tools): iOS + Android, native UI + canvas/WebGL, no-vision, RN debug. Runs locally from the podium-mcp npm package.
mcp-nodejs-debugger
An MCP server to debug Node.js at runtime. Runs locally from the @hyperdrive-eng/mcp-nodejs-debugger npm package.
mcp-server
Flaky test detection, root cause analysis, and fix suggestions for development teams. Remote server at mcp.trunk.io.
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay npm package.