Skip to content

History of Django Chainsaw

io.github.syrian963/django-chainsaw-mcp · Registry status: active

Report data on this entry

Every published change to this entry, most recent first.

Changes
2026-09-11Declared version: 0.1.4 → 0.1.5
2026-09-11Last changed in the registry (raw): 2026-09-09 → 2026-09-10
2026-09-11First listed in the registry (raw): 2026-09-09 → 2026-09-10
2026-09-11Connection paths (source structure): {"packages":[{"registryType":"pypi","identifier":"django-chainsaw-mcp","version":"0.1.4","transport":"stdio","environment":[{"name":"DJANGO_CHAINSAW_PROJECT_PATH","description":"Absolute path to the Django project to analyse - the directory containing manage.py, or whichever directory the settings module is importable from. This server must run in an interpreter that can import that project, so install it into the project's own environment rather than an isolated one.","required":true,"secret":false},{"name":"DJANGO_CHAINSAW_SETTINGS_MODULE","description":"Dotted path to the settings module, for example myproject.settings. Point it at the settings the site actually runs on: a base or partial module can import cleanly and load no models, and the server says so when that happens.","required":true,"secret":false}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"pypi","identifier":"django-chainsaw-mcp","version":"0.1.5","transport":"stdio","environment":[{"name":"DJANGO_CHAINSAW_PROJECT_PATH","description":"Absolute path to the Django project to analyse - the directory containing manage.py, or whichever directory the settings module is importable from. This server must run in an interpreter that can import that project, so install it into the project's own environment rather than an isolated one.","required":true,"secret":false},{"name":"DJANGO_CHAINSAW_SETTINGS_MODULE","description":"Dotted path to the settings module, for example myproject.settings. Point it at the settings the site actually runs on: a base or partial module can import cleanly and load no models, and the server says so when that happens.","required":true,"secret":false}],"additional_arguments_declared":false}],"remotes":[]}
2026-09-11Package versions (raw): 0.1.4 → 0.1.5
2026-09-10Declared version: – → 0.1.4
2026-09-10Repository URL listed: – → yes
2026-09-10Path argument present: – → no
2026-09-10Execution location: – → local
2026-09-10Required secrets declared: – → no
2026-09-10Description (raw): – → Finds what will hurt in a Django project: cascades, N+1, unsafe migrations, tenant leaks.
2026-09-10Last changed in the registry (raw): – → 2026-09-09
2026-09-10First listed in the registry (raw): – → 2026-09-09
2026-09-10Registry status message (raw): – → –
2026-09-10Schema version of the raw record (raw): – → https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json
2026-09-10Icon formats (raw): – → –
2026-09-10Environment variable descriptions (raw): – → DJANGO_CHAINSAW_PROJECT_PATH=Absolute path to the Django project to analyse - the directory containing manage.py, or whichever directory the settings module is importable from. This server must run in an interpreter that can import that project, so install it into the project's own environment rather than an isolated one. · DJANGO_CHAINSAW_SETTINGS_MODULE=Dotted path to the settings module, for example myproject.settings. Point it at the settings the site actually runs on: a base or partial module can import cleanly and load no models, and the server says so when that happens.
2026-09-10Environment variable formats (raw): – → –
2026-09-10Delivery form (raw): – → package
2026-09-10Remote hosts (raw): – → –
2026-09-10Connection paths (source structure): – → {"packages":[{"registryType":"pypi","identifier":"django-chainsaw-mcp","version":"0.1.4","transport":"stdio","environment":[{"name":"DJANGO_CHAINSAW_PROJECT_PATH","description":"Absolute path to the Django project to analyse - the directory containing manage.py, or whichever directory the settings module is importable from. This server must run in an interpreter that can import that project, so install it into the project's own environment rather than an isolated one.","required":true,"secret":false},{"name":"DJANGO_CHAINSAW_SETTINGS_MODULE","description":"Dotted path to the settings module, for example myproject.settings. Point it at the settings the site actually runs on: a base or partial module can import cleanly and load no models, and the server says so when that happens.","required":true,"secret":false}],"additional_arguments_declared":false}],"remotes":[]}
2026-09-10Remote URLs (raw): – → –
2026-09-10Runtime hints (raw): – → –
2026-09-10Package versions (raw): – → 0.1.4
2026-09-10Package identifiers (raw): – → django-chainsaw-mcp
2026-09-10Package registries (raw): – → pypi
2026-09-10Repository subfolder (raw): – → –
2026-09-10Repository platform (raw): – → github
2026-09-10Repository (raw): – → https://github.com/syrian963/django-chainsaw-mcp
2026-09-10Path environment variables (raw): – → –
2026-09-10Path arguments (raw): – → –
2026-09-10Transports (raw): – → stdio
2026-09-10Required secret headers (raw): – → –
2026-09-10Required secret variables (raw): – → –
2026-09-10Environment variables (raw): – → DJANGO_CHAINSAW_PROJECT_PATH, DJANGO_CHAINSAW_SETTINGS_MODULE

tracevero · https://tracevero.com/mcp/io-github-syrian963-django-chainsaw-mcp/aenderungen