This release is a pre-release and may not be stable for production use.
✨ Introduction
I created this repository to automatically test my MCP tool servers.
pytest --mcp-tools=http://localhost:8000
Will create some tests, automatically, and you will get an output that looks like this:
🔍 MCP Tools: Discovering endpoints at http://test-server:8000...
Retry 1/10: Checking http://test-server:8000...
✓ Server reachable (status: 404)
✓ Found endpoint: /mcp (status: 406)
✗ Endpoint /sse not found (status: 404)
✗ Endpoint /messages not found (status: 404)
✅ MCP Tools: Discovered endpoints: /mcp
============================= test session starts ==============================
platform linux -- Python 3.11.14, pytest-9.0.2, pluggy-1.6.0 -- /usr/local/bin/python3.11
cachedir: .pytest_cache
rootdir: /app
configfile: pyproject.toml
plugins: cov-7.0.0, anyio-4.12.1, depends-1.0.1, mock-3.15.1, mcp-tools-0.1.0
collecting ... collected 3 items
✅ MCP tools test created for discovered endpoints: /mcp
📡 HTTP streaming support detected
test_samples/test_sample_math.py::test_sample_addition PASSED [ 25%]
test_samples/test_sample_math.py::test_sample_multiplication PASSED [ 50%]
.::test_mcp_tools[POST /mcp] PASSED [ 75%]
test_samples/test_sample_math.py::test_sample_string_operations PASSED [100%]
============================== 4 passed in 0.03s ===============================
Note the test called .::test_mcp_tools[POST /mcp] PASSED [ 75%].
This is automatically generated by the plugin, and the plan is to make more of these automatically-generated tests based on descriptions of the tools.
Reporting Issues
If you tested this on your server, and think that there is an issue, just give me the docker image of your server in the issue, and tell me what you are expecting, what you got.
If you don't have a docker hub image, give me a minimal example. That's all I need.
🛠️ Development
The only requirement is 🐳 Docker.
(The .devcontainer and tasks.json are prepared assuming a *nix system, but if you know the commands, this will work on Windows, too.)
- Clone the repo.
- Branch out.
- Open in "devcontainer" on VS Code and start developing. Run
pytestunderteststo test. - Akternatively, if you are a fan of Test-Driven Development like me, you can run the tests without getting on a container.
.vscode/tasks.jsonhas the command to do so, but it's also listed here:
docker compose -f tests/docker-compose.yaml up --build --abort-on-container-exit --exit-code-from test
Metadata
Release files for pytest-mcp-tools 0.1.1.dev202602230244
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pytest_mcp_tools-0.1.1.dev202602230244.tar.gz | 9.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_mcp_tools-0.1.1.dev202602230244-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.0 kB
Release files / pytest_mcp_tools-0.1.1.dev202602230244.tar.gz
| Download URL | pytest_mcp_tools-0.1.1.dev202602230244.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2890cb093466c33e70d7f2a2d2d83df8515403fba1667f3da07ac86689f6bf08
|
|
BLAKE2b-256 checksum How to use checksums |
f51c68429ea9ce3769ff0db0219c8a63301ab8b177eb3f1a68aeede3cb4bc8f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 23, 2026.
Transparency logRelease files / pytest_mcp_tools-0.1.1.dev202602230244-py3-none-any.whl
| Download URL | pytest_mcp_tools-0.1.1.dev202602230244-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1050ee22ef6a55866a1afd01563342577c8177e4bb8972846f229443196185c6
|
|
BLAKE2b-256 checksum How to use checksums |
7087725c449765bc28cee4479f16cb2dcb8ba7128002bbbd64c63b55220bbbf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 23, 2026.
Transparency logSecurity for pytest-mcp-tools 0.1.1.dev202602230244
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pytest_mcp_tools-0.1.1.dev202602230244.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.