Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Juliusolsson05/workflow-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/juliusolsson05/workflow-mcp/mcp-registry-workflow-mcp)<a href="https://agentmods.dev/mcp/juliusolsson05/workflow-mcp/mcp-registry-workflow-mcp"><img src="https://agentmods.dev/badge/mcp/juliusolsson05/workflow-mcp/mcp-registry-workflow-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/juliusolsson05/workflow-mcp/mcp-registry-workflow-mcp"><img src="https://agentmods.dev/badge/mcp/juliusolsson05/workflow-mcp/mcp-registry-workflow-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
workflow-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"workflow-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/juliusolsson/workflow-mcp@sha256:4b6889f9e78d0208e6d1d343ba23d0c5d092b1a1513a73c9c85deb2d00ab5855",
"true",
"10001:10001",
"ALL",
"no-new-privileges:true",
"seccomp=unconfined",
"apparmor=unconfined",
"256",
"2g",
"1",
"/tmp:size=256m,mode=1777,uid=10001,gid=10001",
"/run/workflow-mcp:size=16m,mode=0700,uid=10001,gid=10001",
"type=volume,target=/data",
"type=bind,source={project},target=/workspace,readonly"
],
"env": {
"OPENAI_API_KEY": "",
"WORKFLOW_MCP_CONCURRENCY": "1"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 28 lines scan A 6d609d083292
workflow-mcp is an MCP server published in the GitHub repository Juliusolsson05/workflow-mcp (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm run start-stdio.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.