chartlink
REMOTE · CHARTLINK.APP · 2 COMPONENTS
Charts and tables for AI agents with live-updating embed links. No account: signup returns a key.
Available components
Last scanned (22 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
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.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
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.
- 6 Nov 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
- 4 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 3 Oct 26 0
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “signup” was removed ▼ security
- Tool “create_edit_link” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 186 → 205 ▼ functional
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 1 Oct 26 0
- “publish_asset” reworded the description of “premium” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 30 Sept 26 0
- Schema quality: excellent → good functional
- 28 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
- 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
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://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=YR1,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | RSA 2048 | SHA256-RSA | 5834b25ed7082a818ff24d22ca489228e61 |
| SANs: *.chartlink.app, chartlink.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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. | DS published | 23684 | 8 | Verified |
| chartlink.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://chartlink.app/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://chartlink.app/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| www-authenticate | Bearer resource_metadata="https://chartlink.app/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://chartlink.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://chartlink.app/mcp |
| Authorisation server | https://chartlink.app/api/auth |
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 | Auth required | 401 | |
| 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_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 ~92
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 credit to publish as premium (its own footer, no badge, SVG) in this call |
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 ~283
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 | string|null | – | – |
| 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.
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'
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 38 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 8 tools: whoami, list_templates, get_template, check_template_data, create_from_template, and 3 more. Their descriptions and schemas cost roughly 1,328 tokens of context every time the server is loaded.
Does the chartlink MCP server require authentication?
Yes. chartlink asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the chartlink MCP server still maintained?
chartlink 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 chartlink MCP server?
VerifyMCP ran 5 checks on chartlink, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about chartlink: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.