Skip to content

Blixtworks MCP server

Which servers in the official MCP registry are Blixtworks's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-22

← Back to Blixtworks

Whose server it is
  • Registry namecom.blixtworks.www/toolsverified in the MCP registry

The registry name sits under blixtworks.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-22
  • Stateanswerschecked 2026-10-22
  • Tools68
  • Server calls itselfblixtworks
  • Server version2.0.0
  • Protocol version2025-06-18

On 2026-10-22 the server answered initialize and tools/list without a sign-in. First answer in 114 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: tag and caption images with vision models; validate email addresses and check domain MX records; convert currency at ECB reference rates.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "tag and caption images with vision models", the likely first call is categorize.
  • For "validate email addresses and check domain MX records", the likely first call is email_validate.
  • Parameters are untyped or undescribed in 63 of 68 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-22
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it3 of 3 use cases
  • Use22 npm downloads a week
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer154 ms
  • Space in an agent's context≈ 10,969 tokensthe definitions of all its tools (68), which an agent carries on every turn
  • Tool definitionsC · 68 of 100
  • Typed results0 of 68 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 63 of 68
  • Not saying whether it only reads or can destroy: 68 of 68

What an agent can do with it

  • can do · tag and caption images with vision models
  • can do · validate email addresses and check domain MX records
  • can do · convert currency at ECB reference rates

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers68 tools · read 2026-10-22
  • list_tools

    Free: every Blixtworks tool with price, inputs and description (63 tools). Optionally filter by group.

  • try_sample

    Free: runs the real CLIP model on a sample image so you can judge output quality before paying.

  • how_to_pay

    Free: exact payment steps, the receiving address, and how credit works.

  • check_credit

    Free: how much unspent credit a wallet address currently has with this endpoint.

  • redeem_payment

    Turn a USDC payment you already made into credit you can spend across multiple tool calls. Pass the transaction hash.

  • categorize

    Zero-shot image categorization (CLIP). POST {"image": "<https url or data URI>", "labels": ["optional", "custom"]} -> ranked labels with confidence scores. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call…

  • caption

    Image captioning. POST {"image": "<https url or data URI>"} -> one-sentence natural-language description. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • ocr

    OCR (English). POST {"image": "<https url or data URI>"} -> extracted text with confidence score. Costs $0.03 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • embed

    CLIP image embedding. POST {"image": "<https url or data URI>"} -> 512-dim vector for similarity search. Costs $0.015 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • hash

    Cryptographic hashes. POST {"text": "...", "algorithms": ["sha256","md5"]} -> hex digests (default md5, sha1, sha256, sha512). Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • hmac

    HMAC signature. POST {"text": "...", "key": "...", "algorithm": "sha256"} -> hex and base64 signature. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • uuid

    Generate UUIDs. POST {"count": 5, "version": "v4"} -> list of UUIDs (max 100). Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • base64

    Base64 encode or decode. POST {"text": "...", "mode": "encode"|"decode", "urlSafe": false} -> result. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • slugify

    URL-safe slug from any text. POST {"text": "Hällö Wörld!"} -> {"slug": "hallo-world"}. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • case_convert

    Convert text case. POST {"text": "...", "to": "camel"|"snake"|"kebab"|"pascal"|"upper"|"lower"|"title"} -> converted text. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • text_stats

    Text statistics. POST {"text": "..."} -> characters, words, sentences, paragraphs, reading time, top words. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • regex

    Test a regular expression and extract matches. POST {"text": "...", "pattern": "\\d+", "flags": "g"} -> matches with groups and indices. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • diff

    Compare two texts. POST {"a": "...", "b": "...", "mode": "lines"|"words"|"chars"} -> unified diff plus added/removed counts. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • language_detect

    Detect the language of a text. POST {"text": "..."} -> ISO 639-3 code and name. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • word_frequency

    Word and n-gram frequency analysis. POST {"text": "...", "ngram": 1, "limit": 20, "stopwords": true} -> ranked terms. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • lorem

    Generate placeholder text. POST {"paragraphs": 2, "wordsPerParagraph": 40} -> lorem ipsum text. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • json_format

    Format, minify or validate JSON. POST {"json": "...", "mode": "pretty"|"minify"|"validate", "indent": 2} -> formatted output or validation error with position. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call…

  • json_query

    Query JSON with a dot/bracket path. POST {"json": "...", "path": "users[0].name"} -> the value at that path. Supports [*] to map over arrays. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • json_to_csv

    Convert a JSON array of objects to CSV. POST {"json": "[{...}]", "delimiter": ","} -> CSV text. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • csv_to_json

    Convert CSV to JSON. POST {"csv": "...", "header": true, "delimiter": ","} -> array of objects (or arrays when header is false). Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • yaml_convert

    Convert between YAML and JSON. POST {"text": "...", "to": "json"|"yaml"} -> converted document. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • xml_to_json

    Convert XML to JSON. POST {"xml": "<root>...</root>"} -> parsed object. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • markdown_to_html

    Render Markdown to HTML. POST {"markdown": "# Title"} -> HTML string. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • jwt_decode

    Decode a JWT without verifying it. POST {"token": "eyJ..."} -> header, payload, expiry status. Signature is NOT verified. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • rss_parse

    Parse an RSS or Atom feed. POST {"url": "https://..."} or {"xml": "..."} -> feed title and items with links and dates. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • sitemap_parse

    Parse a sitemap.xml (including sitemap indexes). POST {"url": "https://example.com/sitemap.xml"} -> URLs with last-modified dates. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • pdf

    PDF text extraction. POST {"pdf": "<https url or data:application/pdf base64 URI>"} -> plain text, page count and metadata. Costs $0.03 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • http_headers

    Inspect HTTP response headers for a URL. POST {"url": "https://...", "method": "HEAD"} -> status, headers, timing, redirect chain. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • url_expand

    Expand a shortened URL by following redirects. POST {"url": "https://bit.ly/x"} -> final destination and hop chain. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • ssl_check

    Inspect a TLS certificate. POST {"domain": "example.com", "port": 443} -> issuer, subject, validity dates, days until expiry. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • whois

    Domain registration data via RDAP. POST {"domain": "example.com"} -> registrar, creation/expiry dates, nameservers, status. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • robots_check

    Fetch and interpret robots.txt. POST {"url": "https://example.com", "userAgent": "GPTBot", "path": "/"} -> whether crawling is allowed, plus sitemaps. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay…

  • metadata

    Extract page metadata: title, description, Open Graph, Twitter card, canonical, favicon, language. POST {"url": "https://..."}. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • ip_lookup

    Resolve a hostname to IPs and reverse-resolve. POST {"host": "example.com"} -> A/AAAA records and PTR names. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • email_validate

    Validate an email address: syntax plus live MX record check on the domain. POST {"email": "[email protected]"} -> deliverability signals. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • md

    HTML to Markdown. POST {"url": "<https url>"} or {"html": "<raw html>"} (+ optional "mode": "article"|"full", default article) -> clean LLM-ready markdown with title/byline. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to…

  • dns

    DNS lookup. POST {"domain": "example.com", "type": "A"|"AAAA"|"MX"|"TXT"|"NS"|"CNAME"|"SOA"|"all"} -> resolved records. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • unit_convert

    Convert between units. POST {"value": 5, "from": "km", "to": "mi"} -> converted value. Supports length, mass, volume, time, area, speed, data, pressure, energy and temperature (c/f/k). Costs $0.005 in USDC on Base — pass paymentTx or…

  • number_base

    Convert a number between bases. POST {"value": "255", "from": 10, "to": 16} -> converted string (bases 2-36). Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • color_convert

    Convert colours between hex, RGB and HSL. POST {"color": "#2563eb"} -> hex, rgb, hsl and luminance/contrast info. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • timestamp

    Convert timestamps and dates. POST {"value": 1735689600, "timezone": "Europe/Stockholm"} or {"value": "2026-01-01T00:00:00Z"} -> unix seconds/ms, ISO, and formatted local time. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress…

  • date_diff

    Difference between two dates. POST {"from": "2026-01-01", "to": "2026-12-25"} -> days, hours, business days and a human summary. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • cron_parse

    Explain a cron expression and list upcoming run times. POST {"expression": "0 9 * * 1-5", "count": 5, "timezone": "UTC"}. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • distance

    Great-circle distance between two coordinates. POST {"from": {"lat": 59.33, "lon": 18.07}, "to": {"lat": 51.51, "lon": -0.13}} -> km, miles and bearing. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay…

  • currency_convert

    Convert currency at current or historical reference rates (ECB via Frankfurter). POST {"amount": 100, "from": "EUR", "to": "SEK", "date": "2026-01-15"}. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay…

  • luhn_validate

    Validate an identifier with the Luhn checksum (credit cards, IMEI, Swedish personnummer). POST {"number": "4111111111111111"} -> validity and detected card scheme. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call…

  • phone_parse

    Parse and validate a phone number. POST {"phone": "+46701234567", "country": "SE"} -> validity, type, and E.164/national/international formats. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for…

  • iban_validate

    Validate an IBAN (checksum and country length). POST {"iban": "SE45 5000 0000 0583 9825 7466"}. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • percentage

    Percentage maths. POST {"mode": "change"|"of"|"increase"|"decrease", "a": 120, "b": 150} -> result with explanation. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • image_info

    Image dimensions and properties without any ML. POST {"image": "https://..."} -> width, height, aspect ratio, format, file size, transparency. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for…

  • image_resize

    Resize or convert an image. POST {"image": "https://...", "width": 800, "height": null, "format": "jpeg"|"png", "quality": 80} -> data URI of the result. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay…

  • image_palette

    Extract the dominant colour palette from an image. POST {"image": "https://...", "colors": 5} -> hex colours with share percentages. Costs $0.015 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • image_crop

    Crop an image. POST {"image": "https://...", "x": 0, "y": 0, "width": 200, "height": 200} -> cropped image as a data URI. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  • image_transform

    Rotate, flip or apply filters to an image. POST {"image": "...", "rotate": 90, "flip": "horizontal", "filter": "greyscale"|"sepia"|"invert"|"blur"} -> transformed image. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay…

  • image_placeholder

    Generate a solid or gradient placeholder image. POST {"width": 600, "height": 400, "color": "#2563eb", "text": "optional"} -> PNG data URI. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

The first 60 of 68, as the server listed them.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "tools": {
      "type": "http",
      "url": "https://www.blixtworks.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http blixtworks https://www.blixtworks.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.blixtworks.com/mcp as a custom connector in the settings.

Also shipped through: npm

OpenAPI spec

63 paths, read 2026-10-22. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.