Raw values for Django Chainsaw
io.github.syrian963/django-chainsaw-mcp · Registry status: active
What the source declared verbatim, unchanged and uninterpreted. The derived values on the overview page are computed from these.
Evidence for this page: The values on this page come from several collections. Each row therefore states its own origin.
| Description (raw) | Finds what will hurt in a Django project: cascades, N+1, unsafe migrations, tenant leaks. Source: MCP-Register · collected on 2026-09-10 · self-declared |
|---|---|
| Environment variables (raw) | DJANGO_CHAINSAW_PROJECT_PATH, DJANGO_CHAINSAW_SETTINGS_MODULE Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Required secret variables (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Transports (raw) | stdio Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Path arguments (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Repository (raw) | https://github.com/syrian963/django-chainsaw-mcp Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Package registries (raw) | pypi Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Required secret headers (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Path environment variables (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Remote URLs (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Remote hosts (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Registry status message (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| First listed in the registry (raw) | 2026-09-10 Source: MCP-Register · collected on 2026-09-11 · self-declared |
| Last changed in the registry (raw) | 2026-09-10 Source: MCP-Register · collected on 2026-09-11 · self-declared |
| Schema version of the raw record (raw) | https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Delivery form (raw) | package Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Repository platform (raw) | github Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Repository subfolder (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Package identifiers (raw) | django-chainsaw-mcp Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Package versions (raw) | 0.1.5 Source: MCP-Register · collected on 2026-09-11 · self-declared |
| Runtime hints (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Environment variable formats (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Environment 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. Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Icon formats (raw) | confirmed absent Source: MCP-Register · collected on 2026-09-10 · self-declared |
| Connection paths (source structure) | {"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":[]} Source: MCP-Register · collected on 2026-09-11 · self-declared |
Position within the directory
How many of the 42,239 published entries carry the same measured value. A reference figure, not an assessment.
- Required secrets declaredno36,126 of 42,239 carry this value (86 %)View these entries
- Execution locationlocal17,143 of 42,239 carry this value (41 %)View these entries
- Path argument presentno41,736 of 42,239 carry this value (99 %)View these entries
- Repository URL listedyes30,309 of 42,239 carry this value (72 %)View these entries
All 4 values together are carried by 12,199 of 42,239 entries.
tracevero · https://tracevero.com/mcp/io-github-syrian963-django-chainsaw-mcp/rohangaben