The author of this package has not provided a project description
Metadata
Release files for store-mcp-py 0.3.1
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.3.1.tar.gz | 11.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| store_mcp_py-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / store_mcp_py-0.3.1.tar.gz
| Download URL | store_mcp_py-0.3.1.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9847d120d8eefe6d3b786fdaab3a14f3b6a0ef582aa11e0734be351043471dc
|
|
BLAKE2b-256 checksum How to use checksums |
66af6ee35fc99befd5348f334f910378490d66391ce45375d911d1cf49559394
|
| 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.3.1-py3-none-any.whl
| Download URL | store_mcp_py-0.3.1-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3677fff86ebd95f539cfb87ca6c6013bd500146920b00422baeeebb6173069bd
|
|
BLAKE2b-256 checksum How to use checksums |
921a00710b3749b9f566d246a685bfdbfe3bbea93ada4f7a47f39da71bc62baf
|
| 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.3.1
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.