UrlChart MCP server
io.github.gowinder/urlchartgowinderstreamable-httpv1.0.1Scanned
Render charts as PNG images from a URL — Google Image Charts / Image-Charts compatible API.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the UrlChart MCP server can do
The UrlChart MCP server is published by the GitHub account gowinder. It has 3 tools. It can create or change data (3 tools: generate_chart_image, check_legacy_chart_url and build_chart_url), but cannot delete data. None of its tools only reads.
1 tool can send data out of your system (check_legacy_chart_url).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 3Claude Code: ask
build_chart_urlBuild a well-formed UrlChart chart URL from a small, LLM-friendly chart spec.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Build a well-formed UrlChart chart URL from a small, LLM-friendly chart spec. No render, no network, no key. Returns the URL as text; pass it to generate_chart_image (or embed it) to get the PNG. For chart types or parameters outside this spec, use generate_chart_image with raw legacy parameters.
check_legacy_chart_urlThe migration check: analyse a Google Image Charts / Image-Charts / QuickChart URL and report, parameter by parameter, what UrlChart will render, degrade, ignore or not support — p…Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it The migration check: analyse a Google Image Charts / Image-Charts / QuickChart URL and report, parameter by parameter, what UrlChart will render, degrade, ignore or not support — plus the equivalent UrlChart URL. Computed from the URL alone: NOTHING is rendered and no request is made to the chart host. Use this before migrating an embed to find out what changes (for example a multi-axis URL that an alternative charts it only on a paid plan).
generate_chart_imageRender a PNG chart through UrlChart and return the image plus its hosted URL.1 finding
Why it is in this group
- The name "generate_chart_image" says "generate": a word for a change.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...xt result is the same chart without any credential, so embedding it publicly serves the FR..."
Description, as the server wrote it Render a PNG chart through UrlChart and return the image plus its hosted URL. Accepts Google Image Charts / legacy parameters as an object (`{"cht":"bvg","chs":"400x200","chd":"t:10,40,80"}`) or a full legacy chart URL (Google, Image-Charts, QuickChart or urlchart.com). Without an api_key (or an Authorization: Bearer header on this MCP connection) the render is the FREE tier: a canvas of at most 1000 px per side / 1 MP, 60 requests/minute and 1,000 unique renders/month per IP. A request above that canvas is scaled down and reported in X-UrlChart-Meta, never failed. A paid api_key keeps the full 9 MP canvas (3000 px per side) and applies the paid limits. Parameters that are unknown or not implemented never fail the render; they degrade and are reported in X-UrlChart-Meta. chof=jpg|webp|pdf requests another output format; a PDF result is returned as a hosted URL (not an image block). The hosted URL in the text result is the same chart without any credential, so embedding it publicly serves the FREE (capped-canvas) variant unless a key or signed URL is added.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://urlchart.com/mcp: tools/list returned 3 tools to an anonymous client, including generate_chart_image (write), check_legacy_chart_url (write), build_chart_url (write)
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credential".
What this check looks forMatched text
description: "...xt result is the same chart without any credential, so embedding it publicly serves the FR..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http urlchart https://urlchart.com/mcpclaude mcp add --transport http urlchart https://urlchart.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__urlchart__generate_chart_image",
"mcp__urlchart__check_legacy_chart_url",
"mcp__urlchart__build_chart_url"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as urlchart. Review it before you use it.
Capability tags behind 1 rule
- mcp__urlchart__check_legacy_chart_url outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.gowinder/urlchart/verify?hash=5bd9905433c10648469fef65cd0b40391e2e1b1945add2ce8889de99b875f749" | jq -e '.changed == false'Pinned hash 5bd9905433c1, from Nov 20, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.gowinder/urlchart/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.gowinder/urlchart)Source: MCP Registry · repository. Synced Nov 20, 2026, 02:17 UTC.
UrlChart MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the UrlChart MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the UrlChart MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the UrlChart MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the UrlChart MCP server have?
- 3 tools: 3 write. generate_chart_image, check_legacy_chart_url and build_chart_url.
Does the UrlChart MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the UrlChart MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_legacy_chart_url.
Has the UrlChart MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.