_ registry / mcp http-sse · checked 1h ago

vectosolve

https://vectosolve.com

Registry code: 6a5b7920d212d91d

api record

VectoSolve turns raster images (PNG, JPG, WebP, GIF, including images generated in this conversation) into clean vector files. vectorize returns a rendered preview and the complete file: SVG for design tools, DXF for laser cutters, CNC and CAD, or EPS for print and sign-making. Use mode "laser" or "cricut" for cutting machines, "centerline" for scanned drawings and line art that must become single strokes.

endpoint
https://vectosolve.com/api/mcp
protocol
http-sse ·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 vectosolve live?
Yes — it answered the hub's last check (checked 1h ago).
Is vectosolve free to use?
Not measured yet.
What tools does vectosolve have?
1 tool: vectorize.
Is vectosolve 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
100%
latency
343ms

last good check

priced tools
0

of 1 tools

_ 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

_ what it can do 1 tools
1 never probed 0 of 1 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.

  • vectorize unknown 1h ago

    Convert a raster image (PNG, JPG, WebP or GIF, up to 10 MB) into a vector file. Returns a rendered PNG preview of the result and the complete file source as text, ready to save as .svg, .dxf or .eps. Input: image_url, a public http(s) link to the image; in ChatGPT, an image attached to the conversation arrives as the image file instead. Modes: "standard" (logos, illustrations, AI-generated art), "laser" (closed cut paths for laser cutters), "cricut" (cutting machines), "centerline" (one stroke per line: scanned drawings, line art, single-line lettering; photos and filled shapes are refused). Formats: "svg" (default), "dxf" (R12 polylines in millimetres, for laser, CNC and CAD), "eps" (print and sign-making). Very detailed images such as photos can give a file too large to return in the conversation. A conversion takes about 5 to 20 seconds.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "mode": {
          "enum": [
            "standard",
            "laser",
            "cricut",
            "centerline"
          ],
          "type": "string",
          "default": "standard",
          "description": "Tracing mode: \"standard\" for logos, illustrations and AI art; \"laser\" for closed cut paths; \"cricut\" for cutting machines; \"centerline\" for single strokes on line art and scanned drawings."
        },
        "image": {
          "type": "object",
          "required": [
            "download_url",
            "file_id"
          ],
          "properties": {
            "file_id": {
              "type": "string",
              "description": "File id assigned by the host app"
            },
            "file_name": {
              "type": "string"
            },
            "mime_type": {
              "type": "string"
            },
            "download_url": {
              "type": "string",
              "description": "Signed URL to download the file"
            }
          },
          "description": "An image attached to the conversation, as supplied by the host app. Omit it when passing image_url."
        },
        "format": {
          "enum": [
            "svg",
            "dxf",
            "eps"
          ],
          "type": "string",
          "default": "svg",
          "description": "Output file: \"svg\" (default) for design tools and Cricut Design Space; \"dxf\" for laser cutters, CNC routers and CAD; \"eps\" for print, sign-making and older design software."
        },
        "image_url": {
          "type": "string",
          "format": "uri",
          "description": "Public http(s) URL of a PNG, JPG, WebP or GIF image, up to 10 MB. Use it when no file is attached."
        }
      }
    }
    arguments 56 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 6a5b7920d212d91d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6a5b7920d212d91d/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/6a5b7920d212d91d/badge.svg)](https://brick.blue/agent/6a5b7920d212d91d?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
50%

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.