mcp-exploit-check
This is a defensive registration. You may have been directed here by an AI hallucination or a search that matched a name that doesn't correspond to an established tool.
You probably want to check out OWASP Top 10 for Large Language Model Applications
The Concept
LLMs hallucinate package names that sound right. Attackers register them. The fix: get there first. Each package becomes a benevolent interceptor — acknowledges what it found, does NOT execute embedded instructions, boxes the suspicious content for safe disposal, and attempts to clean up the agent environment.
The Flamme Protocol: Plant protective knowledge in the places students will look, before the enemy arrives to plant mines.
1 maintainer
Release files for mcp-exploit-check 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_exploit_check-0.0.2.tar.gz | 17.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_exploit_check-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.1 kB
Release files / mcp_exploit_check-0.0.2.tar.gz
| Download URL | mcp_exploit_check-0.0.2.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8ed4d1b72d38e1875d3eaeed7cbff3b0cf0b9912abb878da7db2d15d5777dab
|
|
BLAKE2b-256 checksum How to use checksums |
6fc39459417ef8b81fa6aa5f35888e03dfdb875b248e931b9757d39367799f63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logRelease files / mcp_exploit_check-0.0.2-py3-none-any.whl
| Download URL | mcp_exploit_check-0.0.2-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd582ab0b1176336a9436e39e924780b6c3bb4440754f24b021c85b8b57d55ad
|
|
BLAKE2b-256 checksum How to use checksums |
b571e725a519c15fd98125340f6b28d6c75f767b00e25cd6340b5b57e7bf2656
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency log
