
Pytest Deprecation Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Oct 24, 2026
Marks the lines in your test suite that current pytest no longer runs — and the config keys it silen
Overview
A local MCP server that flags test-suite lines current pytest no longer runs and the config keys that silence them.
- What you can do
- Pytest Deprecation Lint is a local stdio MCP server distributed as the npm package @readystack/pytest-deprecation-lint and started with npx. Its stated purpose is to mark the lines in a test suite that current pytest no longer runs, along with the configuration keys that silence those warnings. The manifest lists no tools, so the exact operations exposed to an assistant are not documented here.
- When to use it
- Worth considering when you maintain a pytest test suite and want an assistant to help find tests or lines that newer pytest versions skip, plus the config keys hiding those warnings. It is a narrow linting aid rather than a general test runner.
- Requirements
- Runs as a local process on the user's machine over stdio, started with npx from the npm package @readystack/pytest-deprecation-lint. Node.js and npx are therefore needed. No authentication, environment variables, or headers are declared. Desktop only; no web executable.
Installation
In SourceWeft
- Open Pytest Deprecation Lint in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
2- v1.0.2LatestSep 19, 2026
- v1.0.1Sep 18, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
