Endpoints: 76,849MCP servers: 32,730Payout addresses: 3,825Paid calls: 6,164Letters: 84Defects: 3,898counted 3 min ago
teppi

Server definition

Hash
sha256:859573968cd7f6d93b294c487f5e6ae21ab56274e0b2843e141e9af3620a427f
What it is
What a remote MCP server returned when asked what it offers: 10 tools

The blob, as servednamed by its sha256

{ "instructions": "CalderFlow turns structured specs into presentation-ready diagrams. Create charts with the create_* tools; every response includes a share URL that renders the live chart and opens in the CalderFlow editor. Use get_chart → edit_chart to revise. Prefer surgical tool_calls over full rewrites.\n\nAUTHORING GUIDE — calibrate detail to the ask:\n- Vague or ideation-stage request ('map the login flow', 'sketch our onboarding'): go HIGH LEVEL. 4-7 nodes, the happy path plus at most 2 essential decisions, no subgraphs. Consolidate checks that lead to the same outcome and offer a separate detail chart afterward.\n- Presentation density: keep one chart at 18 nodes or fewer. For a larger spec, create an overview first and split dense implementation branches into a follow-up detail chart.\n- Detailed request (a spec/PRD was provided, or the user says comprehensive/all edge cases): use subgraphs as phases, but keep each subgraph to 7 nodes or fewer and the whole chart at 18 nodes or fewer. Beyond that, split into multiple charts (one per phase) and say so.\n- Subgraph completeness: if a flowchart uses any subgraph, put every node exactly once inside a phase—including start, end, error, retry, and success/failure nodes. Keep same-phase edges inside that subgraph and cross-phase edges outside. Never leave boundary nodes homeless at top level.\n- Labels: 1-4 words per node; label every decision branch (Yes/No, or the option name). Put detail in edge labels and node text only when the user asked for it.\n- Flowchart icons and key step: give every node an icon with a `%% nodeIcon <nodeId> <icon>` line after the flowchart line (names: user, users, user-plus, user-check, log-in, log-out, lock, unlock, key, shield-check, fingerprint, mail, send, message-square, bell, phone, building-2, briefcase, landmark, store, credit-card, wallet, receipt, dollar-sign, shopping-cart, package, truck, gift, check-circle, x-circle, alert-triangle, info, help-circle, ban, clock, calendar, timer, hourglass, file-text, clipboard-check, file-signature, book-open, folder, database, server, cloud, code, git-branch, git-merge, terminal, cpu, bug, settings, sliders-horizontal, search, filter, eye, upload, download, refresh-cw, repeat, link, share-2, rocket, flag, target, trophy, star, thumbs-up, heart, sparkles, zap, bar-chart-3, trending-up, trending-down, pie-chart, activity, layout-dashboard, home, globe, map-pin, smartphone, monitor, list-checks, layers, inbox, archive, handshake, lightbulb, megaphone, graduation-cap), and mark the one step to remember with `class <nodeId> keyStep` (one per chart, 4+ nodes). Edit them later with set_node_icon / set_key_step.\n- Process, funnel, timeline and lifecycle charts: give every step, stage, event or milestone an icon field and set key: true on the one item to remember (4+ items). Edit them with set_item_icon / set_key_item. Icons and the key item show in Polished Presentation; Full stays plain.\n- Iterating: NEVER recreate a chart to change part of it — use edit_chart. The user may have hand-arranged the layout; edits preserve it, recreation destroys it.\n- Users describe a communication goal, not usually a chart name. Infer the visual grammar from the relationships; do not default to flowchart because they say process, journey, roadmap, or milestones.\n- Pick in this order: entities/tables + relationships → create_erd_chart; dates/deadlines/history → create_timeline_chart; shrinking counts/filtering/conversion → create_funnel_chart; decisions/branches/dependencies/interacting systems → create_flowchart; a level such as adoption, health, or intensity rising/falling across phases → create_lifecycle_chart; otherwise ordered equal-weight steps → create_chevron_chart. Apply this to the relationship being emphasized: incidental dates or counts do not override the intended visual story.\n- Ambiguous nouns need context: a sequential customer journey → chevron, but changing engagement across that journey → lifecycle; a dated roadmap → timeline, but undated strategic phases → chevron.\n- When Timeline is selected or explicitly requested, every event needs a marker in its date field. Preserve supplied dates/times. Use relative time for proposed plans and disclose estimates; use Phase 1, Phase 2, etc. for undated processes/conversions, not invented factual dates or measured durations. Use one consistent system, with TBD for unknown dates in an otherwise dated chart. Retain concise descriptions in both Full and Presentation.\n- Timeline markers belong in each event's date field, never a missing-timing warning or instructional footer. Do not leave all markers blank; use ordinal phases when timing is unspecified.\n- Chevron descriptions: put real line breaks before and after structured labels such as **Goal:**, **KPI:**, and *Success signals:*; do not bury those labels inside a paragraph.", "tools": [ { "description": "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.", "inputSchema": { "properties": { "steps": { "description": "Ordered list of steps. 3-7 is ideal.", "items": { "properties": { "description": { "description": "1-2 sentence description. Supports markdown. Put \\n before and after structured labels such as **Goal:**, **KPI:**, and *Success signals:* so each label occupies its own line.", "type": "string" }, "icon": { "description": "Icon shown beside this item in Polished Presentation.", "enum": [ "user", "users", "user-plus", "user-check", "log-in", "log-out", "lock", "unlock", "key", "shield-check", "fingerprint", "mail", "send", "message-square", "bell", "phone", "building-2", "briefcase", "landmark", "store", "credit-card", "wallet", "receipt", "dollar-sign", "shopping-cart", "package", "truck", "gift", "check-circle", "x-circle", "alert-triangle", "info", "help-circle", "ban", "clock", "calendar", "timer", "hourglass", "file-text", "clipboard-check", "file-signature", "book-open", "folder", "database", "server", "cloud", "code", "git-branch", "git-merge", "terminal", "cpu", "bug", "settings", "sliders-horizontal", "search", "filter", "eye", "upload", "download", "refresh-cw", "repeat", "link", "share-2", "rocket", "flag", "target", "trophy", "star", "thumbs-up", "heart", "sparkles", "zap", "bar-chart-3", "trending-up", "trending-down", "pie-chart", "activity", "layout-dashboard", "home", "globe", "map-pin", "smartphone", "monitor", "list-checks", "layers", "inbox", "archive", "handshake", "lightbulb", "megaphone", "graduation-cap" ], "type": "string" }, "id": { "description": "Short unique ID (lowercase, underscores). Optional.", "type": "string" }, "key": { "description": "true on the single item the audience should remember (one per chart, 4+ items).", "type": "boolean" }, "label": { "description": "Short step name (1-4 words). Supports markdown.", "type": "string" } }, "required": [ "label" ], "type": "object" }, "type": "array" }, "title": { "description": "Chart title shown in the app and share page.", "type": "string" } }, "required": [ "title", "steps" ], "type": "object" }, "name": "create_chevron_chart", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "entities": { "description": "Entities (tables). 2-8 is ideal.", "items": { "properties": { "attributes": { "description": "Typed fields, keys first.", "items": { "properties": { "comment": { "description": "Optional short note.", "type": "string" }, "key": { "description": "'PK', 'FK', 'UK', or comma list. Omit for plain fields.", "type": "string" }, "name": { "description": "Field name, e.g. 'customer_id'.", "type": "string" }, "type": { "description": "e.g. 'string', 'int', 'date', 'decimal', 'bool'.", "type": "string" } }, "required": [ "type", "name" ], "type": "object" }, "type": "array" }, "name": { "description": "Entity name, e.g. 'CUSTOMER'. Letters/digits/underscores only.", "type": "string" } }, "required": [ "name" ], "type": "object" }, "type": "array" }, "relationships": { "description": "Relationships with cardinality.", "items": { "properties": { "cardinality": { "enum": [ "one-to-one", "one-to-many", "many-to-one", "many-to-many" ], "type": "string" }, "from": { "description": "Source entity name.", "type": "string" }, "label": { "description": "Verb phrase, e.g. 'places', 'contains'.", "type": "string" }, "to": { "description": "Target entity name.", "type": "string" } }, "required": [ "from", "to", "cardinality" ], "type": "object" }, "type": "array" }, "title": { "description": "Chart title shown in the app and share page.", "type": "string" } }, "required": [ "title", "entities" ], "type": "object" }, "name": "create_erd_chart", "outputSchema": null }, { "description": "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).", "inputSchema": { "properties": { "mermaid": { "description": "Mermaid flowchart source code.", "type": "string" }, "title": { "description": "Chart title shown in the app and share page.", "type": "string" } }, "required": [ "title", "mermaid" ], "type": "object" }, "name": "create_flowchart", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "conversionRates": { "description": "Conversion percentages between adjacent stages (length = stages - 1), e.g. [75, 50, 30].", "items": { "type": "number" }, "type": "array" }, "stages": { "description": "Ordered stages from widest (top) to narrowest (bottom). 3-6 is ideal.", "items": { "properties": { "description": { "description": "1-2 sentence description shown beside the stage.", "type": "string" }, "icon": { "description": "Icon shown beside this item in Polished Presentation.", "enum": [ "user", "users", "user-plus", "user-check", "log-in", "log-out", "lock", "unlock", "key", "shield-check", "fingerprint", "mail", "send", "message-square", "bell", "phone", "building-2", "briefcase", "landmark", "store", "credit-card", "wallet", "receipt", "dollar-sign", "shopping-cart", "package", "truck", "gift", "check-circle", "x-circle", "alert-triangle", "info", "help-circle", "ban", "clock", "calendar", "timer", "hourglass", "file-text", "clipboard-check", "file-signature", "book-open", "folder", "database", "server", "cloud", "code", "git-branch", "git-merge", "terminal", "cpu", "bug", "settings", "sliders-horizontal", "search", "filter", "eye", "upload", "download", "refresh-cw", "repeat", "link", "share-2", "rocket", "flag", "target", "trophy", "star", "thumbs-up", "heart", "sparkles", "zap", "bar-chart-3", "trending-up", "trending-down", "pie-chart", "activity", "layout-dashboard", "home", "globe", "map-pin", "smartphone", "monitor", "list-checks", "layers", "inbox", "archive", "handshake", "lightbulb", "megaphone", "graduation-cap" ], "type": "string" }, "id": { "description": "Short unique ID. Optional.", "type": "string" }, "key": { "description": "true on the single item the audience should remember (one per chart, 4+ items).", "type": "boolean" }, "label": { "description": "Stage name (1-4 words). Supports markdown.", "type": "string" }, "value": { "description": "Metric shown below the label, e.g. '1,000 leads', '25%'.", "type": "string" } }, "required": [ "label" ], "type": "object" }, "type": "array" }, "title": { "description": "Chart title shown in the app and share page.", "type": "string" } }, "required": [ "title", "stages" ], "type": "object" }, "name": "create_funnel_chart", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "curveLabel": { "description": "Y-axis label (e.g. 'Value', 'Adoption').", "type": "string" }, "milestones": { "description": "4-8 milestones on the curve.", "items": { "properties": { "description": { "description": "Optional brief description (5-10 words).", "type": "string" }, "icon": { "description": "Icon shown beside this item in Polished Presentation.", "enum": [ "user", "users", "user-plus", "user-check", "log-in", "log-out", "lock", "unlock", "key", "shield-check", "fingerprint", "mail", "send", "message-square", "bell", "phone", "building-2", "briefcase", "landmark", "store", "credit-card", "wallet", "receipt", "dollar-sign", "shopping-cart", "package", "truck", "gift", "check-circle", "x-circle", "alert-triangle", "info", "help-circle", "ban", "clock", "calendar", "timer", "hourglass", "file-text", "clipboard-check", "file-signature", "book-open", "folder", "database", "server", "cloud", "code", "git-branch", "git-merge", "terminal", "cpu", "bug", "settings", "sliders-horizontal", "search", "filter", "eye", "upload", "download", "refresh-cw", "repeat", "link", "share-2", "rocket", "flag", "target", "trophy", "star", "thumbs-up", "heart", "sparkles", "zap", "bar-chart-3", "trending-up", "trending-down", "pie-chart", "activity", "layout-dashboard", "home", "globe", "map-pin", "smartphone", "monitor", "list-checks", "layers", "inbox", "archive", "handshake", "lightbulb", "megaphone", "graduation-cap" ], "type": "string" }, "id": { "description": "Short unique ID.", "type": "string" }, "key": { "description": "true on the single item the audience should remember (one per chart, 4+ items).", "type": "boolean" }, "label": { "description": "Milestone name (1-4 words).", "type": "string" }, "level": { "description": "1 (low) to 10 (high) — curve height at this point. Unless the user gives values, span most of the range and step at least 2 levels between neighbours so the shape is visible.", "type": "number" }, "phaseId": { "description": "ID of the phase this milestone belongs to.", "type": "string" } }, "required": [ "label", "level", "phaseId" ], "type": "object" }, "type": "array" }, "phases": { "description": "2-5 phases shown as headers.", "items": { "properties": { "id": { "description": "Short unique ID.", "type": "string" }, "label": { "description": "Phase name (1-3 words).", "type": "string" } }, "required": [ "label" ], "type": "object" }, "type": "array" }, "timeLabel": { "description": "X-axis label (e.g. 'Time').", "type": "string" }, "title": { "description": "Chart title shown in the app and share page.", "type": "string" } }, "required": [ "title", "phases", "milestones" ], "type": "object" }, "name": "create_lifecycle_chart", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "direction": { "description": "Layout direction; horizontal is default.", "enum": [ "horizontal", "vertical" ], "type": "string" }, "eras": { "description": "Optional named periods grouping events (background bands).", "items": { "properties": { "id": { "description": "Short unique ID.", "type": "string" }, "label": { "description": "Era name (1-3 words).", "type": "string" } }, "required": [ "label" ], "type": "object" }, "type": "array" }, "events": { "description": "Chronological events. 4-10 is ideal.", "items": { "properties": { "date": { "description": "Required timeline marker including units: 'Jan 15, 2027', 'Week 1', 'Second 5', or 'Phase 1'. Shared units are auto-extracted. Preserve supplied dates; disclose proposed relative timing as estimated; use ordinal phases for undated processes or TBD for unknown dates in an otherwise dated chart. Never fabricate factual dates/durations.", "minLength": 1, "type": "string" }, "description": { "description": "Brief 1-sentence description.", "type": "string" }, "eraId": { "description": "Optional era this event belongs to.", "type": "string" }, "icon": { "description": "Icon shown beside this item in Polished Presentation.", "enum": [ "user", "users", "user-plus", "user-check", "log-in", "log-out", "lock", "unlock", "key", "shield-check", "fingerprint", "mail", "send", "message-square", "bell", "phone", "building-2", "briefcase", "landmark", "store", "credit-card", "wallet", "receipt", "dollar-sign", "shopping-cart", "package", "truck", "gift", "check-circle", "x-circle", "alert-triangle", "info", "help-circle", "ban", "clock", "calendar", "timer", "hourglass", "file-text", "clipboard-check", "file-signature", "book-open", "folder", "database", "server", "cloud", "code", "git-branch", "git-merge", "terminal", "cpu", "bug", "settings", "sliders-horizontal", "search", "filter", "eye", "upload", "download", "refresh-cw", "repeat", "link", "share-2", "rocket", "flag", "target", "trophy", "star", "thumbs-up", "heart", "sparkles", "zap", "bar-chart-3", "trending-up", "trending-down", "pie-chart", "activity", "layout-dashboard", "home", "globe", "map-pin", "smartphone", "monitor", "list-checks", "layers", "inbox", "archive", "handshake", "lightbulb", "megaphone", "graduation-cap" ], "type": "string" }, "id": { "description": "Short unique ID. Optional.", "type": "string" }, "key": { "description": "true on the single item the audience should remember (one per chart, 4+ items).", "type": "boolean" }, "label": { "description": "Event name (1-5 words).", "type": "string" } }, "required": [ "label", "date" ], "type": "object" }, "type": "array" }, "title": { "description": "Chart title shown in the app and share page.", "type": "string" } }, "required": [ "title", "events" ], "type": "object" }, "name": "create_timeline_chart", "outputSchema": null }, { "description": "Permanently delete a chart you own.", "inputSchema": { "properties": { "chart_id": { "type": "string" } }, "required": [ "chart_id" ], "type": "object" }, "name": "delete_chart", "outputSchema": null }, { "description": "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?}).", "inputSchema": { "properties": { "chart_id": { "description": "Chart id from create_* / list_charts.", "type": "string" }, "mermaid": { "description": "Full replacement mermaid source (flowchart/ERD charts only).", "type": "string" }, "title": { "description": "New title (optional).", "type": "string" }, "tool_calls": { "description": "Ordered edit operations: [{tool, input}].", "items": { "properties": { "input": { "type": "object" }, "tool": { "type": "string" } }, "required": [ "tool", "input" ], "type": "object" }, "type": "array" } }, "required": [ "chart_id" ], "type": "object" }, "name": "edit_chart", "outputSchema": null }, { "description": "Fetch a chart's current spec (JSON) and editable source text, plus its share URL.", "inputSchema": { "properties": { "chart_id": { "type": "string" } }, "required": [ "chart_id" ], "type": "object" }, "name": "get_chart", "outputSchema": null }, { "description": "List your CalderFlow charts (id, title, type, share URL), newest first.", "inputSchema": { "properties": {}, "type": "object" }, "name": "list_charts", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:859573968cd7f6d93b294c487f5e6ae21ab56274e0b2843e141e9af3620a427f | sha256sum