io.github.notasandy/mcp-code-sanitizer
PYPI · MCP-CODE-SANITIZER · SCANNED SEP 20
Strict AI code reviewer powered by Groq. Finds bugs and vulnerabilities.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 127 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 521 tokens (~74/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.notasandy/mcp-code-sanitizer server?
io.github.notasandy/mcp-code-sanitizer runs locally as a PyPI package, launched with uvx mcp-code-sanitizer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-code-sanitizer
claude mcp add notasandy-mcp-code-sanitizer -- uvx mcp-code-sanitizer
{
"mcpServers": {
"notasandy-mcp-code-sanitizer": {
"command": "uvx",
"args": [
"mcp-code-sanitizer"
]
}
}
} {
"servers": {
"notasandy-mcp-code-sanitizer": {
"command": "uvx",
"args": [
"mcp-code-sanitizer"
]
}
}
} codex mcp add notasandy-mcp-code-sanitizer -- uvx mcp-code-sanitizer
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"notasandy-mcp-code-sanitizer": {
"type": "local",
"command": [
"uvx",
"mcp-code-sanitizer"
],
"enabled": true
}
}
} openclaw mcp add notasandy-mcp-code-sanitizer --command uvx --arg mcp-code-sanitizer
mcp_servers:
notasandy-mcp-code-sanitizer:
command: "uvx"
args: ["mcp-code-sanitizer"] {
"McpServers": {
"notasandy-mcp-code-sanitizer": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-code-sanitizer"
]
}
}
} assistant mcp add notasandy-mcp-code-sanitizer -t stdio -c uvx -a mcp-code-sanitizer
{
"mcpServers": {
"notasandy-mcp-code-sanitizer": {
"command": "uvx",
"args": [
"mcp-code-sanitizer"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcp-code-sanitizer@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_code Analyze Code ~80
Строгий анализ фрагмента кода через Groq LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Фрагмент кода для проверки. |
| context | string | – | Необязательное описание — что делает код, откуда взят. |
| language | string | – | Язык программирования (python, javascript, go, rust, …). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
analyze_file Analyze File ~96
Анализирует целый файл с кодом на диске. Автоматически определяет язык по расширению. Большие файлы разбиваются на чанки и анализируются параллельно.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Описание что делает файл (необязательно). |
| file_path | string | yes | Абсолютный путь к файлу. |
| language | string | – | Язык (если не задан — определяется по расширению). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cache_info Cache Info ~40
Показывает статистику кэша или очищает его.
| Name | Type | Req | Description |
|---|---|---|---|
| clear | boolean | – | True — очищает кэш, False — показывает статистику. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compare_code Compare Code ~76
Сравнивает две версии кода и оценивает качество изменений.
| Name | Type | Req | Description |
|---|---|---|---|
| code_after | string | yes | Новая версия кода. |
| code_before | string | yes | Старая версия кода. |
| context | string | – | Описание что и зачем изменялось. |
| language | string | – | Язык программирования. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
explain_code Explain Code ~61
Объясняет что делает код — пошагово и понятно.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Уровень аудитории — junior, middle или senior. |
| code | string | yes | Код для объяснения. |
| language | string | – | Язык программирования. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_report Generate Report ~81
Генерирует красивый HTML-отчёт из результата analyze_code / analyze_file.
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_json | string | yes | JSON-строка из analyze_code или analyze_file. |
| output_path | string | – | Путь для сохранения HTML (необязательно). |
| source_name | string | – | Название файла/фрагмента для заголовка. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
generate_tests Generate Tests ~66
Генерирует тесты для переданного кода.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Код для тестирования. |
| framework | string | – | Фреймворк (опционально — pytest, jest, unittest и т.д.). |
| language | string | – | Язык программирования. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.notasandy/mcp-code-sanitizer server?
io.github.notasandy/mcp-code-sanitizer is listed in the public MCP registry as io.github.notasandy/mcp-code-sanitizer. Strict AI code reviewer powered by Groq. Finds bugs and vulnerabilities. This page covers its PyPI package (mcp-code-sanitizer).
Is the io.github.notasandy/mcp-code-sanitizer server safe to use?
io.github.notasandy/mcp-code-sanitizer scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.notasandy/mcp-code-sanitizer server expose?
io.github.notasandy/mcp-code-sanitizer exposes 7 tools: analyze_code, compare_code, explain_code, generate_tests, analyze_file, and 2 more. Their descriptions and schemas cost roughly 500 tokens of context every time the server is loaded.
Is the io.github.notasandy/mcp-code-sanitizer server still maintained?
io.github.notasandy/mcp-code-sanitizer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.notasandy/mcp-code-sanitizer server under?
io.github.notasandy/mcp-code-sanitizer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.