Deepsleuth
PYPI · SECURITY-SCANNER-DEEPSLEUTH-MCP
Deterministic, no-LLM security scanner for MCP servers, plus an inline proxy gate.
Available components
Last scanned (14 hours ago)
Scores higher than 68% of PyPI servers
Category Security
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 (Apache-2.0).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 238 tokens (~79/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 15 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Oct 26 25
First indexed and scored.
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 18 Oct 2026 · Analysed pypi/security-scanner-deepsleuth-mcp@1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_listing ~97
Analyze a supplied MCP tool listing with the listing-phase detectors (description/schema poisoning, shadowing, obfuscation, ...) WITHOUT launching the server. Pass another server's tools/list output.
| Name | Type | Req | Description |
|---|---|---|---|
| server_name | string | – | Label for the supplied listing (default: 'supplied-listing'). |
| tools_json | string | yes | A JSON array of tool entries ({name, description, inputSchema}), or an object with a 'tools' key. |
No output schema declared.
No examples provided.
list_detectors ~34
List every detector in the deepsleuth registry: id, category, evidence location, phase, and required capability layers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_target ~107
Scan an MCP server target with the full detection core: source analysis, package manifests, and (optionally, dynamic=True) live execution inside the Docker sandbox. Returns the findings.
| Name | Type | Req | Description |
|---|---|---|---|
| dynamic | boolean | – | Also run the dynamic layer (Docker sandbox required; the target always runs sandboxed). Default: false. |
| target | string | yes | Server directory, mcp.json path, or raw stdio launch command. |
| timeout | integer | – | Per-call timeout seconds (default 30). |
No output schema declared.
No examples provided.
How do I install the Deepsleuth MCP server?
Deepsleuth runs locally as a PyPI package, launched with uvx security-scanner-deepsleuth-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · security-scanner-deepsleuth-mcp
claude mcp add deepsleuth-deepsleuth -- uvx security-scanner-deepsleuth-mcp
What is the Deepsleuth MCP server?
Deepsleuth is an MCP server listed in the public MCP registry as io.github.DeepSleuth/deepsleuth. Deterministic, no-LLM security scanner for MCP servers, plus an inline proxy gate. This page covers its PyPI package (security-scanner-deepsleuth-mcp).
Is the Deepsleuth MCP server safe to use?
Deepsleuth scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 Deepsleuth MCP server expose?
Deepsleuth exposes 3 tools: list_detectors, check_listing, scan_target. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.
Is the Deepsleuth MCP server still maintained?
Deepsleuth is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Deepsleuth MCP server under?
Deepsleuth declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.