io.github.northwindapps/freeflowchart
NPM · FREEFLOWCHART
Render text-based flowcharts (FlowScript) to PNG/PDF/Markdown with layout feedback, offline.
Available components
Last scanned (19 hours ago)
Scores higher than 32% of npm servers
Category Design and Media
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 zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 35 of 117 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1340 tokens (~1340/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 +1
- Package version: 0.3.1 → 0.3.2 functional
- 18 Nov 26 −10
- Known CVEs: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Schema quality: 1111 → 1340 ▼ functional
- Dependency health: unverified → 0.87 ▲ functional
- Package version: 0.2.1 → 0.3.1 functional
- Package version: 0.2.1 → 0.3.0 functional
- 17 Nov 26 −5
- Known CVEs: fail → unverified ▼ security
- Dependency health: 0.87 → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Schema quality: 969 → 1071 ▼ functional
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.1.1 → 0.2.0 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 21 Nov 2026 · Analysed npm/freeflowchart@0.3.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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 117 packages
| Packages resolved | 117 |
|---|---|
| Stale | 35 |
| 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 →
render_flowchart Render flowchart ~1,340
Render a FlowScript flowchart to PNG or PDF. PNG output is returned as an image so you can check the result; PDF is saved to a file. Pass output_path to save either format to disk. The result also includes a JSON layout: every node with its box (x, y, width, height in CSS px from the image top-left; multiply by scale for image pixels), the script line it came from, the edges, and detected issues ("overlap", "edge_crosses_node") with the script lines involved. Use the issues to revise the script and render again. Pass markdown_path to also save a Markdown file documenting the chart: the PNG image, a step-by-step outline of the flow, and the FlowScript source (so it can be edited and re-rendered later). The PNG is saved next to it unless output_path is a .png. Scripts with several pages ("pagebreak <name>" lines) render one image per page; files are saved as name-1.png, name-2.png, …, a PDF gets one page per chart page, and the Markdown gets one section per page. The layout then has a "pages" array. Saved files must end in .png, .pdf or .md (matching the format), cannot be in hidden or system folders, and an existing file is only replaced if freeflowchart created it. # FlowScript language reference FlowScript is a line-based text format that renders to a left-to-right flowchart. ## Rules - **One statement per line.** Indentation and blank lines are ignored; indent only for readability. - A line is either a **keyword line** or a **process line** (any other text becomes a box). - Keywords are lowercase and must be the **first word** on the line. - **Gotcha:** a process label must not start with a keyword word. `none of the above` is read as the `none` keyword followed by a box labelled `of the above`. Reword it (`No match`) or capitalize it (`None of the above`), since keywords are case-sensitive. - Every `if`/`if2` needs a `then … endthen` block and a closing `endif`. `if` may also have one `else … endelse` block between `endthen` and `endif`. ## Keywor…
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format |
| include_layout | boolean | – | Include the JSON layout in the result |
| markdown_path | string | – | Absolute path of a .md file to write: image, step outline and FlowScript source. |
| output_path | string | – | Absolute file path to save the output to. Required to keep a PDF in a specific place; if omitted for PDF, a temp file path is returned. |
| scale | number | – | Pixel ratio (resolution multiplier) |
| script | string | yes | FlowScript source, one statement per line |
| title | string | – | Heading for the Markdown file (default: its file name) |
No output schema declared.
No examples provided.
How do I install the io.github.northwindapps/freeflowchart MCP server?
io.github.northwindapps/freeflowchart runs locally as an npm package, launched with npx -y freeflowchart mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · freeflowchart
claude mcp add northwindapps-freeflowchart -- npx -y freeflowchart mcp
What is the io.github.northwindapps/freeflowchart MCP server?
io.github.northwindapps/freeflowchart is an MCP server listed in the public MCP registry as io.github.northwindapps/freeflowchart. Render text-based flowcharts (FlowScript) to PNG/PDF/Markdown with layout feedback, offline. This page covers its npm package (freeflowchart).
Is the io.github.northwindapps/freeflowchart MCP server safe to use?
io.github.northwindapps/freeflowchart scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.northwindapps/freeflowchart MCP server expose?
io.github.northwindapps/freeflowchart exposes 1 tool: render_flowchart. Their descriptions and schemas cost roughly 1,340 tokens of context every time the server is loaded.
Is the io.github.northwindapps/freeflowchart MCP server still maintained?
io.github.northwindapps/freeflowchart is still listed as active in the MCP registry. We last reached this channel on 21 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.northwindapps/freeflowchart MCP server under?
io.github.northwindapps/freeflowchart declares the MIT 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 io.github.northwindapps/freeflowchart MCP server?
VerifyMCP ran 15 checks on io.github.northwindapps/freeflowchart, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.northwindapps/freeflowchart: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.