[smusali]

Project

• checkowners
• mcp4api
• mcp-cross-exam

Checklist

• I read CONTRIBUTING.md - awesome-python is a shortlist, not a catalog
• One project per PR
• PR title format: Add project-name
• Entry format: - [pypi-name](https://github.com/owner/repo) - Description ending with period.
• Display name is the PyPI package name
• Placed in an existing use case (new sections and subcategories are maintainer-only)
• Meets all Quality Requirements: active, stable, documented, at least 1 month old

Which Tier

Pick one:

• Obvious choice - a tool an experienced Python developer would name when asked "what do I use for this?"
• Challenger - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.

Explain: Maintainer override adds three related tools in one change. checkowners fills the open Code Analysis → General slot (git-history ownership and CODEOWNERS drift). mcp4api sits under Model Context Protocol after fastmcp (OpenAPI to MCP, then live tool verification). mcp-cross-exam sits under Testing → API Testing after schemathesis (schema and behavior audit for MCP servers). mcp4api and mcp-cross-exam are still young and Alpha on PyPI; age and stability are intentionally waived here.

flowchart LR
  README --> Gen[Code Analysis General]
  README --> Mcp[Model Context Protocol]
  README --> Api[API Testing]
  Gen --> A[checkowners]
  Mcp --> B[mcp4api]
  Api --> C[mcp-cross-exam]

Loading

Displacement

Not applicable. Code Analysis → General was 4 of 5, Model Context Protocol was 2 of 5, and API Testing was 1 of 5.

Local check

1. Open README.md and confirm each line sits in the section above, with PyPI display names and a trailing period.
2. make preview, then open http://127.0.0.1:8000 and confirm the three entries render on their category pages.