cam-verdict (Python)
mcp-name: io.github.kau17033/cam-product-viability-standard
The CAM — Product Viability Standard as a Python package. Given a product's price and all six cost items (product cost, shipping, marketplace fee, return reserve, other variable cost), it returns a deterministic verdict:
TEST_CANDIDATE— profit clears the target and every check passesHOLD— profit is positive but a check fails, or inputs are incompleteREJECT— profit is zero or negative
Report form: CAM verdict: TEST_CANDIDATE — profit ¥5,920 per order
New in 1.1.0: input enters through the translator
(cam_verdict.translate) — loose English/Japanese field names and string
numbers are canonized into the six items before judging, and missing items
are never guessed. The package also ships an MCP (stdio) server,
cam-verdict-mcp, exposing the same cam_verdict tool as the npm package.
Standard, worked examples, benchmark and verification record: https://kau17033.github.io/cam-product-viability-standard/
1 maintainer
Metadata
1 maintainer
Release files for cam-verdict 1.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 | Actions |
|---|---|---|---|---|
| cam_verdict-1.1.1.tar.gz | 9.6 kB | With provenance | Details for cam_verdict-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cam_verdict-1.1.1-py3-none-any.whl | Python 3 | none | any | Details for cam_verdict-1.1.1-py3-none-any.whl |
Total release size: 19.5 kB
Release files / cam_verdict-1.1.1.tar.gz
| Download URL | cam_verdict-1.1.1.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03b026814f57d6f5325b049428ed18666c60d3e4b06848ed565c14e6ff9ea5ce
|
|
BLAKE2b-256 checksum How to use checksums |
9c44794678d015def6557e8639c92fa72f6f29e36b913d8eb2555e036742c4ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / cam_verdict-1.1.1-py3-none-any.whl
| Download URL | cam_verdict-1.1.1-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e631b3031e85267cf24fdd02e858868a99c4d8964d689d5104122da3485b9729
|
|
BLAKE2b-256 checksum How to use checksums |
3df2e1459f2b092591c1c16bc77d1b766016d1b0d91a01d5799c872e2f653c25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for cam-verdict 1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cam_verdict-1.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
