Skip to content

Blixtworks MCP server

com.blixtworks.www/toolswww.blixtworks.comstreamable-httpv1.1.0Scanned

63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.

68 tools: 8 do something that can't be undone, 45 change things and 15 only read.

Tools: 0 delete, 8 irreversible, 45 write, 15 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 14
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Blixtworks MCP server can do

The Blixtworks MCP server is published by www.blixtworks.com, a domain the MCP Registry verified. It has 68 tools. It can do things that cannot be undone, such as sending, paying or publishing (how_to_pay, redeem_payment, case_convert, yaml_convert and 4 more) and create or change data (45 tools: try_sample, check_credit, categorize, caption and 41 more), but cannot delete data. 15 tools only read.

2 tools bring in text other people can write (http_headers and robots_check); 14 tools can send data out of your system (case_convert, yaml_convert, rss_parse and 11 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 10, 2026, version 1.1.0.

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.

68 tools

Can't be undone 8Claude Code: ask
  • case_convertConvert text case.Can send data outNo findings

    Why it is in this group

    • The name "case_convert" says "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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).
  • currency_convertConvert currency at current or historical reference rates (ECB via Frankfurter).Can send data outNo findings

    Why it is in this group

    • The name "currency_convert" says "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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 for details).
  • distanceGreat-circle distance between two coordinates.Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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 for details).
  • how_to_payFree: exact payment steps, the receiving address, and how credit works.No findings

    Why it is in this group

    • The name "how_to_pay" says "pay": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Free: exact payment steps, the receiving address, and how credit works.
  • number_baseConvert a number between bases.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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).
  • redeem_paymentTurn a USDC payment you already made into credit you can spend across multiple tool calls.No findings

    Why it is in this group

    • The name "redeem_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Turn a USDC payment you already made into credit you can spend across multiple tool calls. Pass the transaction hash.
  • unit_convertConvert between units.Can send data outNo findings

    Why it is in this group

    • The name "unit_convert" says "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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 payerAddress to pay (call how_to_pay for details).
  • yaml_convertConvert between YAML and JSON.Can send data outNo findings

    Why it is in this group

    • The name "yaml_convert" says "convert": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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).
Changes things 45Claude Code: ask
  • base64Base64 encode or decode.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
    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).
  • captionImage captioning.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
    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).
  • categorizeZero-shot image categorization (CLIP).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
    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 how_to_pay for details).
  • check_creditFree: how much unspent credit a wallet address currently has with this endpoint.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
    Free: how much unspent credit a wallet address currently has with this endpoint.
  • color_convertConvert colours between hex, RGB and HSL.No findings

    Why it is in this group

    • The name "color_convert" says "convert": a word for a change.
    Description, as the server wrote it
    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).
  • csv_to_jsonConvert CSV to JSON.No findings

    Why it is in this group

    • The description's first verb is "convert": a word for a change.
    Description, as the server wrote it
    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).
  • dnsDNS lookup.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
    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).
  • embedCLIP image embedding.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
    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).
  • exifEXIF metadata extraction.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
    EXIF metadata extraction. POST {"image": "<https url or data:image URI>"} -> camera, timestamps, GPS and other metadata. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • gas_priceCurrent gas price and what a transfer costs.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
    Current gas price and what a transfer costs. POST {"chain": "base"|"ethereum"} -> gwei, block number and estimated transfer cost. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • hashCryptographic hashes.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
    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).
  • hmacHMAC signature.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
    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).
  • image_cropCrop an image.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
    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_infoImage dimensions and properties without any ML.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
    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 details).
  • image_paletteExtract the dominant colour palette from an image.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
    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_placeholderGenerate a solid or gradient placeholder image.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    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).
  • image_resizeResize or convert an image.No findings

    Why it is in this group

    • The name "image_resize" says "resize": a word for a change.
    Description, as the server wrote it
    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 for details).
  • image_transformRotate, flip or apply filters to an image.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
    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 (call how_to_pay for details).
  • json_formatFormat, minify or validate JSON.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
    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 how_to_pay for details).
  • json_to_csvConvert a JSON array of objects to CSV.No findings

    Why it is in this group

    • The description's first verb is "convert": a word for a change.
    Description, as the server wrote it
    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).
  • jwt_decodeDecode a JWT without verifying it.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
    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).
  • language_detectDetect the language of a text.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
    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).
  • loremGenerate placeholder text.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    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).
  • markdown_to_htmlRender Markdown to HTML.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
    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).
  • mdHTML to Markdown.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
    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 pay (call how_to_pay for details).
  • metadataExtract page metadata: title, description, Open Graph, Twitter card, canonical, favicon, language.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
    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).
  • ocrOCR (English).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
    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).
  • pdfPDF text extraction.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
    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).
  • percentagePercentage maths.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
    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).
  • phone_parseParse and validate a phone number.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 destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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 details).
  • qrQR code generation.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
    QR code generation. POST {"text": "<content>", "format": "svg"|"png"} -> QR code as an SVG string or PNG data URI. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • regexTest a regular expression and extract matches.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
    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).
  • rss_parseParse an RSS or Atom feed.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
    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_parseParse a sitemap.xml (including sitemap indexes).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
    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).
  • slugifyURL-safe slug from any text.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
    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).
  • text_statsText statistics.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
    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).
  • timestampConvert timestamps and dates.No findings

    Why it is in this group

    • The description's first verb is "convert": a word for a change.
    Description, as the server wrote it
    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 to pay (call how_to_pay for details).
  • token_infoERC-20 token metadata.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
    ERC-20 token metadata. POST {"token": "0x...", "chain": "base"} -> name, symbol, decimals, total supply. Costs $0.015 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • try_sampleFree: runs the real CLIP model on a sample image so you can judge output quality before paying.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
    Free: runs the real CLIP model on a sample image so you can judge output quality before paying.
  • url_expandExpand a shortened URL by following redirects.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
    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).
  • uuidGenerate UUIDs.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    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).
  • wallet_balanceNative and USDC balance for an address.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
    Native and USDC balance for an address. POST {"address": "0x...", "chain": "base"|"ethereum"} -> balances, transaction count and explorer link. Costs $0.015 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • whoisDomain registration data via RDAP.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
    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).
  • word_frequencyWord and n-gram frequency analysis.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
    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).
  • xml_to_jsonConvert XML to JSON.No findings

    Why it is in this group

    • The description's first verb is "convert": a word for a change.
    Description, as the server wrote it
    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).
