Bragproof

← Reports

@cyanheads/workflows-mcp-server

Starts with no setup0.5.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: nothing

5tools listed
0hosts contacted
0files written
0.3 sto start
38dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @cyanheads/workflows-mcp-server@0.5.0

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.

workflow_listNo usable answer tool reported an error: Error: Workflow index is not ready yet Recovery: Retry after the server has finished initializing its workflow index. (reason index_un

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

workflow_list query, category, tags, includeTools
List permanent workflows, optionally narrowed by category (case-insensitive substring), tags (AND match), and a keyword query matched against workflow names and descriptions. Filters combine with AND. Set includeTools to true to surface the unique <server>/<tool> pairs used across each matching workflow. Temporary workflows are never included.
workflow_get name, version
Retrieve a complete workflow definition by name. When version is omitted, returns the highest available version. Also returns optional global execution guidance to apply when running the workflow, or null when none is configured. Template placeholders like {{input.foo}} in step params are opaque strings, returned verbatim. Temporary workflows are accessible here but excluded from workflow_list.
workflow_create name, version, description, author, category, tags, steps
Create and durably store a new permanent workflow. Rejects the write when the same name and version already exist, as a permanent workflow or a temporary draft — bump the version to store a revision alongside the existing one. Created and last-updated dates are stamped automatically. Template placeholders like {{input.foo}} in step params are stored verbatim, not resolved. New workflows appear in workflow_list and are retrievable with workflow_get.
workflow_create_temp name, version, description, author, tags, steps
Create a temporary workflow draft for a one-shot plan, scaffolding, or a draft not yet meant for the permanent library. Drafts are retrievable with workflow_get but never appear in workflow_list. A draft stays on disk until it is deleted with workflow_delete — nothing expires it. Writing a name and version that already has a draft overwrites that draft, keeps its created date, and reports status "overwritten"; a name and version held by a permanent workflow is rejected. Created and last-updated dates are stamped automatically.
workflow_delete name, version
Remove a workflow — a permanent workflow or a temporary draft — from the library by name. When version is omitted, the highest version across both is selected; pass a version to target a specific one. Before anything is deleted, the user is asked to confirm the resolved workflow (name@version, whether it is permanent or temporary, and its file). Each prompt is valid for one answer within 10 minutes, and the file is deleted only if it is unchanged since the user saw it; a declined confirmation deletes nothing, and a client that cannot show the prompt cannot delete. Deletion is irreversible: the file is removed, and the workflow no longer appears in workflow_list or workflow_get — unless another file declares the same name and version, in which case that copy takes its place and the result carries a notice naming it. Deleting a draft frees its name and version for workflow_create.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=24.0.0
Sourcegithub.com/cyanheads/workflows-mcp-server
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-ka8yrUmg3mPoxWWYiQY22LYkGP91MhbBbulzHEl6Nz42Fc9ovs9Id4loHYd6R4/0cAHVCXGiTGy170VxyLb3Bg==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@cyanheads/workflows-mcp-server.svg)](https://bragproof.smaverk.com/r/%40cyanheads/workflows-mcp-server)

New version out? Ask for a fresh report.