The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mcp-sse 0.3.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 | |
|---|---|---|---|---|
| mcp_sse-0.3.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_sse-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.0 kB
Release files / mcp_sse-0.3.0.tar.gz
| Download URL | mcp_sse-0.3.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
803c0d3734118ff11c418760b20a668d30a019fbec71ffcafb12b868ee27e7f9
|
|
BLAKE2b-256 checksum How to use checksums |
add4b49b52b68b9369a4dd2569eb4b8705995969e9c6c6a391c182b38efd4de5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.1
|
Release files / mcp_sse-0.3.0-py3-none-any.whl
| Download URL | mcp_sse-0.3.0-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee4884d9008f10b5b37eb3150a396da4a84173c3f6bf7d3cc978db261102204c
|
|
BLAKE2b-256 checksum How to use checksums |
e124794da0c382fb1160499fe1b4728706f1f34ee409dc5bd24bb5b5e0387e01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.1
|
Security for mcp-sse 0.3.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.