Only reads 15Show 15 read-only tools
  • address_validateValidate an EVM address and detect whether it is a contract.No findings

    Why it is in this group

    • The name "address_validate" says "validate": a word for reading.
    Description, as the server wrote it
    Validate an EVM address and detect whether it is a contract. POST {"address": "0x...", "chain": "base"} -> checksum form and account type. Costs $0.005 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • cron_parseExplain a cron expression and list upcoming run times.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    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).
  • date_diffDifference between two dates.No findings

    Why it is in this group

    • The name "date_diff" says "diff": a word for reading.
    Description, as the server wrote it
    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).
  • diffCompare two texts.No findings

    Why it is in this group

    • The name "diff" says "diff": a word for reading.
    Description, as the server wrote it
    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).
  • email_validateValidate an email address: syntax plus live MX record check on the domain.No findings

    Why it is in this group

    • The name "email_validate" says "validate": a word for reading.
    Description, as the server wrote it
    Validate an email address: syntax plus live MX record check on the domain. POST {"email": "a@b.com"} -> deliverability signals. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • ens_resolveResolve an ENS name to an address, or an address to its primary ENS name.No findings

    Why it is in this group

    • The name "ens_resolve" says "resolve": a word for reading.
    Description, as the server wrote it
    Resolve an ENS name to an address, or an address to its primary ENS name. POST {"name": "vitalik.eth"} or {"address": "0x..."}. Costs $0.015 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).
  • http_headersInspect HTTP response headers for a URL.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "inspect": a word for reading.

    What it can reach

    • untrusted-inputThe name "http_headers" says "http": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "inspect" and "http": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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).
  • iban_validateValidate an IBAN (checksum and country length).No findings

    Why it is in this group

    • The name "iban_validate" says "validate": a word for reading.
    Description, as the server wrote it
    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).
  • ip_lookupResolve a hostname to IPs and reverse-resolve.No findings

    Why it is in this group

    • The name "ip_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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).
  • json_queryQuery JSON with a dot/bracket path.No findings

    Why it is in this group

    • The name "json_query" says "query": a word for reading.
    Description, as the server wrote it
    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).
  • list_toolsFree: every Blixtworks tool with price, inputs and description (63 tools).No findings

    Why it is in this group

    • The name "list_tools" says "list": a word for reading.
    Description, as the server wrote it
    Free: every Blixtworks tool with price, inputs and description (63 tools). Optionally filter by group.
  • luhn_validateValidate an identifier with the Luhn checksum (credit cards, IMEI, Swedish personnummer).No findings

    Why it is in this group

    • The name "luhn_validate" says "validate": a word for reading.
    Description, as the server wrote it
    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 how_to_pay for details).
  • robots_checkFetch and interpret robots.txt.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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 for details).
  • ssl_checkInspect a TLS certificate.No findings

    Why it is in this group

    • The description's first verb is "inspect": a word for reading.
    Description, as the server wrote it
    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).
  • tx_lookupLook up a transaction by hash.No findings

    Why it is in this group

    • The name "tx_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up a transaction by hash. POST {"hash": "0x...", "chain": "base"} -> status, value, gas used, from/to and block. Costs $0.02 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out14
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Oct 22, 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
53
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 53 tools that change things (8 irreversible, 45 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.blixtworks.com/mcp: tools/list returned 68 tools to an anonymous client, including how_to_pay (irreversible), redeem_payment (irreversible), case_convert (irreversible), yaml_convert (irreversible), unit_convert (irreversible) and 48 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.1.0. Values in angle brackets are yours to fill in.

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

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tools__list_tools",
      "mcp__tools__diff",
      "mcp__tools__json_query",
      "mcp__tools__ssl_check",
      "mcp__tools__ip_lookup",
      "mcp__tools__email_validate",
      "mcp__tools__date_diff",
      "mcp__tools__cron_parse",
      "mcp__tools__luhn_validate",
      "mcp__tools__iban_validate",
      "mcp__tools__address_validate",
      "mcp__tools__ens_resolve",
      "mcp__tools__tx_lookup"
    ],
    "ask": [
      "mcp__tools__try_sample",
      "mcp__tools__how_to_pay",
      "mcp__tools__check_credit",
      "mcp__tools__redeem_payment",
      "mcp__tools__categorize",
      "mcp__tools__caption",
      "mcp__tools__ocr",
      "mcp__tools__embed",
      "mcp__tools__hash",
      "mcp__tools__hmac",
      "mcp__tools__uuid",
      "mcp__tools__base64",
      "mcp__tools__slugify",
      "mcp__tools__case_convert",
      "mcp__tools__text_stats",
      "mcp__tools__regex",
      "mcp__tools__language_detect",
      "mcp__tools__word_frequency",
      "mcp__tools__lorem",
      "mcp__tools__json_format",
      "mcp__tools__json_to_csv",
      "mcp__tools__csv_to_json",
      "mcp__tools__yaml_convert",
      "mcp__tools__xml_to_json",
      "mcp__tools__markdown_to_html",
      "mcp__tools__jwt_decode",
      "mcp__tools__rss_parse",
      "mcp__tools__sitemap_parse",
      "mcp__tools__pdf",
      "mcp__tools__http_headers",
      "mcp__tools__url_expand",
      "mcp__tools__whois",
      "mcp__tools__robots_check",
      "mcp__tools__metadata",
      "mcp__tools__md",
      "mcp__tools__dns",
      "mcp__tools__unit_convert",
      "mcp__tools__number_base",
      "mcp__tools__color_convert",
      "mcp__tools__timestamp",
      "mcp__tools__distance",
      "mcp__tools__currency_convert",
      "mcp__tools__phone_parse",
      "mcp__tools__percentage",
      "mcp__tools__image_info",
      "mcp__tools__image_resize",
      "mcp__tools__image_palette",
      "mcp__tools__image_crop",
      "mcp__tools__image_transform",
      "mcp__tools__image_placeholder",
      "mcp__tools__qr",
      "mcp__tools__exif",
      "mcp__tools__wallet_balance",
      "mcp__tools__token_info",
      "mcp__tools__gas_price"
    ],
    "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 tools. Review it before you use it.

