The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for a4a-mcp 0.3.3
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.3.3.tar.gz | 318.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| a4a_mcp-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 438.4 kB
Release files / a4a_mcp-0.3.3.tar.gz
| Download URL | a4a_mcp-0.3.3.tar.gz |
|---|---|
| Size | 318.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d55853c290a1e4149726aae162ba6cd52194473483852c8f2c50074a22a7857f
|
|
BLAKE2b-256 checksum How to use checksums |
846ffe1adb24ba278758bb8436a89b5ca36ce4b3c94db2f058969199300527de
|
| 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.3.3-py3-none-any.whl
| Download URL | a4a_mcp-0.3.3-py3-none-any.whl |
|---|---|
| Size | 120.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72d2a1ac4d276b7ce01ca2434de8d8c1f7b6d3e63b89350b99ddfebaed7d40c5
|
|
BLAKE2b-256 checksum How to use checksums |
798f6edb9feca80052916866fa6d0c6515e1a7cf53d18c2638726e80508dd1ce
|
| 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.3.3
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.
