mcp-surveys-cli
Python CLI for secure short-lived human surveys.
Secure create is the default and stores the E2EE receipt locally. Send only the returned public_url to the human.
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli install-skill --target both
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli template decision > survey.json
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli schema
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli create survey.json
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli wait <survey_id> --format markdown
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli answers <survey_id>
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli stats
Receipt path defaults to ~/.config/mcp-surveys/receipts/<survey_id>.json; override with MCP_SURVEYS_RECEIPT_DIR or pass --receipt when reading answers elsewhere.
Plaintext is explicit opt-in only:
uvx --refresh-package mcp-surveys-cli mcp-surveys-cli create survey.json --mode plaintext
Use MCP_SURVEYS_BASE_URL or --base-url to point at a different instance. Outdated-version notices go to stderr and never block the command.
The hosted API also has a server-side critical upgrade gate: agent calls without x-mcp-surveys-version: 0.5.1+ receive HTTP 426 with an urgent update message. Current CLI commands send anonymous client/version/mode headers automatically for observability. Secure creates use the authenticated E2EE v2 envelope.
1 maintainer
Metadata
1 maintainer
Release files for mcp-surveys-cli 0.5.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 | |
|---|---|---|---|---|
| mcp_surveys_cli-0.5.1.tar.gz | 9.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_surveys_cli-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.8 kB
Release files / mcp_surveys_cli-0.5.1.tar.gz
| Download URL | mcp_surveys_cli-0.5.1.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33eed747c1249a7e1eaecfe292afd78827a2538434ddb7d08936233f29181086
|
|
BLAKE2b-256 checksum How to use checksums |
121de6a68cadb541909cfb64c45a3aae0b63122a88e9239dc28e43882e550c2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / mcp_surveys_cli-0.5.1-py3-none-any.whl
| Download URL | mcp_surveys_cli-0.5.1-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
518df8422af13aa521bde5fbad2764b05c9cdcdf452f0092372b770524379a06
|
|
BLAKE2b-256 checksum How to use checksums |
5ee5fa4a949e540b90b07b4dcdb4ce32b0b7c07463d19d3f03f6ce68393aa65f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for mcp-surveys-cli 0.5.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
