Experimental package — This module provides a set of MCP tools to retrieve information from GitHub
Free
Nothing to run from here
Flowspec is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for FlowSpec — exposes project specs to Claude Code
Quickstart
# 1 — run it from where its publisher ships it
npx -y flowspec-mcp
# 2 — ask your agent something
> MCP server for FlowSpec — exposes project specs to Claude Code
Flowspec is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
JKAll 1 server
jktfe1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Flowspec as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add flowspec-mcp -- npx -y flowspec-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
32 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all FlowSpec projects with names and dates
Takes no parameters.
Example callreturns →
Get the full JSON spec for a FlowSpec project (optimised for Claude Code consumption)
Takes no parameters.
Example callreturns →
Get project data (nodes, edges, screens) for a FlowSpec project
Takes no parameters.
Example callreturns →
Search for nodes by label across all projects, optionally filtered by type
Takes no parameters.
Example callreturns →
Get screen/region/element structure for a FlowSpec project (lightweight alternative to full JSON)
Takes no parameters.
Example callreturns →
Create a new FlowSpec project. Before building from a codebase, scan source files for @flowspec annotations (left by the codebase-indexer skill) to avoid re-discovering already-indexed elements.
Takes no parameters.
Example callreturns →
Add a node (datapoint, component, transform, or table) to a project. Check source files for @flowspec annotations first — they contain pre-indexed element definitions (e.g. // @flowspec dp-name: type, source, constraints).
Takes no parameters.
Example callreturns →
Update a node\
Takes no parameters.
Example callreturns →
Connect two nodes with an edge type (flows-to, derives-from, transforms, validates, contains)
Takes no parameters.
Example callreturns →
Run orphan node and duplicate label analysis on a project
Takes no parameters.
Example callreturns →
Validate data flow semantics: DataPoint sources, Transform I/O, Component references, type matching, and circular dependencies
Takes no parameters.
Example callreturns →
Update a project name or replace its entire canvas state
Takes no parameters.
Example callreturns →
Delete a FlowSpec project
Takes no parameters.
Example callreturns →
Remove a node and all its connected edges from a project
Takes no parameters.
Example callreturns →
Remove an edge from a project
Takes no parameters.
Example callreturns →
Import JSON specification to create/merge nodes, edges, and screens. If the codebase has @flowspec annotations, incorporate them into the spec before importing to avoid duplicating pre-indexed elements.
Takes no parameters.
Example callreturns →
Apply automatic hierarchical layout (Dagre) to organize nodes
Takes no parameters.
Example callreturns →
Upload an image and get its URL with auto-detected dimensions
Takes no parameters.
Example callreturns →
Create a new wireframe screen with optional image
Takes no parameters.
Example callreturns →
Update screen properties (name, image)
Takes no parameters.
Example callreturns →
Delete a wireframe screen and all its regions
Takes no parameters.
Example callreturns →
Add a region to a screen with % coordinates and element IDs
Takes no parameters.
Example callreturns →
Update region position, size, label, or element IDs
Takes no parameters.
Example callreturns →
Remove a region from a screen
Takes no parameters.
Example callreturns →
Update edge type, label, or handle positions
Takes no parameters.
Example callreturns →
Clone a project for backup or branching
Takes no parameters.
Example callreturns →
List all decision trees for a project
Takes no parameters.
Example callreturns →
Get a decision tree with full node/edge structure
Takes no parameters.
Example callreturns →
Delete a decision tree from a project
Takes no parameters.
Example callreturns →
Analyse a decision tree: depth, orphans, outcomes, under-branched decisions
Takes no parameters.
Example callreturns →
Get the Boring Logic board for a project — a separate canvas of input/output/process/decision nodes sketching data logic
Takes no parameters.
Example callreturns →
Save (create or replace) the Boring Logic board for a project
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Flowspec costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 5.5.2 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digesta352e6ae4f2348a4e64e4c883f8680b166ce459c65669ff6b4e5feebc25c7307
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (30 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| flowspec_list_projects | no tags | |
| flowspec_get_json | no tags | |
| flowspec_get_project | no tags | |
| flowspec_search_nodes | no tags | |
| flowspec_get_screen_context | no tags | |
| flowspec_create_project | no tags | |
| flowspec_create_node | no tags | |
| flowspec_update_node | no tags | |
| flowspec_create_edge | no tags | |
| flowspec_analyse_project | no tags | |
| flowspec_validate_project | no tags | |
| flowspec_update_project | no tags | |
| flowspec_delete_project | no tags | |
| flowspec_delete_node | no tags | |
| flowspec_delete_edge | no tags | |
| flowspec_import_json | no tags | |
| flowspec_auto_layout | no tags | |
| flowspec_upload_image | no tags | |
| flowspec_create_screen | no tags | |
| flowspec_update_screen | no tags | |
| flowspec_delete_screen | no tags | |
| flowspec_add_region | no tags | |
| flowspec_update_region | no tags | |
| flowspec_remove_region | no tags | |
| flowspec_update_edge | no tags | |
| flowspec_clone_project | no tags | |
| flowspec_list_decision_trees | no tags | |
| flowspec_get_decision_tree | no tags | |
| flowspec_delete_decision_tree | no tags | |
| flowspec_analyse_decision_tree | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta352e6ae4f2348a4
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 5.5.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
5.5.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Flowspec in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.