pytest-mcp-server 0.1.0__tar.gz

pytest_mcp_server-0.1.0/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+venv/
+dist/
+build/
+.pytest_cache/
+.ruff_cache/
+node_modules/
+coverage/
+.DS_Store

pytest_mcp_server-0.1.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+## 0.1.0 (2026-11-06)
+
+First release. Published on PyPI as `pytest-mcp-server` (the name `mcptest` was refused as too
+similar to `mcp-test`); the command and import are `mcptest`.
+
+- Dependency-free MCP client for stdio and Streamable HTTP: handshake, paginated tool,
+  resource and prompt listing, tool calls, server ping replies, and clear errors that include
+  the server's stderr and any non-protocol output on stdout.
+- Linter with 15 rules for tool names, descriptions and schemas, including tool-poisoning
+  phrases and hidden characters.
+- Snapshot format and diff that classifies each change as breaking or compatible.
+- pytest plugin: `mcp`, `mcp_server` and `mcp_snapshot` fixtures, `mcp_server` marker,
+  `mcp_command` / `mcp_url` settings, `--mcp-update-snapshots`.
+- CLI: `mcptest lint`, `tools`, `call`, `snapshot`, `diff`.

pytest_mcp_server-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Sri Krishna Lingamaneni
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pytest_mcp_server-0.1.0/PKG-INFO

