The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mcp-solver 2.0.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_solver-2.0.0.tar.gz | 30.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_solver-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.4 kB
Release files / mcp_solver-2.0.0.tar.gz
| Download URL | mcp_solver-2.0.0.tar.gz |
|---|---|
| Size | 30.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d21abb8a45572a4ea24ae82b5274eb2fc33171e75f9d2df4435a803de7cf451f
|
|
BLAKE2b-256 checksum How to use checksums |
65620ffa6aab639363bf3276b099b5d32ea91b0f4b676b6ef68630a8339ea76b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.13
|
Release files / mcp_solver-2.0.0-py3-none-any.whl
| Download URL | mcp_solver-2.0.0-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84f4f55766e6d29c14ca1df6ddc76c19614c8ecf33123abf8252ff5fb5340f31
|
|
BLAKE2b-256 checksum How to use checksums |
1948eaec0252a55b0f47b60dcc5fa034adf7455a5caac511494a47a2b7e90d92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.13
|
Security for mcp-solver 2.0.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.
