"A server for testing purposes" matching MCP servers:

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

MCP server for testing GitHub Actions workflows locally using nektos/act.

A specialized MCP server for QA engineering. It provides tools for user story analysis, test strategy, BDD/Gherkin scenarios, contract testing, integration tests, performance plans, security checklists, and CI/CD pipeline generation, accessible from any MCP-compatible IDE or client.

Enables submitting FMF-based test requests to Testing Farm and listing available OS composes for testing.

A multi-language testing automation server that enables AI assistants to discover, plan, and execute tests across six major programming languages. It provides comprehensive tools for repository scanning, automated test execution, and detailed coverage reporting.

Analyzes Testing Farm jobs, checks job status, and investigates failures with detailed error information.

Enables automated testing and coverage reporting for MCP services with test execution, file generation, and mock service creation. Provides comprehensive testing infrastructure including Jest integration, coverage reports, and health checks for the MCP ecosystem.

Supply-chain gate for AI agent skills and MCP servers: poison-scan tool definitions, hash-pin the vetted set into a lock file and verify drift in CI. truecopy-mcp is a drop-in stdio proxy that filters a live server's tools/list down to its pinned, unmodified, unpoisoned tools.

A Model Context Protocol server for checking package versions and metadata across multiple package managers including npm, PyPI, Maven, NuGet, RubyGems, Crates.io, and Go modules.

Enables scanning Python repos for dead code and automatically drafting a branch + PR for the safe subset (unused single-name imports) after running the repo's full test suite. All other findings are reported without modification, and a human always merges.

Record an agent's MCP tool-call workflow once, replay it deterministically for zero tokens, and get a receipt — a snapshot-testing and deterministic-execution layer for Agent Skills.

Provides disposable email inboxes for AI agents to automatically receive and extract OTPs and magic links, enabling seamless email verification during autonomous workflows.

A Model Context Protocol server for Bitbucket Cloud that lets agents read pull request diffs, comments, and pipeline logs, as well as write PR comments and edit PR details.

An MCP server that enables AI assistants to discover and execute Nox sessions for project automation tasks like testing, linting, and building. It provides tools to list available sessions and run them using specific Python versions, tags, or keyword expressions.

Enables AI assistants to summarize Playwright test runs, identify flaky tests, heuristically triage failures, generate Playwright test stubs, and retrieve recent GitHub CI status through MCP tool calls.

Enables AI agents to interact with Appcircle mobile CI/CD platform for build management, signing identities, testing distribution, and reporting.

A Model Context Protocol server that monitors shadow-cljs builds and provides real-time build status updates for ClojureScript projects, allowing LLMs to verify build status after making code changes.

Enables code-review gating by converting a git diff into a typed verdict with safety probabilities, severity, and recommended actions for auto-merge or human review.

Publishes normalized release notices to a configured webhook via MCP, with built-in validation, deterministic dry-run mode, and a clear boundary for authority gates.

A reference MCP server for observing Vercel projects and deployments over stdio. It provides read-only tools to list and fetch details of Vercel projects and deployments.