io.github.shofer-dev/slang-workflows
NPM · SLANG-WORKFLOWS
Provable, declarative multi-agent workflows for Claude Code (typed .slang, non-LLM executor).
Available components
Last scanned (4 hours ago)
Scores higher than 65% of npm servers
Category AI and Machine Learning
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 112 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 122 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 704 tokens (~100/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
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 npm/slang-workflows@0.1.2
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 →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 112 packages
| Packages resolved | 112 |
|---|---|
| Stale | 33 |
| No linked repository | 8 |
| 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 →
get_slang_grammar Get slang grammar ~67
Return a concise slang grammar cheatsheet (constructs + a complete example) so you can GENERATE a workflow on the fly and run it inline via run_workflow(source). Validate generated source with validate_workflow(source) first; run_workflow also rejects parse/static-analysis errors.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_topology Get workflow topology (Mermaid) ~61
Return the current agent topology of a run as a Mermaid flowchart (nodes colored by status, plus live sending/waiting edges). Render it inline. Identify it by `workflow_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | Id returned by run_workflow. |
No output schema declared.
No examples provided.
get_trace Get workflow trace (Mermaid sequence + event log) ~87
Return a run's execution trace as a Mermaid `sequenceDiagram` (round-by-round: who staked/routed to whom, commits, escalations, terminal event) plus the raw event log. The timeline counterpart to `get_topology`'s snapshot. Render the diagram inline. Identify it by `workflow_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | Id returned by run_workflow. |
No output schema declared.
No examples provided.
get_workflow_state Get workflow state ~64
Return the serialized FlowState for a run started by `run_workflow`: per-agent status, opIndex, bindings, round, budget usage, and flow status. Identify it by `workflow_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | Id returned by run_workflow. |
No output schema declared.
No examples provided.
list_workflows List workflows ~49
Discover .slang workflow files in the project (.claude/workflows/) and global (~/.claude/workflows/) directories. Returns each flow's name, title, params, and agent count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_workflow Run workflow ~264
Parse and run a .slang workflow to completion, dispatching each agent through the Claude Agent SDK and validating results against output contracts. Identify it by `name` or `path`; pass flow `params` as an object. Returns the final flow status and each agent's output. Rejects parse/static-analysis errors before running. Default runs synchronously (returns the final status + each agent's output). Pass background:true to start the run and return a workflow_id immediately, then poll get_trace/get_topology/get_workflow_state to watch it live; @Human escalation only works in synchronous runs.
| Name | Type | Req | Description |
|---|---|---|---|
| background | boolean | – | Start the run and return a workflow_id immediately, then poll get_trace/get_topology/get_workflow_state. (@Human escalation unsupported in background.) |
| model | string | – | Default model for agents without api_configuration (e.g. sonnet). |
| name | string | – | Flow name or .slang filename. |
| params | object | – | Flow parameters as a key/value object. |
| path | string | – | Absolute path to a .slang file (overrides `name`). |
| source | string | – | Inline .slang source (overrides name/path) — e.g. a workflow an LLM generated on the fly. |
No output schema declared.
No examples provided.
validate_workflow Validate workflow ~112
Parse and statically analyze one workflow (deadlock detection, unknown refs, missing converge/budget, orphan outputs) without running it. Identify it by `name` or absolute `path`.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Flow name or .slang filename (project scope preferred). |
| path | string | – | Absolute path to a .slang file (overrides `name`). |
| source | string | – | Inline .slang source to validate (overrides name/path) — validate generated flows before running. |
No output schema declared.
No examples provided.
How do I install the io.github.shofer-dev/slang-workflows MCP server?
io.github.shofer-dev/slang-workflows runs locally as an npm package, launched with npx -y slang-workflows. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · slang-workflows
claude mcp add shofer-dev-slang-workflows -- npx -y slang-workflows
What is the io.github.shofer-dev/slang-workflows MCP server?
io.github.shofer-dev/slang-workflows is an MCP server listed in the public MCP registry as io.github.shofer-dev/slang-workflows. Provable, declarative multi-agent workflows for Claude Code (typed .slang, non-LLM executor). This page covers its npm package (slang-workflows).
Is the io.github.shofer-dev/slang-workflows MCP server safe to use?
io.github.shofer-dev/slang-workflows scores 80 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 5 November 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.shofer-dev/slang-workflows MCP server expose?
io.github.shofer-dev/slang-workflows exposes 7 tools: list_workflows, get_slang_grammar, validate_workflow, run_workflow, get_workflow_state, and 2 more. Their descriptions and schemas cost roughly 704 tokens of context every time the server is loaded.
Is the io.github.shofer-dev/slang-workflows MCP server still maintained?
io.github.shofer-dev/slang-workflows 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 io.github.shofer-dev/slang-workflows MCP server under?
io.github.shofer-dev/slang-workflows 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.