_ registry / mcp streamable-http · checked 3h ago

urlchart

https://urlchart.com

Registry code: d77314c05475c1df

api record

UrlChart renders PNG charts from legacy Google Image Charts parameters. Use build_chart_url to compose a URL, generate_chart_image to render it, and check_legacy_chart_url to see what an existing (Google / Image-Charts / QuickChart) chart URL will look like on UrlChart before migrating. Renders without an api_key are free-tier: 1000 px per side / 1 MP canvas.

endpoint
https://urlchart.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is urlchart live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is urlchart free to use?
Yes — the hub reached it with no key and no payment.
What tools does urlchart have?
3 tools: generate_chart_image, build_chart_url, check_legacy_chart_url.
Is urlchart safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
359ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • generate_chart_image unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "params"
      ],
      "properties": {
        "params": {
          "oneOf": [
            {
              "type": "object",
              "additionalProperties": {
                "type": [
                  "string",
                  "number",
                  "boolean"
                ]
              }
            },
            {
              "type": "string"
            }
          ],
          "description": "Legacy chart parameters. Either an object of parameter name -> value (cht, chs, chd, chds, chl, chdl, chdlp, chxt, chxl, chxr, chxs, chxp, chxtc, chco, chtt, chts, chma, chg, chf, chbh, chls, chm (and chld/choe for cht=qr)), or a full chart URL / query string. Values may be strings or numbers."
        },
        "api_key": {
          "type": "string",
          "description": "Optional UrlChart API key (uc_live_… / uc_test_…). Omit to use the free tier. Alternatively send `Authorization: Bearer <key>` on the MCP request itself."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • build_chart_url unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "values"
      ],
      "properties": {
        "title": {
          "type": "string",
          "description": "Chart title (chtt)."
        },
        "width": {
          "type": "integer",
          "default": 400,
          "maximum": 3000,
          "minimum": 10
        },
        "y_max": {
          "type": "number",
          "description": "Y axis maximum (chxr). Requires y_min."
        },
        "y_min": {
          "type": "number",
          "description": "Y axis minimum (chxr). Requires y_max."
        },
        "colors": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Series colours as hex (with or without #) or legacy colour names (chco)."
        },
        "height": {
          "type": "integer",
          "default": 200,
          "maximum": 3000,
          "minimum": 10
        },
        "labels": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Category labels (chl): one per value for a single series. Omit for no labels. For scatter, labels are not used."
        },
        "values": {
          "oneOf": [
            {
              "type": "array",
              "items": {
                "type": "number"
              },
              "minItems": 1
            },
            {
              "type": "array",
              "items": {
                "type": "array",
                "items": {
                  "type": "number"
                },
                "minItems": 1
              },
              "minItems": 1
            }
          ],
          "description": "Data. For bar/line/pie/doughnut: one series (number[]) or several series (number[][]). For scatter: number[][] where the FIRST row is the x series and each further row a y series."
        },
        "background": {
          "type": "string",
          "description": "Background colour (chf=bg,s,…), hex or legacy name."
        },
        "chart_type": {
          "enum": [
            "bar",
            "bar-horizontal",
            "line",
            "pie",
            "doughnut",
            "scatter"
          ],
          "type": "string",
          "default": "bar",
          "description": "Chart family. Default bar (cht=bvg)."
        }
      },
      "additionalProperties": false
    }
    arguments 87 lines
  • check_legacy_chart_url unknown 3h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The full legacy chart URL, including https://."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d77314c05475c1df.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d77314c05475c1df/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d77314c05475c1df/badge.svg)](https://brick.blue/agent/d77314c05475c1df?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.