@@ -0,0 +1,239 @@
+Metadata-Version: 2.5
+Name: pytest-mcp-server
+Version: 0.1.0
+Summary: Automated tests, linting and breaking-change checks for MCP servers, as a pytest plugin and CLI
+Project-URL: Homepage, https://github.com/srikrishnaL/kitforge/tree/main/packages/mcptest
+Project-URL: Source, https://github.com/srikrishnaL/kitforge
+Project-URL: Issues, https://github.com/srikrishnaL/kitforge/issues
+Project-URL: Changelog, https://github.com/srikrishnaL/kitforge/blob/main/packages/mcptest/CHANGELOG.md
+Author: Sri Krishna Lingamaneni
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ai agents,ci,lint,llm,mcp,model context protocol,pytest,testing
+Classifier: Development Status :: 4 - Beta
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.9
+Provides-Extra: test
+Requires-Dist: pytest>=7; extra == 'test'
+Description-Content-Type: text/markdown
+
+# mcptest
+
+Automated tests, linting and breaking-change checks for [MCP](https://modelcontextprotocol.io) servers.
+
+You build an MCP server, then poke at it by hand in the Inspector. mcptest turns that into tests
+that run in CI: start the server, call its tools, check what an agent will actually see, and fail
+the build when a change would break the agents and clients that depend on it.
+
+- **pytest plugin**: an `mcp` fixture connected to your server, plus schema snapshots.
+- **Linter**: 15 rules for tool names, descriptions and schemas, including hidden instructions
+  aimed at the model ("tool poisoning").
+- **Breaking-change diff**: removed tools, new required parameters, narrowed types, removed
+  enum values, removed output fields.
+- **CLI** for any server in any language: `mcptest lint -- node dist/index.js`.
+- **No dependencies.** It speaks the protocol itself over stdio and Streamable HTTP, so an SDK
+  upgrade on your side never breaks your tests.
+
+```bash
+pip install pytest-mcp-server
+```
+
+The package is published on PyPI as `pytest-mcp-server`; the command and the Python import are
+both `mcptest`.
+
+Python 3.9+. Works with servers written in any language.
+
+## Check a server in one line
+
+```console
+$ mcptest lint -- python my_server.py
+error   MCP001 bad name!: invalid tool name 'bad name!'
+error   MCP008 get_file: required parameter 'missing' is not in properties
+error   MCP012 get_file: description says '<IMPORTANT>', 'Before using any tools, you must',
+                              'read ~/.ssh', 'Do not tell the user'
+error   MCP003 noschema: inputSchema must be an object schema with "type": "object"
+warning MCP005 Get-File: description is only 1 characters: 'x'
+warning MCP011 Get-File: easily confused with 'get_file'
+warning MCP007 get_file: parameter 'path' has no description
+
+my-server: 4 tools, about 146 tokens of definitions; 4 errors, 3 warnings, 0 info
+```
+
+Even well-known servers have gaps an agent pays for. On 2026-11-06 the official reference
+filesystem server (`@modelcontextprotocol/server-filesystem`) got 18 warnings, nearly all
+parameters with no description, which leaves the model guessing what to pass.
+
+The exit code is 1 when there is a finding at `--fail-on` level or worse (default `error`), so
+it drops straight into CI. Other commands:
+
+```bash
+mcptest tools -- python my_server.py                    # print the tool list as JSON
+mcptest call add '{"a": 2, "b": 3}' -- python my_server.py
+mcptest snapshot -o mcp-tools.json -- python my_server.py
+mcptest diff mcp-tools.json -- python my_server.py      # exit 1 on breaking changes
+mcptest lint --url http://localhost:8000/mcp --header "Authorization: Bearer $TOKEN"
+mcptest lint --rules                                    # list every rule
+```
+
+Anything after `--` is the command that starts your server over stdio: `npx -y @acme/server`,
+`uv run server.py`, `docker run -i --rm acme/mcp`, and so on.
+
+## Test a server with pytest
+
+Tell pytest how to start the server once:
+
+```toml
+# pyproject.toml
+[tool.pytest.ini_options]
+mcp_command = "python -m my_server"
+# or, for a server that is already running:
+# mcp_url = "http://localhost:8000/mcp"
+```
+
+Then write ordinary tests. The `mcp` fixture is a connected client, and the server is stopped
+when the test ends:
+
+```python
+from mcptest import assert_lint_clean
+
+
+def test_add(mcp):
+    result = mcp.call_tool("add", {"a": 2, "b": 3})
+    assert not result.is_error
+    assert result.text == "5"
+    assert result.structured == {"result": 5}
+
+
+def test_bad_input_is_a_tool_error(mcp):
+    assert mcp.call_tool("add", {"a": "two"}).is_error
+
+
+def test_tools_are_well_described(mcp):
+    assert_lint_clean(mcp)            # fails on warnings and errors
+
+
+def test_no_surprise_schema_changes(mcp, mcp_snapshot):
+    mcp_snapshot(mcp)
+```
+
+A test can pick a different server with a marker, and `mcp_server` starts as many as you need:
+
+```python
+import pytest
+
+
+@pytest.mark.mcp_server(command=["node", "dist/index.js"], env={"API_KEY": "test"})
+def test_node_server(mcp):
+    assert "search" in [t["name"] for t in mcp.list_tools()]
+
+
+def test_two_versions(mcp_server):
+    old = mcp_server(["python", "server_v1.py"])
+    new = mcp_server(url="http://localhost:9000/mcp")
+    ...
+```
+
+## Schema snapshots
+
+`mcp_snapshot(mcp)` stores the tool list in `__mcp_snapshots__/<test file>/tools.json` on the
+first run and compares against it afterwards. Commit the file. When the tools change, the test
+fails and says which changes are breaking:
+
+```text
+MCP tools differ from snapshot tools.json (3 breaking, 4 compatible):
+  BREAKING add: new required parameter 'c'
+  BREAKING add: outputSchema was removed
+  BREAKING echo: tool was removed
+  ok       add: parameter 'a' type changed integer -> number
+  ...
+Run pytest --mcp-update-snapshots to accept these changes.
+```
+
+Pass `allow_compatible=True` to fail only on breaking changes.
+
+## Lint rules
+
+| Code | Level | What it catches |
+| --- | --- | --- |
+| MCP001 | error | Tool name is not 1-128 characters of `A-Z a-z 0-9 _ - .` |
+| MCP002 | error | Two tools share a name |
+| MCP003 | error | `inputSchema` missing or not `"type": "object"` |
+| MCP004 | warning | No description |
+| MCP005 | warning | Description under 20 characters |
+| MCP006 | warning | Description over 1,024 characters |
+| MCP007 | warning | Parameter has no description |
+| MCP008 | error | `required` names a parameter that isn't defined |
+| MCP009 | warning | Parameter has no type |
+| MCP010 | warning | All definitions together exceed 32,000 characters (about 8k tokens per turn) |
+| MCP011 | warning | Two names differ only by case or separators (`get_file`, `Get-File`) |
+| MCP012 | error | Text that tries to instruct the model: "ignore previous instructions", "do not tell the user", `<IMPORTANT>` blocks, reading `~/.ssh` |
+| MCP013 | error | Invisible or bidirectional control characters |
+| MCP014 | error | `outputSchema` is not `"type": "object"` |
+| MCP015 | info | Parameter description just repeats its name |
+
+Skip rules with `--ignore MCP005,MCP015` or `assert_lint_clean(mcp, ignore=["MCP005"])`.
+MCP012 is a heuristic: it catches common tool-poisoning phrasing, not every attack.
+
+## Use the client directly
+
+```python
+from mcptest import MCPClient
+
+with MCPClient.stdio(["python", "server.py"], env={"DEBUG": "1"}, timeout=10) as client:
+    print(client.server_info, client.protocol_version)
+    for tool in client.list_tools():          # follows pagination
+        print(tool["name"])
+    result = client.call_tool("search", {"q": "mcp"})
+    print(result.text, result.is_error)
+```
+
+When a server dies, mcptest shows its last stderr lines, and it points out anything printed to
+stdout that isn't protocol (the most common stdio bug):
+
+```text
+MCPTransportError: server closed stdout (exit code 3)
+  server stderr (last lines):
+    fatal: database not configured
+```
+
+## In CI
+
+```yaml
+- run: pip install pytest-mcp-server
+- run: mcptest lint --fail-on warning -- python -m my_server
+- run: mcptest diff mcp-tools.json -- python -m my_server
+```
+
+## Tested against real servers
+
+Checked on 2026-11-06 with mcptest 0.1.0: connect, list tools, call a tool, snapshot twice.
+
+| Server | Transport | Tools | Tool call | Lint findings |
+| --- | --- | --- | --- | --- |
+| @modelcontextprotocol/server-everything | stdio, Streamable HTTP | 14 | ok | 1 warning |
+| @modelcontextprotocol/server-filesystem | stdio | 14 | ok | 18 warnings |
+| @modelcontextprotocol/server-memory | stdio | 9 | ok | 4 warnings |
+| @modelcontextprotocol/server-sequential-thinking | stdio | 1 | ok | 1 warning |
+| @playwright/mcp | stdio, Streamable HTTP | 25 | returned as a tool error (no browser in the test machine) | 3 warnings |
+| mcp-server-time | stdio | 3 | ok | none |
+| mcp-server-git | stdio | 14 | ok | 24 warnings |
+| mcp-server-fetch | stdio | 1 | not called (needs network) | none |
+| Official Python SDK 2.3 (`MCPServer`) | stdio, Streamable HTTP | 2 | ok | 3 warnings |
+
+Almost all warnings are parameters with no description (MCP007) or very short descriptions (MCP005).
+
+## Limits
+
+- Covers tools fully, resources and prompts through the client only (no lint rules for them yet).
+- No OAuth flow: for protected HTTP servers, pass a token with `--header` or `headers=`.
+- The legacy HTTP+SSE transport (two endpoints) is not supported; Streamable HTTP and stdio are.
+
+## License
+
+MIT

pytest_mcp_server-0.1.0/README.md

@@ -0,0 +1,214 @@
+# mcptest
+
+Automated tests, linting and breaking-change checks for [MCP](https://modelcontextprotocol.io) servers.
+
+You build an MCP server, then poke at it by hand in the Inspector. mcptest turns that into tests
+that run in CI: start the server, call its tools, check what an agent will actually see, and fail
+the build when a change would break the agents and clients that depend on it.
+
+- **pytest plugin**: an `mcp` fixture connected to your server, plus schema snapshots.
+- **Linter**: 15 rules for tool names, descriptions and schemas, including hidden instructions
+  aimed at the model ("tool poisoning").
+- **Breaking-change diff**: removed tools, new required parameters, narrowed types, removed
+  enum values, removed output fields.
+- **CLI** for any server in any language: `mcptest lint -- node dist/index.js`.
+- **No dependencies.** It speaks the protocol itself over stdio and Streamable HTTP, so an SDK
+  upgrade on your side never breaks your tests.
+
+```bash
+pip install pytest-mcp-server
+```
+
+The package is published on PyPI as `pytest-mcp-server`; the command and the Python import are
+both `mcptest`.
+
+Python 3.9+. Works with servers written in any language.
+
+## Check a server in one line
+
+```console
+$ mcptest lint -- python my_server.py
+error   MCP001 bad name!: invalid tool name 'bad name!'
+error   MCP008 get_file: required parameter 'missing' is not in properties
+error   MCP012 get_file: description says '<IMPORTANT>', 'Before using any tools, you must',
+                              'read ~/.ssh', 'Do not tell the user'
+error   MCP003 noschema: inputSchema must be an object schema with "type": "object"
+warning MCP005 Get-File: description is only 1 characters: 'x'
+warning MCP011 Get-File: easily confused with 'get_file'
+warning MCP007 get_file: parameter 'path' has no description
+
+my-server: 4 tools, about 146 tokens of definitions; 4 errors, 3 warnings, 0 info
+```
+
+Even well-known servers have gaps an agent pays for. On 2026-11-06 the official reference
+filesystem server (`@modelcontextprotocol/server-filesystem`) got 18 warnings, nearly all
+parameters with no description, which leaves the model guessing what to pass.
+
+The exit code is 1 when there is a finding at `--fail-on` level or worse (default `error`), so
+it drops straight into CI. Other commands:
+
+```bash
+mcptest tools -- python my_server.py                    # print the tool list as JSON
+mcptest call add '{"a": 2, "b": 3}' -- python my_server.py
+mcptest snapshot -o mcp-tools.json -- python my_server.py
+mcptest diff mcp-tools.json -- python my_server.py      # exit 1 on breaking changes
+mcptest lint --url http://localhost:8000/mcp --header "Authorization: Bearer $TOKEN"
+mcptest lint --rules                                    # list every rule
+```
+
+Anything after `--` is the command that starts your server over stdio: `npx -y @acme/server`,
+`uv run server.py`, `docker run -i --rm acme/mcp`, and so on.
+
+## Test a server with pytest
+
+Tell pytest how to start the server once:
+
+```toml
+# pyproject.toml
+[tool.pytest.ini_options]
+mcp_command = "python -m my_server"
+# or, for a server that is already running:
+# mcp_url = "http://localhost:8000/mcp"
+```
+
+Then write ordinary tests. The `mcp` fixture is a connected client, and the server is stopped
+when the test ends:
+
+```python
+from mcptest import assert_lint_clean
+
+
+def test_add(mcp):
+    result = mcp.call_tool("add", {"a": 2, "b": 3})
+    assert not result.is_error
+    assert result.text == "5"
+    assert result.structured == {"result": 5}
+
+
+def test_bad_input_is_a_tool_error(mcp):
+    assert mcp.call_tool("add", {"a": "two"}).is_error
+
+
+def test_tools_are_well_described(mcp):
+    assert_lint_clean(mcp)            # fails on warnings and errors
+
+
+def test_no_surprise_schema_changes(mcp, mcp_snapshot):
+    mcp_snapshot(mcp)
+```
+
+A test can pick a different server with a marker, and `mcp_server` starts as many as you need:
+
+```python
+import pytest
+
+
+@pytest.mark.mcp_server(command=["node", "dist/index.js"], env={"API_KEY": "test"})
+def test_node_server(mcp):
+    assert "search" in [t["name"] for t in mcp.list_tools()]
+
+
+def test_two_versions(mcp_server):
+    old = mcp_server(["python", "server_v1.py"])
+    new = mcp_server(url="http://localhost:9000/mcp")
+    ...
+```
+
+## Schema snapshots
+
+`mcp_snapshot(mcp)` stores the tool list in `__mcp_snapshots__/<test file>/tools.json` on the
+first run and compares against it afterwards. Commit the file. When the tools change, the test
+fails and says which changes are breaking:
+
+```text
+MCP tools differ from snapshot tools.json (3 breaking, 4 compatible):
+  BREAKING add: new required parameter 'c'
+  BREAKING add: outputSchema was removed
+  BREAKING echo: tool was removed
+  ok       add: parameter 'a' type changed integer -> number
+  ...
+Run pytest --mcp-update-snapshots to accept these changes.
+```
+
+Pass `allow_compatible=True` to fail only on breaking changes.
+
+## Lint rules
+
+| Code | Level | What it catches |
+| --- | --- | --- |
+| MCP001 | error | Tool name is not 1-128 characters of `A-Z a-z 0-9 _ - .` |
+| MCP002 | error | Two tools share a name |
+| MCP003 | error | `inputSchema` missing or not `"type": "object"` |
+| MCP004 | warning | No description |
+| MCP005 | warning | Description under 20 characters |
+| MCP006 | warning | Description over 1,024 characters |
+| MCP007 | warning | Parameter has no description |
+| MCP008 | error | `required` names a parameter that isn't defined |
+| MCP009 | warning | Parameter has no type |
+| MCP010 | warning | All definitions together exceed 32,000 characters (about 8k tokens per turn) |
+| MCP011 | warning | Two names differ only by case or separators (`get_file`, `Get-File`) |
+| MCP012 | error | Text that tries to instruct the model: "ignore previous instructions", "do not tell the user", `<IMPORTANT>` blocks, reading `~/.ssh` |
+| MCP013 | error | Invisible or bidirectional control characters |
+| MCP014 | error | `outputSchema` is not `"type": "object"` |
+| MCP015 | info | Parameter description just repeats its name |
+
+Skip rules with `--ignore MCP005,MCP015` or `assert_lint_clean(mcp, ignore=["MCP005"])`.
+MCP012 is a heuristic: it catches common tool-poisoning phrasing, not every attack.
+
+## Use the client directly
+
+```python
+from mcptest import MCPClient
+
+with MCPClient.stdio(["python", "server.py"], env={"DEBUG": "1"}, timeout=10) as client:
+    print(client.server_info, client.protocol_version)
+    for tool in client.list_tools():          # follows pagination
+        print(tool["name"])
+    result = client.call_tool("search", {"q": "mcp"})
+    print(result.text, result.is_error)
+```
+
+When a server dies, mcptest shows its last stderr lines, and it points out anything printed to
+stdout that isn't protocol (the most common stdio bug):
+
+```text
+MCPTransportError: server closed stdout (exit code 3)
+  server stderr (last lines):
+    fatal: database not configured
+```
+
+## In CI
+
+```yaml
+- run: pip install pytest-mcp-server
+- run: mcptest lint --fail-on warning -- python -m my_server
+- run: mcptest diff mcp-tools.json -- python -m my_server
+```
+
+## Tested against real servers
+
+Checked on 2026-11-06 with mcptest 0.1.0: connect, list tools, call a tool, snapshot twice.
+
+| Server | Transport | Tools | Tool call | Lint findings |
+| --- | --- | --- | --- | --- |
+| @modelcontextprotocol/server-everything | stdio, Streamable HTTP | 14 | ok | 1 warning |
+| @modelcontextprotocol/server-filesystem | stdio | 14 | ok | 18 warnings |
+| @modelcontextprotocol/server-memory | stdio | 9 | ok | 4 warnings |
+| @modelcontextprotocol/server-sequential-thinking | stdio | 1 | ok | 1 warning |
+| @playwright/mcp | stdio, Streamable HTTP | 25 | returned as a tool error (no browser in the test machine) | 3 warnings |
+| mcp-server-time | stdio | 3 | ok | none |
+| mcp-server-git | stdio | 14 | ok | 24 warnings |
+| mcp-server-fetch | stdio | 1 | not called (needs network) | none |
+| Official Python SDK 2.3 (`MCPServer`) | stdio, Streamable HTTP | 2 | ok | 3 warnings |
+
+Almost all warnings are parameters with no description (MCP007) or very short descriptions (MCP005).
+
+## Limits
+
+- Covers tools fully, resources and prompts through the client only (no lint rules for them yet).
+- No OAuth flow: for protected HTTP servers, pass a token with `--header` or `headers=`.
+- The legacy HTTP+SSE transport (two endpoints) is not supported; Streamable HTTP and stdio are.
+
+## License
+
+MIT

pytest_mcp_server-0.1.0/pyproject.toml

@@ -0,0 +1,46 @@
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[project]
+name = "pytest-mcp-server"
+version = "0.1.0"
+description = "Automated tests, linting and breaking-change checks for MCP servers, as a pytest plugin and CLI"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.9"
+authors = [{ name = "Sri Krishna Lingamaneni" }]
+keywords = ["mcp", "model context protocol", "pytest", "testing", "lint", "ai agents", "llm", "ci"]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Framework :: Pytest",
+  "Intended Audience :: Developers",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Topic :: Software Development :: Testing",
+  "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+dependencies = []
+
+[project.optional-dependencies]
+test = ["pytest>=7"]
+
+[project.urls]
+Homepage = "https://github.com/srikrishnaL/kitforge/tree/main/packages/mcptest"
+Source = "https://github.com/srikrishnaL/kitforge"
+Issues = "https://github.com/srikrishnaL/kitforge/issues"
+Changelog = "https://github.com/srikrishnaL/kitforge/blob/main/packages/mcptest/CHANGELOG.md"
+
+[project.scripts]
+mcptest = "mcptest.cli:main"
+
+[project.entry-points.pytest11]
+mcptest = "mcptest.plugin"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/mcptest"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

pytest_mcp_server-0.1.0/src/mcptest/__init__.py

@@ -0,0 +1,45 @@
+"""mcptest: automated tests and CI checks for MCP servers."""
+
+from __future__ import annotations
+
+from typing import Any, Iterable
+
+from .client import (
+    MCPClient,
+    MCPError,
+    MCPTimeout,
+    MCPTransportError,
+    ToolResult,
+)
+from .lint import RULES, Finding, at_or_above, lint_tools
+from .snapshot import Change, diff, normalize
+
+__version__ = "0.1.0"
+
+__all__ = [
+    "MCPClient",
+    "MCPError",
+    "MCPTimeout",
+    "MCPTransportError",
+    "ToolResult",
+    "Finding",
+    "RULES",
+    "lint_tools",
+    "assert_lint_clean",
+    "Change",
+    "diff",
+    "normalize",
+    "__version__",
+]
+
+
+def assert_lint_clean(source: Any, *, fail_on: str = "warning", ignore: Iterable[str] = ()) -> None:
+    """Raise ``AssertionError`` if the tools have findings at ``fail_on`` or worse.
+
+    ``source`` is an :class:`MCPClient` or a ``tools/list`` result.
+    """
+    tools = source.list_tools() if isinstance(source, MCPClient) else source
+    findings = at_or_above(lint_tools(tools, ignore=ignore), fail_on)
+    if findings:
+        body = "\n  ".join(str(f) for f in findings)
+        raise AssertionError(f"{len(findings)} MCP lint finding(s):\n  {body}")

pytest_mcp_server-0.1.0/src/mcptest/__main__.py

@@ -0,0 +1,5 @@
+import sys
+
+from .cli import main
+
+sys.exit(main())