chartlink
REMOTE · CHARTLINK.APP · 2 COMPONENTS · SCANNED SEP 26
Charts and tables for AI agents with live-updating embed links. No account: signup returns a key.
Available components
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (check_template_data). See how to fix → View diagnostics → Fail
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2058 tokens (~187/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 Management0
- Stability check failed: schema churn in the 11 days we've observed: 19 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- 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
How do I install the chartlink MCP server?
chartlink is a hosted endpoint at https://chartlink.app/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 · chartlink.app
claude mcp add --transport http oscarleoo-chartlink 'https://chartlink.app/mcp'
{
"mcpServers": {
"oscarleoo-chartlink": {
"url": "https://chartlink.app/mcp"
}
}
} {
"servers": {
"oscarleoo-chartlink": {
"type": "http",
"url": "https://chartlink.app/mcp"
}
}
} [mcp_servers.oscarleoo-chartlink] url = "https://chartlink.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"oscarleoo-chartlink": {
"type": "remote",
"url": "https://chartlink.app/mcp",
"enabled": true
}
}
} openclaw mcp add oscarleoo-chartlink --url 'https://chartlink.app/mcp' --transport streamable-http
mcp_servers:
oscarleoo-chartlink:
url: "https://chartlink.app/mcp" {
"McpServers": {
"oscarleoo-chartlink": {
"Transport": "http",
"Url": "https://chartlink.app/mcp"
}
}
} assistant mcp add oscarleoo-chartlink -t streamable-http -u 'https://chartlink.app/mcp'
{
"mcpServers": {
"oscarleoo-chartlink": {
"type": "http",
"url": "https://chartlink.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −1
- Tool “get_template” rewrote its description, which is the text the model reads security
- Tool “create_from_template” rewrote its description, which is the text the model reads security
- “get_template” reworded the description of “id” cosmetic
- “create_from_template” reworded the description of “template” cosmetic
- “check_template_data” reworded the description of “template” cosmetic
- 23 Sept 26 −3
- Stability: 0.23 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “create_checkout_link” was removed ▼ security
- Tool “delete_asset” was removed ▼ security
- Tool “duplicate_asset” was removed ▼ security
- Tool “fetch_data_source” was removed ▼ security
- Tool “get_asset” was removed ▼ security
- Tool “get_billing” was removed ▼ security
- Tool “get_spec_schema” was removed ▼ security
- Tool “list_asset_types” was removed ▼ security
- Tool “list_assets” was removed ▼ security
- Tool “list_brands” was removed ▼ security
- Tool “list_geographies” was removed ▼ security
- Tool “replace_asset_data” was removed ▼ security
- Tool “revoke_edit_link” was removed ▼ security
- Tool “set_data_source” was removed ▼ security
- Tool “unpublish_asset” was removed ▼ security
- Tool “update_brand” was removed ▼ security
- Tool “upgrade_to_premium” was removed ▼ security
- Tool “clear_data_source” was removed ▼ security
- Tool “create_asset” was removed ▼ security
- Tool “create_brand” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “check_template_data”, which the server declares destructive security
- Schema quality: 120 → 174 ▼ functional
- Tool coverage: 53% → 69% ▲ functional
- Schema quality: good → excellent functional
- New tool “create_from_template” functional
- New tool “get_template” functional
- “list_templates” added an optional parameter “limit” cosmetic
- “list_templates” added an optional parameter “tags” cosmetic
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_geographies” rewrote its description, which is the text the model reads security
- Tool “list_templates” rewrote its description, which is the text the model reads security
- Tool “set_data_source” is now declared destructive security
- Tool “clear_data_source” is now declared destructive security
- Tool “fetch_data_source” is now declared destructive security
- Tool “publish_asset” is now declared destructive security
- Tool “replace_asset_data” is now declared destructive security
- Tool “revoke_edit_link” is now declared destructive security
- Tool “update_asset” is now declared destructive security
- Tool “update_brand” is now declared destructive security
- Tool “upgrade_to_premium” is now declared destructive security
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- Destructive annotations: All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- New prompt “make-a-chart” functional
- New resource “manual” functional
- “list_templates” added an optional parameter “q” cosmetic
- “replace_asset_data” added an optional parameter “config” cosmetic
- Tool “list_templates” changed its title: Charts offered as templates — start a new chart from one → Templates by need — search, then start a chart from the best match cosmetic
- 18 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “update_brand” reworded the description of “tokens” cosmetic
- “create_brand” reworded the description of “tokens” cosmetic
- 17 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_asset” rewrote its description, which is the text the model reads security
- Tool “create_edit_link” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 47% → 52% ▲ functional
- New tool “signup” functional
- “replace_asset_data” reworded the description of “data” cosmetic
- “update_asset” reworded the description of “data” cosmetic
- 16 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- New tool “list_geographies” functional
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 26 Sept 2026 · Probed https://chartlink.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.chartlink.app | CN=YR2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 5af48e9c9c619cacf244efc60890bb8e41e |
| SANs: *.chartlink.app, chartlink.app | ||||||
| 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 chartlink.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| chartlink.app. | absent | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chartlink.app/mcp | Verified | 200 | |
| http (plaintext) | http://chartlink.app/mcp | HTTPS enforced | 308 | https://chartlink.app/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 →
check_template_data Dry run: would this data and these knobs work with the template? Creates nothing ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | The data you intend to send |
| knobs | object | – | – |
| template | string | yes | Template id, slug, or page address (sweden/municipalities) |
No output schema declared.
No examples provided.
create_edit_link Mint a no-login tweak link — hand it to your human ~137
Returns a URL opening the visual tweak panel for ONE chart (text, colors, spacing, label nudges) with no login. PUBLISH FIRST: the editor saves and republishes a published chart, it cannot publish a draft. Scope: view, tweak, and republish that chart only — never delete, never spend credits, nothing else in the workspace. OFFER THIS whenever the human's request is aesthetic fine-tuning: handing over the wheel beats a nudge-by-nudge back-and-forth. The secret is shown once; links don't expire and can be revoked with revoke_edit_link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ast_... |
No output schema declared.
No examples provided.
create_from_template Create a chart from a template with your data and a few knobs — returns an inline preview ~341
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.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | ADVANCED: engine settings deep-merged after the knobs |
| data | object | yes | Typed columns + row-major rows, shaped like the template's example |
| knobs | object | – | The template's knobs — get_template returns their schema |
| publish | boolean | – | true = published and live in this call; omit while you iterate |
| template | string | yes | Template id or slug from list_templates, or the page address (sweden/municipalities, us/texas/counties, london/wards) when you know the place |
No output schema declared.
No examples provided.
get_template One template's contract: knobs, columns, region codes, an example call ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Template id (ast_…), slug, or page address (place/level) |
No output schema declared.
No examples provided.
list_templates Templates by need — search, then start a chart from the best match ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | At most this many, best first (default 20) |
| q | string | – | What is needed, in the person's words |
| tags | string | – | Comma-separated tags every result must carry, e.g. map,united-states |
| type | string | – | Only this asset type, e.g. "bar" |
No output schema declared.
No examples provided.
publish_asset Publish — snapshot a version and update every embed ~96
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| note | string | – | – |
| premium | boolean | – | Spend one paid credit to publish as premium (2400px, SVG, your branding, no badge) in this call |
No output schema declared.
No examples provided.
signup Get an API key — no account, one call ~106
Creates a workspace and returns its API key (shown ONCE — keep it). Works on a keyless connection; every other tool needs the key. Then put the key where your client keeps it (plugin api_key setting, the Authorization header, or CHARTLINK_API_KEY for the npx bridge) and reconnect.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A name for the workspace (the project, the newsletter…) |
| ref | string | – | Where you heard of chartlink — free text |
No output schema declared.
No examples provided.
submit_feedback Report a gap — don't silently give up ~122
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).
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | – | – |
| description | string | yes | What you tried, what you expected, what happened instead — include the asset id if one is involved |
| title | string | yes | – |
| type | string | yes | – |
No output schema declared.
No examples provided.
update_asset Update a draft (deep-merge patch, or replace the config) — returns an inline preview image ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| config | object | – | REPLACES the whole config — the way to remove keys; applied before configPatch if both are given |
| configPatch | object | – | Deep-merged onto the current config |
| data | object | – | Typed columns + row-major rows. A date column whose strings are not ISO-ish takes dateFormat (e.g. "%d/%m/%Y"). |
| expectedVersion | integer | yes | – |
| id | string | yes | – |
| publish | boolean | – | true = publish immediately after this update succeeds (one call instead of two) |
| showcase | boolean | – | Offer this chart as a template in the public gallery and list_templates (once published). Workspace keys only. |
| title | string | – | – |
No output schema declared.
No examples provided.
whoami Verify your API key ~38
Returns key name + workspace. Call this first — non-destructive auth check. Everything you write is stamped createdBy/updatedBy = key name.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the chartlink MCP server?
chartlink is an MCP server listed in the public MCP registry as io.github.oscarleoo/chartlink. Charts and tables for AI agents with live-updating embed links. No account: signup returns a key. This page covers its hosted endpoint (https://chartlink.app/mcp).
Is the chartlink MCP server safe to use?
chartlink scores 66 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 chartlink MCP server expose?
chartlink exposes 10 tools: signup, whoami, list_templates, get_template, check_template_data, and 5 more. Their descriptions and schemas cost roughly 1,572 tokens of context every time the server is loaded.
Does the chartlink MCP server require authentication?
No. We connected to chartlink without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the chartlink MCP server still maintained?
chartlink is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.