Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,528Letters: 13Defects: 1,322counted 4 min ago
teppi

Server definition

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

The blob, as servednamed by its sha256

{ "instructions": "chartlink makes charts and maps with live-updating embeds. No accounts: the API key is the workspace.\nTHE TEMPLATE LOOP (the default, four steps): list_templates {q: what the person asked for} → get_template {id} (its contract:\nknobs, columns, region codes, an example call) → create_from_template {template, data, knobs, publish: true} → hand back\nurls.embedIframe / urls.png / urls.page. Knobs are the template's few settings (theme, dataType, texts, scale); the design\nis the template's. No key on this connection? Ask your person for one from their chartlink studio (Workspace → Keys for your AI agents). The full engine (every chart type, the whole settings schema)\nis the advanced path: connect to /mcp?full=1 or read https://chartlink.app/llms-full.txt.\n\nThe engine loop, for the advanced path: list_asset_types → get_spec_schema(type) once (read its notes, examples and defaults, not just the schema) → create_asset {type, data, config} (a 201 means it validated AND rendered;\nthe preview image comes back inline) → update_asset with a small configPatch → publish_asset → hand back urls.embedIframe / urls.png / urls.page.\nNew numbers later: replace_asset_data (republishes every embed). A CSV/JSON URL that refreshes itself: set_data_source.\nPrefer a template: list_templates {q: what the person asked for} ranks them by need — take the first, then create_asset {template, data}. Maps: list_geographies before naming regions.\nHumans fine-tune in the studio (the chart is in their workspace: /studio/{brand}/chart/{id}), so keep configs lean:\none element per idea (a multi-colour headline is ONE title with [spans](#hex) and \n, not stacked texts[]; a grid is\nyAxis.gridlines, not reference lines), and 2–3 decimals for position fractions.\nThe inline preview is 640px: before judging a hairline, a gridline or a label, fetch /api/assets/{id}/preview.png?width=1600.\nNo key on this connection? Ask your person for one from their chartlink studio (Workspace → Keys for your AI agents). Manual: https://chartlink.app/llms.txt", "tools": [ { "description": "Matches every region value against the template's geography and reports unmatched values with the closest real codes, how many regions would stay grey, and the scale the map would use. No key needed. Use it when unsure of the codes; then create_from_template with the same data and knobs.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "data": { "additionalProperties": false, "description": "The data you intend to send", "properties": { "columns": { "items": { "additionalProperties": false, "properties": { "dateFormat": { "description": "For date columns whose strings are NOT ISO-ish: a strftime-style parse hint tried first — tokens %Y %m %d %b %B %q %H %M %S, e.g. \"%d/%m/%Y\" for \"15/03/2024\", \"%b %Y\" for \"Mar 2024\". Removes the day/month guess; ISO-ish strings never need it.", "type": "string" }, "id": { "description": "Column identifier referenced by encodings", "minLength": 1, "type": "string" }, "label": { "description": "Display label; defaults to id", "type": "string" }, "type": { "description": "date columns parse ISO-ish strings on their own: \"2024\", \"2024-03\", \"2024-03-15\", \"2024-Q2\", full ISO timestamps, or epoch numbers. Anything else needs dateFormat.", "enum": [ "string", "number", "date", "boolean" ], "type": "string" } }, "required": [ "id", "type" ], "type": "object" }, "minItems": 1, "type": "array" }, "rows": { "description": "Row-major values, one array per row, order matching columns", "items": { "items": { "type": [ "string", "number", "boolean", "null" ] }, "type": "array" }, "type": "array" } }, "required": [ "columns", "rows" ], "type": "object" }, "knobs": { "additionalProperties": {}, "propertyNames": { "type": "string" }, "type": "object" }, "template": { "description": "Template id, slug, or page address (sweden/municipalities)", "type": "string" } }, "required": [ "template", "data" ], "type": "object" }, "name": "check_template_data", "outputSchema": null }, { "description": "The template's design, your data, your words. `knobs` are the template's settings (get_template shows the schema): theme light|dark|editorial, dataType gradient|buckets|categories and surroundings true|false (then waterColor, landColor) for maps, title/description/source/brand {text, fontFamily, fontSize, color}, backgroundColor, and the scale knobs for the dataType (colormap and direction, range, breaks or classes, categoryColors/categoryOrder). data = {columns: [{id, type}], rows: [[…]]}: use the template's column ids, or exactly two columns (region first, value second) for a map. publish: true makes the URLs live in the same call. A success means it validated AND rendered — look at the preview. Region values that match nothing come back as a 400 listing each with its closest real codes, before anything is made — no separate check needed. `config` is the advanced path: the engine's settings, merged after the knobs.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "config": { "additionalProperties": {}, "description": "ADVANCED: engine settings deep-merged after the knobs", "propertyNames": { "type": "string" }, "type": "object" }, "data": { "additionalProperties": false, "description": "Typed columns + row-major rows, shaped like the template's example", "properties": { "columns": { "items": { "additionalProperties": false, "properties": { "dateFormat": { "description": "For date columns whose strings are NOT ISO-ish: a strftime-style parse hint tried first — tokens %Y %m %d %b %B %q %H %M %S, e.g. \"%d/%m/%Y\" for \"15/03/2024\", \"%b %Y\" for \"Mar 2024\". Removes the day/month guess; ISO-ish strings never need it.", "type": "string" }, "id": { "description": "Column identifier referenced by encodings", "minLength": 1, "type": "string" }, "label": { "description": "Display label; defaults to id", "type": "string" }, "type": { "description": "date columns parse ISO-ish strings on their own: \"2024\", \"2024-03\", \"2024-03-15\", \"2024-Q2\", full ISO timestamps, or epoch numbers. Anything else needs dateFormat.", "enum": [ "string", "number", "date", "boolean" ], "type": "string" } }, "required": [ "id", "type" ], "type": "object" }, "minItems": 1, "type": "array" }, "rows": { "description": "Row-major values, one array per row, order matching columns", "items": { "items": { "type": [ "string", "number", "boolean", "null" ] }, "type": "array" }, "type": "array" } }, "required": [ "columns", "rows" ], "type": "object" }, "knobs": { "additionalProperties": {}, "description": "The template's knobs — get_template returns their schema", "propertyNames": { "type": "string" }, "type": "object" }, "publish": { "description": "true = published and live in this call; omit while you iterate", "type": "boolean" }, "template": { "description": "Template id or slug from list_templates, or the page address (sweden/municipalities, us/texas/counties, london/wards) when you know the place", "type": "string" } }, "required": [ "template", "data" ], "type": "object" }, "name": "create_from_template", "outputSchema": null }, { "description": "Read this before create_from_template. Returns the template with `contract`: its looks (theme × dataType × surroundings), the knobs JSON Schema, the columns with their roles, the region-code convention with three real codes and a lookup URL, what each dataType expects of the value column, and a complete example call whose shape you copy. Takes an id, the page slug, or the page address as on chartlink.app/maps — sweden/municipalities, us/texas/counties, london/wards — so you can skip list_templates when you know the place.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "id": { "description": "Template id (ast_…), slug, or page address (place/level)", "type": "string" } }, "required": [ "id" ], "type": "object" }, "name": "get_template", "outputSchema": null }, { "description": "Templates are named by the NEED they answer (need, asks, tags), each with urls.png (show it to your human) and `columns`: the column ids your data must supply. Pass q with what the person asked for — \"map of brazil's states\", \"ranked bars with flags\", \"change between two years\" — and the list comes back ranked; take the first. Then create_asset with template: <id> and your data — the whole design comes along. Any chart id you were shown works as a template too, not only these.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "description": "At most this many, best first (default 20)", "maximum": 200, "minimum": 1, "type": "integer" }, "q": { "description": "What is needed, in the person's words", "type": "string" }, "tags": { "description": "Comma-separated tags every result must carry, e.g. map,united-states", "type": "string" }, "type": { "description": "Only this asset type, e.g. \"bar\"", "type": "string" } }, "type": "object" }, "name": "list_templates", "outputSchema": null }, { "description": "Makes the draft live. Returns urls: paste urls.embedIframe on iframe platforms; on Substack insert urls.png as an image and link it to urls.page. Pinned history: urls.png + '?v=N'.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "id": { "type": "string" }, "note": { "type": "string" }, "premium": { "description": "Spend one credit to publish as premium (its own footer, no badge, SVG) in this call", "type": "boolean" } }, "required": [ "id" ], "type": "object" }, "name": "publish_asset", "outputSchema": null }, { "description": "If a capability is missing, a schema fights you, or docs are wrong: record it here so the owner can fix it. One report per distinct issue, with a real description — reports get fixed same-day when they say what you tried, what you expected, and what happened (title-only reports can't be acted on).", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "assetId": { "type": "string" }, "description": { "description": "What you tried, what you expected, what happened instead — include the asset id if one is involved", "minLength": 40, "type": "string" }, "title": { "type": "string" }, "type": { "enum": [ "bug", "feature_request", "limitation", "documentation_gap", "other" ], "type": "string" } }, "required": [ "type", "title", "description" ], "type": "object" }, "name": "submit_feedback", "outputSchema": null }, { "description": "configPatch is DEEP-MERGED: objects merge recursively, arrays replace wholesale, null clears a key — send only what changes. To REMOVE keys (drop document.aspect, delete one of texts[]) pass `config` instead: it REPLACES the whole config (get_asset returns the current one to edit). `data` (if given) replaces rows wholesale. Requires expectedVersion from the last envelope; on 409 re-merge onto the returned `current`. Updating does NOT publish by default — pass publish: true to publish in the same call, or call publish_asset separately.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "brand": { "type": [ "string", "null" ] }, "config": { "additionalProperties": {}, "description": "REPLACES the whole config — the way to remove keys; applied before configPatch if both are given", "propertyNames": { "type": "string" }, "type": "object" }, "configPatch": { "additionalProperties": {}, "description": "Deep-merged onto the current config", "propertyNames": { "type": "string" }, "type": "object" }, "data": { "additionalProperties": false, "description": "Typed columns + row-major rows. A date column whose strings are not ISO-ish takes dateFormat (e.g. \"%d/%m/%Y\").", "properties": { "columns": { "items": { "additionalProperties": false, "properties": { "dateFormat": { "description": "For date columns whose strings are NOT ISO-ish: a strftime-style parse hint tried first — tokens %Y %m %d %b %B %q %H %M %S, e.g. \"%d/%m/%Y\" for \"15/03/2024\", \"%b %Y\" for \"Mar 2024\". Removes the day/month guess; ISO-ish strings never need it.", "type": "string" }, "id": { "description": "Column identifier referenced by encodings", "minLength": 1, "type": "string" }, "label": { "description": "Display label; defaults to id", "type": "string" }, "type": { "description": "date columns parse ISO-ish strings on their own: \"2024\", \"2024-03\", \"2024-03-15\", \"2024-Q2\", full ISO timestamps, or epoch numbers. Anything else needs dateFormat.", "enum": [ "string", "number", "date", "boolean" ], "type": "string" } }, "required": [ "id", "type" ], "type": "object" }, "minItems": 1, "type": "array" }, "rows": { "description": "Row-major values, one array per row, order matching columns", "items": { "items": { "type": [ "string", "number", "boolean", "null" ] }, "type": "array" }, "type": "array" } }, "required": [ "columns", "rows" ], "type": "object" }, "expectedVersion": { "maximum": 9007199254740991, "minimum": 1, "type": "integer" }, "id": { "type": "string" }, "publish": { "description": "true = publish immediately after this update succeeds (one call instead of two)", "type": "boolean" }, "showcase": { "description": "Offer this chart as a template in the public gallery and list_templates (once published). Workspace keys only.", "type": "boolean" }, "title": { "type": "string" } }, "required": [ "id", "expectedVersion" ], "type": "object" }, "name": "update_asset", "outputSchema": null }, { "description": "Returns key name + workspace. Call this first — non-destructive auth check. Everything you write is stamped createdBy/updatedBy = key name.", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": {}, "type": "object" }, "name": "whoami", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:ace1dc2a82c47b422798df0fe5a802327950db6e2f86c2390e3c391aa21354f8 | sha256sum