Blixtworks

REMOTE · WWW.BLIXTWORKS.COM · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · www.blixtworks.com 60 npm · blixtworks-mcp 56

60 60 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 68 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability61

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 8166 tokens (~120/item across 68 items; 68 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management10

Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage85

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
55% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · www.blixtworks.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.com-blixtworks-www-tools]
url = "https://www.blixtworks.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-blixtworks-www-tools": {
      "type": "remote",
      "url": "https://www.blixtworks.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-blixtworks-www-tools --url https://www.blixtworks.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-blixtworks-www-tools:
    url: "https://www.blixtworks.com/mcp"

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 −2
- Tool coverage: 100% → 55% ▼ functional
- Schema quality: pass → fail ▼ functional
1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
31 Jul 26 62

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://www.blixtworks.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=www.blixtworks.com	CN=WE1,O=Google Trust Services,C=US	31 Jul 2026	29 Oct 2026	ECDSA 256	ECDSA-SHA256	fdc7945cbc91356f137f729d77863ca6
SANs: www.blixtworks.com
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of www.blixtworks.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
blixtworks.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://www.blixtworks.com/mcp	Verified	200
http (plaintext)	http://www.blixtworks.com/mcp	HTTPS enforced	301	https://www.blixtworks.com/mcp

MCP tools — 68 exposed · ~7,933 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

robots_check robots_check ($0.01) ~132

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
url	string	—	—
userAgent	string	—	—

No output schema declared.

No examples provided.

rss_parse rss_parse ($0.02) ~116

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
url	string	—	—

No output schema declared.

No examples provided.

sitemap_parse sitemap_parse ($0.02) ~114

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
url	string	—	—

No output schema declared.

No examples provided.

slugify slugify ($0.005) ~114

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
text	string	—	—

No output schema declared.

No examples provided.

ssl_check ssl_check ($0.02) ~115

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

Input Output Examples

Name	Type	Req	Description
domain	string	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)

No output schema declared.

No examples provided.

text_stats text_stats ($0.005) ~108

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
text	string	—	—

No output schema declared.

No examples provided.

timestamp timestamp ($0.005) ~145

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
timezone	string	—	—
value	string	—	—

No output schema declared.

No examples provided.

token_info token_info ($0.015) ~121

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

Input Output Examples

Name	Type	Req	Description
chain	string	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
token	string	—	—

No output schema declared.

No examples provided.

try_sample Run a free sample (free) ~29

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tx_lookup tx_lookup ($0.02) ~125

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

Input Output Examples

Name	Type	Req	Description
chain	string	—	—
hash	string	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)

No output schema declared.

No examples provided.

unit_convert unit_convert ($0.005) ~150

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

Input Output Examples

Name	Type	Req	Description
from	string	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
to	string	—	—
value	number	—	—

No output schema declared.

No examples provided.

url_expand url_expand ($0.01) ~110

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
url	string	—	—

No output schema declared.

No examples provided.

uuid uuid ($0.005) ~111

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

Input Output Examples

Name	Type	Req	Description
count	number	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)

No output schema declared.

No examples provided.

wallet_balance wallet_balance ($0.015) ~126

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

Input Output Examples

Name	Type	Req	Description
address	string	—	—
chain	string	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)

No output schema declared.

No examples provided.

whois whois ($0.02) ~112

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

Input Output Examples

Name	Type	Req	Description
domain	string	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)

No output schema declared.

No examples provided.

word_frequency word_frequency ($0.01) ~136

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

Input Output Examples

Name	Type	Req	Description
limit	number	—	—
ngram	number	—	—
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
text	string	—	—

No output schema declared.

No examples provided.

xml_to_json xml_to_json ($0.01) ~105

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
xml	string	—	—

No output schema declared.

No examples provided.

yaml_convert yaml_convert ($0.01) ~116

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

Input Output Examples

Name	Type	Req	Description
payerAddress	string	—	Your wallet address, to spend existing credit without a new payment
paymentTx	string	—	Transaction hash of your USDC payment on Base (see how_to_pay)
text	string	—	—
to	string	—	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

31 Jul 3 Aug