Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.infoinlet-marketplace/mcp-workflow

NPM · @INFOINLET/MCP-WORKFLOW · SCANNED SEP 21

Workflow automation for AI agents — browse 125 connectors + 234 templates, run via FluxTurn.

0 this week 72 Trust /100
Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 274 tokens (~45/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 10% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.infoinlet-marketplace/mcp-workflow server?

io.github.infoinlet-marketplace/mcp-workflow runs locally as an npm package, launched with npx -y @infoinlet/mcp-workflow. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @infoinlet/mcp-workflow

# add to Claude Code
claude mcp add infoinlet-marketplace-mcp-workflow -- npx -y @infoinlet/mcp-workflow
// .cursor/mcp.json
{
  "mcpServers": {
    "infoinlet-marketplace-mcp-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "@infoinlet/mcp-workflow"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "infoinlet-marketplace-mcp-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "@infoinlet/mcp-workflow"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add infoinlet-marketplace-mcp-workflow -- npx -y @infoinlet/mcp-workflow
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "infoinlet-marketplace-mcp-workflow": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@infoinlet/mcp-workflow"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add infoinlet-marketplace-mcp-workflow --command npx --arg -y --arg @infoinlet/mcp-workflow
# ~/.hermes/config.yaml
mcp_servers:
  infoinlet-marketplace-mcp-workflow:
    command: "npx"
    args: ["-y", "@infoinlet/mcp-workflow"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "infoinlet-marketplace-mcp-workflow": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@infoinlet/mcp-workflow"
      ]
    }
  }
}
# add to Vellum
assistant mcp add infoinlet-marketplace-mcp-workflow -t stdio -c npx -a -y @infoinlet/mcp-workflow
// mcp.json
{
  "mcpServers": {
    "infoinlet-marketplace-mcp-workflow": {
      "command": "npx",
      "args": [
        "-y",
        "@infoinlet/mcp-workflow"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 21 Sept 2026 · Analysed npm/@infoinlet/mcp-workflow@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 109 packages
Packages resolved 109
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~274 tokens

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 →

Tool Tokens
get_template ~46

Get a template by id or name. Returns the bundled summary; the full canvas/steps come from the engine when FLUXTURN_API_URL is set.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

get_workflow_status ~34

Poll the status/result of a workflow execution. Requires FLUXTURN_API_URL.

NameTypeReqDescription
execution_idstringyes

No output schema declared.

No examples provided.

list_connectors ~59

Browse the 125 available integration connectors (Slack, Gmail, Stripe, HubSpot, Salesforce, freee, Money Forward, ...). Optionally filter by category.

NameTypeReqDescription
categorystringe.g. communication, crm, finance, ecommerce

No output schema declared.

No examples provided.

list_templates ~55

Browse 234 prebuilt automation templates. Filter by category or free-text search (matches name/description/tags/required connectors).

NameTypeReqDescription
categorystring
limitnumber
searchstring

No output schema declared.

No examples provided.

run_template ~40

Instantiate and run a prebuilt template with inputs. Requires FLUXTURN_API_URL.

NameTypeReqDescription
inputsobject
template_idstringyes

No output schema declared.

No examples provided.

run_workflow ~40

Run an existing workflow by id with inputs. Requires FLUXTURN_API_URL.

NameTypeReqDescription
inputsobject
workflow_idstringyes

No output schema declared.

No examples provided.

Common questions

What is the io.github.infoinlet-marketplace/mcp-workflow server?

io.github.infoinlet-marketplace/mcp-workflow is listed in the public MCP registry as io.github.infoinlet-marketplace/mcp-workflow. Workflow automation for AI agents, browse 125 connectors + 234 templates, run via FluxTurn. This page covers its npm package (@infoinlet/mcp-workflow).

Is the io.github.infoinlet-marketplace/mcp-workflow server safe to use?

io.github.infoinlet-marketplace/mcp-workflow scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.infoinlet-marketplace/mcp-workflow server expose?

io.github.infoinlet-marketplace/mcp-workflow exposes 6 tools: list_connectors, list_templates, get_template, run_template, run_workflow, get_workflow_status. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

Is the io.github.infoinlet-marketplace/mcp-workflow server still maintained?

io.github.infoinlet-marketplace/mcp-workflow is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.infoinlet-marketplace/mcp-workflow server under?

io.github.infoinlet-marketplace/mcp-workflow declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.