The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for toot-mcp 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 | |
|---|---|---|---|---|
| toot_mcp-0.1.1.tar.gz | 12.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| toot_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.4 kB
Release files / toot_mcp-0.1.1.tar.gz
| Download URL | toot_mcp-0.1.1.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de04005205f4af54ff795a402346e293c72aba13d8c704db5fecd9f17012cbf4
|
|
BLAKE2b-256 checksum How to use checksums |
23d83bd27610b6fc3d6add975cbbb790e0f5bf9c96c6c1bdb64ab1142c6c380f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Release files / toot_mcp-0.1.1-py3-none-any.whl
| Download URL | toot_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e2220a072187b916d81953cb7c4e3e0e183c521288a7633d5ae0e4195c519df
|
|
BLAKE2b-256 checksum How to use checksums |
8531ff7f084dd8878f2df9121c6ee082ac9b7da238c40d8f81b41d92c1d3dcdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Security for toot-mcp 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.