Capability tags behind 14 rules
  • mcp__tools__case_convert outbound
  • mcp__tools__yaml_convert outbound
  • mcp__tools__rss_parse outbound
  • mcp__tools__sitemap_parse outbound
  • mcp__tools__http_headers untrusted-input, outbound
  • mcp__tools__url_expand outbound
  • mcp__tools__robots_check untrusted-input, outbound
  • mcp__tools__metadata outbound
  • mcp__tools__md outbound
  • mcp__tools__unit_convert outbound
  • mcp__tools__number_base outbound
  • mcp__tools__distance outbound
  • mcp__tools__currency_convert outbound
  • mcp__tools__phone_parse 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/com.blixtworks.www/tools/verify?hash=aa8ee84ec0297e6a6c8224ec202db9e12cdd336010e3b80eb5581e9960bb28aa" | jq -e '.changed == false'

Pinned hash aa8ee84ec029, from Nov 10, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.blixtworks.www/tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.blixtworks.www/tools
[![Anlyon Radar](https://radar.anlyon.com/badge/com.blixtworks.www/tools.svg)](https://radar.anlyon.com/servers/com.blixtworks.www/tools)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:52 UTC.

Blixtworks MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Blixtworks MCP server safe?

No scan can promise that. What its definitions show: 68 tools, 53 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Blixtworks MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Blixtworks MCP server do things that cannot be undone?

Yes. 8 tools can send, pay, publish or merge: how_to_pay, redeem_payment, case_convert, yaml_convert, unit_convert, number_base and 2 more.

What tools does the Blixtworks MCP server have?

68 tools: 8 irreversible, 45 write, 15 read. how_to_pay, redeem_payment, case_convert, yaml_convert, unit_convert, number_base, distance, currency_convert and 60 more.

Does the Blixtworks MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Blixtworks MCP server send data to outside services?

14 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): case_convert, yaml_convert, rss_parse, sitemap_parse, http_headers, url_expand and 8 more.

Has the Blixtworks MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.