Blixtworks
REMOTE · WWW.BLIXTWORKS.COM · 2 COMPONENTS
63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.
Available components
Last scanned (7 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 → Why this is hard to 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 Usability64
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "how_to_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 69 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Tool coverage: 100% → 55% ▼ functional
- Schema quality: pass → fail ▼ functional
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 0
First indexed and scored.
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 5 Nov 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 | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b6cd5ba4b37c06ee0ead3f27063db690 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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 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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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).
| 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.
How do I install the Blixtworks MCP server?
Blixtworks is a hosted endpoint at https://www.blixtworks.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.blixtworks.com
claude mcp add --transport http com-blixtworks-www-tools 'https://www.blixtworks.com/mcp'
What is the Blixtworks MCP server?
Blixtworks is an MCP server listed in the public MCP registry as com.blixtworks.www/tools. 63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402. This page covers its hosted endpoint (https://www.blixtworks.com/mcp).
Is the Blixtworks MCP server safe to use?
Blixtworks scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Blixtworks MCP server expose?
Blixtworks exposes 68 tools: list_tools, try_sample, how_to_pay, check_credit, redeem_payment, and 63 more. Their descriptions and schemas cost roughly 7,933 tokens of context every time the server is loaded.
Does the Blixtworks MCP server require authentication?
No. We connected to Blixtworks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Blixtworks MCP server still maintained?
Blixtworks is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.