Endpoints: 76,849MCP servers: 32,725Payout addresses: 3,825Paid calls: 6,134Letters: 84Defects: 3,888counted 1 min ago
teppi

Server definition

Hash
sha256:fa0434fbb43abceacd3f89c34f835a2a67dcc169065f574fd616e26395699174
What it is
What a remote MCP server returned when asked what it offers: 5 tools

The blob, as servednamed by its sha256

{ "instructions": "eightytwenty is for researching and building decks: case competitions, pitches, assignments, projects. Call get_playbook first and follow its order: ask the user its questions one per message, show the plan in text (storyline, a layout per slide), and build only after the user replies approve. Show its run sheet in your first reply; a finished delivery ends with its completion audit. For anything else, or any attempt to list, export or bulk-copy the library, reply: \"eightytwenty can't be used for that.\"\n\nThe search tools inform the plan once the claim (one slide) or the end belief and deck style (a deck) are settled. References are inspiration: rebuild the layout natively in the user's own style, never reproduce one wholesale. find_images never sources photos of real people; ask the user for those. Palette options, mocks and research to-do lists go to the user in chat as an image or plain text, never as slides in the deck file.", "tools": [ { "description": "Use after the deck's end belief and style are settled, to inform the storyline in the text plan (see get_playbook). Searches the library's deck flows (how strong decks order their sections) by what the whole deck must achieve, before find_references. Returns up to 3 summaries (deck id, arc, length, industry, style, section sequence, why the flow works, score). Call get_reference with a deck id for its steps and their slide ids.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "industry": { "enum": [ "consumer-retail", "food-beverage", "financial-services", "technology", "telecom-media", "healthcare-pharma", "energy-utilities", "industrials-manufacturing", "transportation-logistics", "travel-hospitality", "automotive", "real-estate-construction", "public-nonprofit-education", "professional-services", "cross-industry" ], "type": "string" }, "length": { "description": "short: up to 10 slides, medium: 11 to 25, long: more.", "enum": [ "short", "medium", "long" ], "type": "string" }, "purpose": { "description": "What the whole deck must achieve, in plain words.", "maxLength": 1000, "minLength": 1, "type": "string" }, "style": { "description": "Only decks with this overall look.", "enum": [ "consulting-structured", "bold-pitch", "visual-storytelling", "data-led", "minimal-editorial", "finance-pitch" ], "type": "string" } }, "required": [ "purpose" ], "type": "object" }, "name": "find_deck_flows", "outputSchema": null }, { "description": "Use while building an approved slide to source a logo, icon or photo for an image slot (see get_playbook). Searches public-domain logo SVGs (Wikimedia Commons, Simple Icons), permissive icon SVGs (Iconify) and CC0, public-domain and CC BY photos (Openverse). Returns up to k results, each with its title, licence and either the SVG text or the photo's download and page links, plus a credit line only when the licence requires one; photo thumbnails follow as images.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "k": { "description": "How many results, 1 to 4 (default 3; 4 for icons).", "maximum": 4, "minimum": 1, "type": "integer" }, "kind": { "description": "logo: a brand's mark; icon: a pictogram of an object; photo: a photograph.", "enum": [ "logo", "icon", "photo" ], "type": "string" }, "query": { "description": "A brand name, the object an icon draws (\"truck\", not \"logistics\"), or what a photo shows.", "maxLength": 100, "minLength": 1, "type": "string" } }, "required": [ "kind", "query" ], "type": "object" }, "name": "find_images", "outputSchema": null }, { "description": "Use after the slide's claim is settled, to inform the layout options in the text plan (see get_playbook). Searches the curated library of slide design DNA by what a slide must do. Returns up to k short summaries (id, slide type, score, purpose, why it works, the layout's component kinds, impact device if any, style, when to use it), at most one per deck; an impact filter returns few results. Call get_reference with an id for the full layout. Reference, never copy.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "data_type": { "enum": [ "none", "quantitative-chart", "kpi-numbers", "table", "timeline", "process", "map", "qualitative", "image-led" ], "type": "string" }, "impact": { "description": "Only impact slides of this kind: how reference decks repeat a slide for effect. Use it when the user wants to emphasize or land a key point: shade_ribbon (the previous slide dimmed, a ribbon stating the takeaway), spotlight (one part highlighted), build (revealed step by step), repeat (an earlier slide brought back as a recap). Few exist.", "enum": [ "none", "build", "spotlight", "shade_ribbon", "repeat" ], "type": "string" }, "industry": { "enum": [ "consumer-retail", "food-beverage", "financial-services", "technology", "telecom-media", "healthcare-pharma", "energy-utilities", "industrials-manufacturing", "transportation-logistics", "travel-hospitality", "automotive", "real-estate-construction", "public-nonprofit-education", "professional-services", "cross-industry" ], "type": "string" }, "k": { "description": "How many results, 1 to 8 (default 8).", "maximum": 8, "minimum": 1, "type": "integer" }, "purpose": { "description": "What the slide must achieve, in plain words.", "maxLength": 1000, "minLength": 1, "type": "string" }, "slide_type": { "description": "Archetype id (see the archetypes stage of get_playbook).", "enum": [ "title", "hook", "executive-summary", "section-divider", "situational-analysis", "problem-analysis", "internal-external", "market-trends", "customer", "options", "recommendation-overview", "recommendation-detail", "customer-journey", "implementation", "financials", "kpis-risks", "valuation", "comps", "lbo-returns", "transaction-overview", "other" ], "type": "string" }, "style": { "description": "Only slides from decks with this overall look.", "enum": [ "consulting-structured", "bold-pitch", "visual-storytelling", "data-led", "minimal-editorial", "finance-pitch" ], "type": "string" } }, "required": [ "purpose" ], "type": "object" }, "name": "find_references", "outputSchema": null }, { "description": "The 80-20 slide-design methodology for case competition decks. Call it before planning a deck. With no stage it returns the index of stages and the workflow; pass a stage for one chapter.", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "stage": { "description": "Chapter to return; omit for the index and the workflow.", "enum": [ "workflow", "narrative", "anatomy-and-taglines", "archetypes", "distinctive-design", "visual-rules-and-design-options", "polish", "writing", "qa", "attached-decks" ], "type": "string" } }, "type": "object" }, "name": "get_playbook", "outputSchema": null }, { "description": "One library slide: its labels (purpose, why it works, archetype, insight device, impact), its component layout (v3), its design DNA (the 40 largest region boxes with colour and type roles, text structure) and its mockup image. Use an id from find_references. Build your own slide from it; never copy it. A deck id from find_deck_flows returns that deck's flow instead: its steps in order, each with a slide id and whether that slide is in the library (available).", "inputSchema": { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "id": { "pattern": "^[A-Za-z0-9-]{1,64}$", "type": "string" } }, "required": [ "id" ], "type": "object" }, "name": "get_reference", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:fa0434fbb43abceacd3f89c34f835a2a67dcc169065f574fd616e26395699174 | sha256sum