The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for refinex-mcp 0.1.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 | |
|---|---|---|---|---|
| refinex_mcp-0.1.0.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| refinex_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.9 kB
Release files / refinex_mcp-0.1.0.tar.gz
| Download URL | refinex_mcp-0.1.0.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e21a57c18f01cd26c1c4fe96882b69ca6c1833fe819d671e9d5d6cd301df57a7
|
|
BLAKE2b-256 checksum How to use checksums |
20ba82b7f785f08aaed7fe5d192ba9bb13c0928a7221efd2c0ffe1fe9d6bcad2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / refinex_mcp-0.1.0-py3-none-any.whl
| Download URL | refinex_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b775a31d5cf4796c319373468e0aaaba733d9945e3609cb9d3e036f783eef46e
|
|
BLAKE2b-256 checksum How to use checksums |
f0045b1077fa51efe2f0b47fbd20440af380e989bf081378dfbc55e44fb2b4ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for refinex-mcp 0.1.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.
