The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mcp-colab-gpu 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 | |
|---|---|---|---|---|
| mcp_colab_gpu-0.3.1.tar.gz | 181.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_colab_gpu-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 203.8 kB
Release files / mcp_colab_gpu-0.3.1.tar.gz
| Download URL | mcp_colab_gpu-0.3.1.tar.gz |
|---|---|
| Size | 181.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88a271b3bf1c370118fafe24ef9577f67996da2dac81fd687a85c4ab1f24def8
|
|
BLAKE2b-256 checksum How to use checksums |
af38727e83814662a7a7dbe64f56dbf050bed85f4ef870786de80acc361b6679
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.7
|
Release files / mcp_colab_gpu-0.3.1-py3-none-any.whl
| Download URL | mcp_colab_gpu-0.3.1-py3-none-any.whl |
|---|---|
| Size | 22.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e9d51881a14bf391a1a409de1257cce1ec5f49c5bf9c72381c8b47ce28a5e02
|
|
BLAKE2b-256 checksum How to use checksums |
4a4fff04ddf3192d0db1a15039cd84b08103b07b0449a5ba17e16523982c8095
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.7
|
Security for mcp-colab-gpu 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.
