django-chainsaw-mcp

Purpose: Finding hidden Django project risks such as N+1 queries, unsafe migrations, tenant leaks, and transaction side effects.

Inferred · not functionally tested

Audience: Django developers and code reviewers

Inferred · not functionally tested

Functions: analytics, monitoring

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

In the Static analysis & linters space, django-chainsaw-mcp takes a focused approach. Inferred · not functionally tested: It focuses on finding hidden Django project risks such as N+1 queries, unsafe migrations, tenant leaks, and transaction side effects. Inferred · not functionally tested: It is built as an open-source project for django developers and code reviewers. Basis unknown · not verified: django-chainsaw-mcp is open source under the MIT license. Basis unknown · not verified: It ships for the command line, and it can be self-hosted.

syrian963 builds and maintains django-chainsaw-mcp, and it first shipped in 2026. The project is developed in the open on GitHub with 86 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include cascade analysis, N+1 detection, and migration safety checks. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.