The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for a4a-mcp 0.4.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 | |
|---|---|---|---|---|
| a4a_mcp-0.4.0.tar.gz | 320.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| a4a_mcp-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 442.9 kB
Release files / a4a_mcp-0.4.0.tar.gz
| Download URL | a4a_mcp-0.4.0.tar.gz |
|---|---|
| Size | 320.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1689567d3b3ca75cd051e69672eacecd74c1c396934f120c7359d176ba1683b
|
|
BLAKE2b-256 checksum How to use checksums |
3bbcef13a2a68088af0b922a85ddc576549cf0915d6d72ba0f38f2e2e41ba462
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Release files / a4a_mcp-0.4.0-py3-none-any.whl
| Download URL | a4a_mcp-0.4.0-py3-none-any.whl |
|---|---|
| Size | 122.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2cfe7ecc69f08209d8443bac220f8cb43854d8b854b3c4acdedc77ec8026985
|
|
BLAKE2b-256 checksum How to use checksums |
a614cbb33504ffe10a40071666a66eaa40a4f687970b630c5e62142b69fee8f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Security for a4a-mcp 0.4.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.
