The author of this package has not provided a project description
Metadata
Release files for tocson-mcp-server 0.1.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 | |
|---|---|---|---|---|
| tocson_mcp_server-0.1.1.tar.gz | 16.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tocson_mcp_server-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.1 kB
Release files / tocson_mcp_server-0.1.1.tar.gz
| Download URL | tocson_mcp_server-0.1.1.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e83ee7f3aedad6258ff51b02f7af18e292fb9cb5f4ea2f1755ea1324314cfa7
|
|
BLAKE2b-256 checksum How to use checksums |
8c17f7d861547ec783b0777cab5a5ef21b29cb897819ffab31f14e862b6500e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.20
|
Release files / tocson_mcp_server-0.1.1-py3-none-any.whl
| Download URL | tocson_mcp_server-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45b32c83c1dfe0a192a3d86e9dff86ddfe1455bbf1a42278259dd79ab1cc9d7b
|
|
BLAKE2b-256 checksum How to use checksums |
70c1c14b9717b5767cfa7c89756c08e4dd735e36f3e8b07fb4b3c8935e5c00be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.20
|
Security for tocson-mcp-server 0.1.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.