Skip to main content
Glama

UrlChart

Server Details

Render charts as PNG images from a URL — Google Image Charts / Image-Charts compatible API.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
gowinder/urlchart-mcp
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool maps to a distinct stage: building a UrlChart URL from a spec, auditing a legacy URL for migration, and rendering a PNG. The descriptions explicitly cross-reference each other (build_chart_url → generate_chart_image, check_legacy_chart_url is analysis-only, generate_chart_image is the renderer), leaving little room for misselection. Even the overlapping 'legacy parameter' input path is explicitly attributed to generate_chart_image only.

Naming Consistency5/5

All three tools follow a uniform snake_case verb_noun pattern: build_chart_url, check_legacy_chart_url, generate_chart_image. The shared '_chart_url'/'chart' suffix reinforces the domain and makes the family obvious.

Tool Count5/5

Three tools is a tight, well-earned surface: one for authoring, one for read-only migration analysis, one for rendering. Nothing appears redundant, and the split between pure-URL computation and network rendering justifies separate tools rather than one overloaded entry point.

Completeness4/5

The build → audit → render lifecycle is covered end to end, including free/paid tier and format handling in the renderer. Minor gap: there is no tool to validate or introspect an existing UrlChart URL (the analyser only targets legacy formats), so agents auditing their own generated URLs must rely on rendering feedback. That is a small, workable gap rather than a dead end.

Available Tools

3 tools
build_chart_urlBuild a chart URLAInspect

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.

Inputs: values (required), title, width, y_max, +6 more.

check_legacy_chart_urlCheck a legacy chart URLAInspect

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).

Inputs: url (required).

generate_chart_imageGenerate a chart imageAInspect

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.

Inputs: params (required), api_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.