The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tobe-time-mcp 0.1.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 | |
|---|---|---|---|---|
| tobe_time_mcp-0.1.0.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tobe_time_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 kB
Release files / tobe_time_mcp-0.1.0.tar.gz
| Download URL | tobe_time_mcp-0.1.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc41819c78bc4837c5b788370c727b32b043e0041edb07f08fd9bb94b16c70ce
|
|
BLAKE2b-256 checksum How to use checksums |
24e162731b5a7ec24bdeaa5d2ecccb8a9f66c1c04e76a4c741ab2899effb07b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Release files / tobe_time_mcp-0.1.0-py3-none-any.whl
| Download URL | tobe_time_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fac462d0bb6572d9bc716acc3e2b88446c9aab4bde7a4ad8ce9d9f845621d4ba
|
|
BLAKE2b-256 checksum How to use checksums |
c7a23276a4a429056599c5430732c5e3349b7ad26d338d01154639995aea502f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Security for tobe-time-mcp 0.1.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.
