PROCESIO
PYPI · PROCESIO-CLI · 2 COMPONENTS
Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents.
Available components
Last scanned (7 hours ago)
Scores higher than 89% of PyPI servers
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Procesio-Externals/procesio-cli). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1983 tokens (~94/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 +1
- Package version: 0.1.5 → 0.1.6 functional
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.3 → 0.1.5 functional
- Package version: 0.1.3 → 0.1.4 functional
- 27 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/procesio-cli@0.1.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Procesio-Externals/procesio-cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Procesio-Externals/procesio-cli/.github/workflows/release.yml@refs/tags/v0.1.6 |
| Rekor log index | 3666294434 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:806ca141f9de9cd3af4203206b5ab862b7727af279a19688a08366714166b418 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
procesio_add_form_field Add fields to a PROCESIO form ~121
Add one or more input fields to an existing form.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | Report what would be added; add nothing. |
| elements | string | – | The fields to add, as a JSON array. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The form id. |
| parent | string | – | Id of the container to add them into. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_build_connector Build a PROCESIO connector from API docs ~122
Start building a custom PROCESIO connector from an API's documentation. Give it the docs URL and what you need the connector to do; it reads the docs, asks what it still needs, and generates a connector package. Returns a build id - follow it with procesio_get_connector_build.
| Name | Type | Req | Description |
|---|---|---|---|
| api_docs_text | string | – | The documentation itself, if there is no public URL. |
| api_url | string | – | URL of the API documentation to read. |
| user_requirements | string | – | What the connector needs to do, in plain language. |
No output schema declared.
No examples provided.
procesio_create_form Create a PROCESIO form ~107
Create a form from a JSON definition. Returns the new form id. Add fields afterwards with procesio_add_form_field.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | – | The form definition, as a JSON object. |
| dry_run | boolean | – | Report what would be created; create nothing. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_create_process Create a PROCESIO process ~117
Create a new automation process from a JSON definition of its steps and connections. Returns the new process id. Pass dry_run to see what would be built without creating anything.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | – | The process definition, as a JSON object. |
| dry_run | boolean | – | Report what would be created; create nothing. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_download_connector Download a built connector ~56
Save a finished build's connector package to a local file, ready to install with procesio_install_connector.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | The build id. |
| out | string | yes | Local path to write the package to. |
No output schema declared.
No examples provided.
procesio_edit_process Edit a PROCESIO process ~144
Change an existing process - add, retarget or reconfigure its steps. Pass dry_run first to see the diff. Removing steps additionally requires allow_remove, so a partial definition cannot silently delete work.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_remove | boolean | – | Permit this edit to delete steps. |
| config | string | – | The changes, as a JSON object. |
| dry_run | boolean | – | Report the diff; change nothing. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The process id. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_get_connector_build Check a connector build ~44
Report a build's stage, what it is waiting on, and whether a connector package is ready to download.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | The build id. |
No output schema declared.
No examples provided.
procesio_get_form Read a PROCESIO form ~80
Return a form's definition - its fields, their types and how they are laid out.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The form id. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_get_run_output Read a PROCESIO run output ~88
Return the values a finished run produced. Only meaningful once the run has completed - check with procesio_get_run_status first.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The run id. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_get_run_status Check a PROCESIO run ~103
Report whether a run is still going, finished or failed, and which step it reached. Takes the run id returned by procesio_run_process.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | boolean | – | Include per-step detail. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The run id. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_install_connector Install a connector into PROCESIO ~100
Install a connector package into a workspace, after which its operations appear as steps you can use when building a process.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| file | string | yes | Path to the connector package. |
| name | string | – | Name to show in the designer. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_list_connector_builds List connector builds ~44
List connector builds and their current stage.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number. |
| status | string | – | Only builds in this stage. |
No output schema declared.
No examples provided.
procesio_list_connectors List installed connectors ~71
List the connectors installed in a workspace - the extra step types available when building a process.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_list_environments List PROCESIO environments ~27
List the configured environments, so a call can be pointed at the right one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
procesio_list_forms List PROCESIO forms ~75
List the forms in a workspace. A form is the screen a person fills in to start or feed a process.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_list_processes List PROCESIO processes ~121
List the automation processes in a PROCESIO workspace, newest first. Use this to find the id of a process before running, editing or validating it.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| page | integer | – | 1-based page number. |
| page_size | integer | – | Processes per page. |
| search | string | – | Only processes whose name matches this text. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_list_workspaces List PROCESIO workspaces ~75
List the workspaces this account can reach. A workspace holds its own processes, forms, connectors and credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_run_process Run a PROCESIO process ~158
Execute a process and return its run id. A process does real work - it can send mail, write to databases and call external systems - so this is never run unattended. Follow it with procesio_get_run_status and procesio_get_run_output.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The process id. |
| payload | string | – | Input values for the run, as a JSON object. |
| synchronous | boolean | – | Wait for the run to finish instead of returning immediately. |
| timeout | integer | – | Seconds to wait when synchronous. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_test_credential Test a PROCESIO credential ~95
Check that a stored credential can still reach the system it belongs to. Answers whether a connection is working without running a whole process.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | – | The credential to test, as a JSON object. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_tidy_process_layout Tidy a process canvas ~124
Re-arrange a process's steps on the design canvas so it is readable. Changes only the visual layout, never what the process does. Worth running after building a process through the API, which places steps without arranging them.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | Report the new layout; change nothing. |
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The process id. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
procesio_validate_process Validate a PROCESIO process ~111
Check a process for errors without running it - unconnected steps, missing required inputs, broken references. Do this before running a process you just built. Validating is not the same as running: a process can validate and still fail at execution.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Named environment, e.g. Internal-QA. Omit for the default. |
| id | string | yes | The process id. |
| workspace_id | string | – | Workspace to act in. Omit to use the default workspace. |
No output schema declared.
No examples provided.
How do I install the PROCESIO MCP server?
PROCESIO runs locally as a PyPI package, launched with uvx procesio-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · procesio-cli
claude mcp add procesio-externals-procesio-cli -- uvx procesio-cli
What is the PROCESIO MCP server?
PROCESIO is an MCP server listed in the public MCP registry as io.github.Procesio-Externals/procesio-cli. Lets your own AI assistant build, run, validate and audit PROCESIO processes, forms and documents. This page covers its PyPI package (procesio-cli).
Is the PROCESIO MCP server safe to use?
PROCESIO scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PROCESIO MCP server expose?
PROCESIO exposes 21 tools: procesio_list_processes, procesio_create_process, procesio_edit_process, procesio_validate_process, procesio_run_process, and 16 more. Their descriptions and schemas cost roughly 1,983 tokens of context every time the server is loaded.
Is the PROCESIO MCP server still maintained?
PROCESIO is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the PROCESIO MCP server under?
PROCESIO declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the PROCESIO MCP server?
VerifyMCP ran 16 checks on PROCESIO, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.