The author of this package has not provided a project description
Metadata
Release files for store-mcp-py 0.3.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.3.0.tar.gz | 11.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| store_mcp_py-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.5 kB
Release files / store_mcp_py-0.3.0.tar.gz
| Download URL | store_mcp_py-0.3.0.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8fc4de8d58550243530d93b02d8448bfc170c5393aac0a2ff20730b11369aee
|
|
BLAKE2b-256 checksum How to use checksums |
57dacbb754b38fd477f2cf3449f54ed7069196ccae799efca01893516a4976ce
|
| 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.0-py3-none-any.whl
| Download URL | store_mcp_py-0.3.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c806cd3ee917ac0e8413be8af931a8de61eb6b372d39d8111dab604930ddbe2
|
|
BLAKE2b-256 checksum How to use checksums |
cf8cf6fd37affc633ff1f601098bd860f84a9fb9d707964e39f6de553cc7a9b7
|
| 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.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.