Metadata
Release files for ai4h-mcp-server 0.0.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 | |
|---|---|---|---|---|
| ai4h_mcp_server-0.0.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai4h_mcp_server-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / ai4h_mcp_server-0.0.1.tar.gz
| Download URL | ai4h_mcp_server-0.0.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5fe5ad1a2602ebd898e0cc72062e512944d4f19f8c0e149649e58ccba8476882
|
|
BLAKE2b-256 checksum How to use checksums |
e0c512dc9c92a23f96be71a821ca574aa902166707ffdb8455125437171c2c9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / ai4h_mcp_server-0.0.1-py3-none-any.whl
| Download URL | ai4h_mcp_server-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b57270d739afc5dc313ad0104d931834d49314beb41a8109f6d40b67ead454e7
|
|
BLAKE2b-256 checksum How to use checksums |
623317990bf5426251ae57b54bb242f0b7884454bf4ba85ce5d13147340eb13c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for ai4h-mcp-server 0.0.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.