CalderFlow MCP server
com.calderflow/calderflowcalderflow.comstreamable-httpv1.0.0Scanned
Make editable flowcharts, process charts, funnels, timelines and data models from plain language.
10 tools: 1 can delete or cancel things, 7 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CalderFlow MCP server can do
The CalderFlow MCP server is published by calderflow.com, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: delete_chart) and create or change data (7 tools: create_flowchart, create_chevron_chart, create_funnel_chart, create_lifecycle_chart and 3 more). 2 tools only read.
2 tools bring in text other people can write (get_chart and list_charts).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Deletes or cancels 1Claude Code: deny
delete_chartPermanently delete a chart you own.No findings
Why it is in this group
- The name "delete_chart" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
Description, as the server wrote it Permanently delete a chart you own.
Changes things 7Claude Code: ask
create_chevron_chartCreate a sequential/chevron chart: a linear sequence of steps, phases, or stages (e.g.No findings
Why it is in this group
- The name "create_chevron_chart" says "create": a word for a change.
Description, as the server wrote it Create a sequential/chevron chart: a linear sequence of steps, phases, or stages (e.g. onboarding steps, project phases). NOT for branching logic — use create_flowchart for that. Include a 1-2 sentence description per step to make it presentation-ready. Aim for 4-6 steps: Presentation is one slide of at most 6. For a longer process, follow up with edit_chart set_presentation_steps choosing the 4-6 most important step IDs.
create_erd_chartCreate an entity-relationship diagram (database schema / data model) with typed fields, PK/FK markers, and crow's-foot relationships.No findings
Why it is in this group
- The name "create_erd_chart" says "create": a word for a change.
Description, as the server wrote it Create an entity-relationship diagram (database schema / data model) with typed fields, PK/FK markers, and crow's-foot relationships. Entity names UPPER_SNAKE_CASE, 3-8 focused fields each.
create_flowchartCreate a presentation-ready flowchart or architecture diagram from Mermaid source.No findings
Why it is in this group
- The name "create_flowchart" says "create": a word for a change.
Description, as the server wrote it Create a presentation-ready flowchart or architecture diagram from Mermaid source. Use for branching processes, decision trees, and system architecture. Rules: start with 'flowchart TD' or 'flowchart LR'; solid arrows only (-->, optionally with |labels|); node shapes: A[Process] B{Decision} C([Start/End]). CalderFlow presents decisions as compact amber cards and terminals as green states, so use shapes semantically and do not add decorative classDef noise. CALIBRATE DETAIL: vague/ideation ask → 4-7 nodes, happy path + at most 2 essential decisions, NO subgraphs; detailed/spec-driven ask → subgraphs as phases, <=7 nodes per subgraph, <=18 nodes total (split the story into an overview plus detail chart beyond that). Consolidate checks that lead to the same outcome. If any subgraph is used, EVERY node—including starts, errors, and final outcomes—must be declared inside exactly one subgraph. Put internal edges inside their subgraph and cross-phase edges outside. Node labels 1-4 words; label every decision branch. Connect phases that hand off to each other. Returns the chart id + share URL. Give every node an icon with a %% nodeIcon <nodeId> <icon> line and mark the one step to remember with class <nodeId> keyStep (see the server instructions for icon names).
create_funnel_chartCreate a funnel chart for filtering/narrowing processes where quantities reduce per stage (conversion funnels, pipelines).No findings
Why it is in this group
- The name "create_funnel_chart" says "create": a word for a change.
Description, as the server wrote it Create a funnel chart for filtering/narrowing processes where quantities reduce per stage (conversion funnels, pipelines). Include stage values when numbers are available; set conversionRates for proportional widths.
create_lifecycle_chartCreate a lifecycle chart: phases across the top and milestones plotted on a curve.No findings
Why it is in this group
- The name "create_lifecycle_chart" says "create": a word for a change.
Description, as the server wrote it Create a lifecycle chart: phases across the top and milestones plotted on a curve. Each milestone has a level 1-10 setting its height — bell curves, S-curves, dips all emerge from levels. Use for product lifecycles, customer journeys, adoption/maturity curves. Every milestone needs a phaseId.
create_timeline_chartCreate a timeline of events in chronological order (roadmaps, company history, sprint/release schedules).No findings
Why it is in this group
- The name "create_timeline_chart" says "create": a word for a change.
Description, as the server wrote it Create a timeline of events in chronological order (roadmaps, company history, sprint/release schedules). Every event needs a marker: supplied dates, relative time for a proposed plan, or Phase 1, Phase 2, etc. for an undated process. Never invent factual dates or measured durations. Include concise descriptions; group related events into eras.
edit_chartEdit an existing chart.1 finding
Why it is in this group
- The name "edit_chart" says "edit": a word for a change.
Findings
- Info
The description is 2,468 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...tyle_chart takes {target: '<nodeId>'|'all', bgColor?, textColor?, borderColor?})."
Description, as the server wrote it Edit an existing chart. Call get_chart first to see its current spec, then pass tool_calls (surgical edits) and/or mermaid (full source replacement, flowchart/ERD only). A create_* tool call replaces the chart's data wholesale and can switch its type. Valid tool names — flowchart: style_chart, update_node, delete_node, add_node, connect_nodes, delete_edge, organize_sections, add_section, update_section, delete_section, move_node_to_section, set_node_icon ({nodeId, icon} or icon "none" to remove), set_key_step ({nodeId} or "none"); process/funnel/timeline/lifecycle: set_item_icon ({itemId, icon} or icon "none") and set_key_item ({itemId} or "none"), plus icon on add_* calls; any type: set_slide_text ({headline, takeaway}) for the Designed presentation slide and set_walkthrough ({steps:[{id, caption}]}) for the Walkthrough (a flowchart with 2+ sections walks one step per section, using subgraph IDs; otherwise use node or item IDs); chevron: create_chevron_chart, add_step, update_step, delete_step, reorder_steps, set_presentation_steps, style_chevron_chart; funnel: create_funnel_chart, add_funnel_stage, update_funnel_stage, delete_funnel_stage, reorder_funnel_stages, style_funnel_chart; lifecycle: create_lifecycle_chart, add_lifecycle_milestone, update_lifecycle_milestone, delete_lifecycle_milestone, update_lifecycle_phase, style_lifecycle_chart; timeline: create_timeline_chart, add_timeline_event, update_timeline_event, delete_timeline_event, reorder_timeline_events, style_timeline_chart; erd: create_erd_chart, add_erd_entity, update_erd_entity, delete_erd_entity, add_erd_attribute, update_erd_attribute, delete_erd_attribute, add_erd_relationship, update_erd_relationship, delete_erd_relationship, set_erd_direction, style_erd_chart (set_erd_direction takes {direction: "vertical"|"horizontal"}). For chevron Presentation-only selection/order edits, use set_presentation_steps with {stepIds:[up to 6 existing IDs in featured order]} (or null to reset to all); never reorder_steps, delete_step, or rename Full steps to change a Presentation summary. Use organize_sections with {sections:[{sectionId,title,nodeIds}], ungroupedNodeIds?} for a complete multi-section regroup; omitted nodes are placed with their closest connected section. Input shapes otherwise match the get_chart spec data (e.g. add_node takes {nodeId, label, shape?, connectFrom?, connectTo?}; style_chart takes {target: '<nodeId>'|'all', bgColor?, textColor?, borderColor?}).
Only reads 2Show 2 read-only tools
get_chartFetch a chart's current spec (JSON) and editable source text, plus its share URL.Reads text others writeNo findings
Why it is in this group
- The name "get_chart" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch a chart's current spec (JSON) and editable source text, plus its share URL.
list_chartsList your CalderFlow charts (id, title, type, share URL), newest first.Reads text others writeNo findings
Why it is in this group
- The name "list_charts" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List your CalderFlow charts (id, title, type, share URL), newest first.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.calderflow.com/mcp: tools/list returned 10 tools to an anonymous client, including delete_chart (destructive), create_flowchart (write), create_chevron_chart (write), create_funnel_chart (write), create_lifecycle_chart (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Infoedit_chart
The description is 2,468 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...tyle_chart takes {target: '<nodeId>'|'all', bgColor?, textColor?, borderColor?})."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http calderflow https://www.calderflow.com/mcp --header 'X-API-Key: <your-x-api-key>'claude mcp add --transport http calderflow https://www.calderflow.com/mcp --header 'X-API-Key: <your-x-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__calderflow__get_chart",
"mcp__calderflow__list_charts"
],
"ask": [
"mcp__calderflow__create_flowchart",
"mcp__calderflow__create_chevron_chart",
"mcp__calderflow__create_funnel_chart",
"mcp__calderflow__create_lifecycle_chart",
"mcp__calderflow__create_timeline_chart",
"mcp__calderflow__create_erd_chart",
"mcp__calderflow__edit_chart"
],
"deny": [
"mcp__calderflow__delete_chart"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as calderflow. Review it before you use it.
Capability tags behind 2 rules
- mcp__calderflow__get_chart untrusted-input
- mcp__calderflow__list_charts untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.calderflow/calderflow/verify?hash=57e34d1b17abe437538cc0015f56aa9e429364ed8d5fb1985838ebd9624db9bb" | jq -e '.changed == false'Pinned hash 57e34d1b17ab, from Nov 15, 2026, 04:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.calderflow/calderflow/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.calderflow/calderflow)Source: MCP Registry. Synced Nov 15, 2026, 05:17 UTC.
CalderFlow MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CalderFlow MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CalderFlow MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_chart.
Can the CalderFlow MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CalderFlow MCP server have?
- 10 tools: 1 destructive, 7 write, 2 read. delete_chart, create_flowchart, create_chevron_chart, create_funnel_chart, create_lifecycle_chart, create_timeline_chart, create_erd_chart, edit_chart and 2 more.
Does the CalderFlow MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CalderFlow MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CalderFlow MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.