MCP server that gives access to structured evidence regarding pytest test failures.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pytest-evidence-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# pytest-evidence-mcp MCP server that gives an AI agent access to structured evidence about pytest test failures. The server delivers deterministic data — it does not diagnose. Diagnosis is the agent's job. It exposes four tools (`list_failed_tests`, `get_test_failure`, `inspect_fixture`, `parse_pytest_output`), one documentation resource per tool, and one prompt template per tool. ## Prerequisites - Python 3.10+. - pytest installed in the **target project's own environment** (the project being investigated), not in this server's environment. This server does not depend on pytest as a package — it locates and calls the pytest already installed where the code under investigation lives (its `.venv`, by default). If pytest isn't installed there, `list_failed_tests`/`get_test_failure` raise `PytestNotFoundError` with a clean message instead of crashing. - An MCP client that supports stdio transport (Claude Code, VS Code with the Copilot Chat MCP integration, or any other MCP-compatible client). - [`uv`](https://docs.astral.sh/uv/) installed, if you're running the server via `uvx` (recommended, see below) rather than from a local clone. Any reasonably recent version works (tested with 0.12.x). ## Quick start: running from PyPI (recommended) No clone, no virtualenv to manage — `uvx` downloads the package and runs it in an isolated, disposable environment on demand: ```bash uvx pytest-evidence-mcp ``` It should log `Starting MCP Server.` to stderr and wait on stdin (this is a stdio server — running it standalone in a terminal is only useful to sanity-check that it starts; stop it with Ctrl+C). This is also the command your MCP client will run under the hood (see "Registering with an MCP client" below). **Updating to a new version:** `uvx` resolves the latest version compatible with your Python at each run, but may reuse a cached resolution. To force it to pick up a version you just published: ```bash uvx --refresh-package pytest-evidence-mcp pytest-evidence-mcp …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.