CalderFlow
REMOTE · WWW.CALDERFLOW.COM
Make editable flowcharts, process charts, funnels, timelines and data models from plain language.
Available components
Last scanned (23 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2826 tokens (~256/item across 11 items; 10 tools + 1 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_chart" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
- Supports UI / widget rendering.Pass
Checks we ran (13)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 64
First indexed and scored.
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 · Probed https://www.calderflow.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.calderflow.com | CN=YR2,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | RSA 2048 | SHA256-RSA | 5ad95d8695e355ae0168e60f27d0354043e |
| SANs: www.calderflow.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.calderflow.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| calderflow.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.calderflow.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.calderflow.com/mcp | HTTPS enforced | 308 | https://www.calderflow.com/mcp |
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 →
create_chevron_chart ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| steps | array | yes | Ordered list of steps. 3-7 is ideal. |
| title | string | yes | Chart title shown in the app and share page. |
No output schema declared.
No examples provided.
create_erd_chart ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | Entities (tables). 2-8 is ideal. |
| relationships | array | – | Relationships with cardinality. |
| title | string | yes | Chart title shown in the app and share page. |
No output schema declared.
No examples provided.
create_flowchart ~321
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).
| Name | Type | Req | Description |
|---|---|---|---|
| mermaid | string | yes | Mermaid flowchart source code. |
| title | string | yes | Chart title shown in the app and share page. |
No output schema declared.
No examples provided.
create_funnel_chart ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| conversionRates | array | – | Conversion percentages between adjacent stages (length = stages - 1), e.g. [75, 50, 30]. |
| stages | array | yes | Ordered stages from widest (top) to narrowest (bottom). 3-6 is ideal. |
| title | string | yes | Chart title shown in the app and share page. |
No output schema declared.
No examples provided.
create_lifecycle_chart ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| curveLabel | string | – | Y-axis label (e.g. 'Value', 'Adoption'). |
| milestones | array | yes | 4-8 milestones on the curve. |
| phases | array | yes | 2-5 phases shown as headers. |
| timeLabel | string | – | X-axis label (e.g. 'Time'). |
| title | string | yes | Chart title shown in the app and share page. |
No output schema declared.
No examples provided.
create_timeline_chart ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Layout direction; horizontal is default. |
| eras | array | – | Optional named periods grouping events (background bands). |
| events | array | yes | Chronological events. 4-10 is ideal. |
| title | string | yes | Chart title shown in the app and share page. |
No output schema declared.
No examples provided.
delete_chart ~24
Permanently delete a chart you own.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_id | string | yes | – |
No output schema declared.
No examples provided.
edit_chart ~660
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…
| Name | Type | Req | Description |
|---|---|---|---|
| chart_id | string | yes | Chart id from create_* / list_charts. |
| mermaid | string | – | Full replacement mermaid source (flowchart/ERD charts only). |
| title | string | – | New title (optional). |
| tool_calls | array | – | Ordered edit operations: [{tool, input}]. |
No output schema declared.
No examples provided.
get_chart ~35
Fetch a chart's current spec (JSON) and editable source text, plus its share URL.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_id | string | yes | – |
No output schema declared.
No examples provided.
list_charts ~27
List your CalderFlow charts (id, title, type, share URL), newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the CalderFlow MCP server?
CalderFlow is a hosted endpoint at https://www.calderflow.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.calderflow.com
claude mcp add --transport http com-calderflow-calderflow 'https://www.calderflow.com/mcp'
What is the CalderFlow MCP server?
CalderFlow is an MCP server listed in the public MCP registry as com.calderflow/calderflow. Make editable flowcharts, process charts, funnels, timelines and data models from plain language. This page covers its hosted endpoint (https://www.calderflow.com/mcp).
Is the CalderFlow MCP server safe to use?
CalderFlow scores 67 out of 100 on VerifyMCP. 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 CalderFlow MCP server expose?
CalderFlow exposes 10 tools: create_flowchart, create_chevron_chart, create_funnel_chart, create_lifecycle_chart, create_timeline_chart, and 5 more. Their descriptions and schemas cost roughly 1,729 tokens of context every time the server is loaded.
Does the CalderFlow MCP server require authentication?
No. We connected to CalderFlow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CalderFlow MCP server still maintained?
CalderFlow 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 did VerifyMCP test on the CalderFlow MCP server?
VerifyMCP ran 13 checks on CalderFlow, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 9 more. One item could not be completed, a gap on our side rather than a finding about CalderFlow: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.