The author of this package has not provided a project description
Metadata
Release files for store-mcp-py 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| store_mcp_py-0.2.0.tar.gz | 11.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| store_mcp_py-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / store_mcp_py-0.2.0.tar.gz
| Download URL | store_mcp_py-0.2.0.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebaf5160475d23282148a2042b6ea6a1fa9c58f9d40ccebb1a7e1e07df530acd
|
|
BLAKE2b-256 checksum How to use checksums |
8d24fdf5545baaa1661e0e4b43e56788af9e7df23776da0b6669ab37fa060055
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / store_mcp_py-0.2.0-py3-none-any.whl
| Download URL | store_mcp_py-0.2.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1d9219b8a8f49cf28aef7c5bc5c3cb0b260449c231aea3ce0078566e1ad6a70
|
|
BLAKE2b-256 checksum How to use checksums |
60e2913f62e5bad14fe6ada06ee7b18be8a21306520f68f991b5d9059deaf0e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for store-mcp-py 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.