The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for opera-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 | |
|---|---|---|---|---|
| opera_mcp-0.1.1.tar.gz | 13.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opera_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.0 kB
Release files / opera_mcp-0.1.1.tar.gz
| Download URL | opera_mcp-0.1.1.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ca195119d11c8d0ae018c1e60213cb644b3363c1e0d22ee78b240482fcb8fc4
|
|
BLAKE2b-256 checksum How to use checksums |
19b6b0443d8fa5f5002476b4051000360e618e285b561d4b6a7e11834ad5a6a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Release files / opera_mcp-0.1.1-py3-none-any.whl
| Download URL | opera_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a205b6bdc21a3aef19e7e53e38807bf83d8e061a0b9a89c34791e816b911d381
|
|
BLAKE2b-256 checksum How to use checksums |
ef2cd3a514ddbf1a0946418bf4fc68d608dd08c105444d579ab38bc8e62b86c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Security for opera-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.
