Is the Blixtworks Tools MCP server down?

mcp-registry/com.blixtworks.www/tools · v2.0.0

Also listed as glama/eggis70/img-categorize

healthy
Last checked 2026-10-19 18:04 UTC · handshake 99ms

As of 2026-10-19 18:04 UTC, the Blixtworks Tools MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
3,887
outages (90d)
2
tools
68

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

Install Blixtworks Tools MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (64/100)

D (64/100): 0 error(s), 5 warning(s) across 68 tool(s); ~12,180 tokens of tool definitions.
Scores higher than 1% of 15,354 MCP servers Glimind has audited.
Its tool list costs an agent ~12,180 tokens per session — more than 85% of servers.
64 → 64 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints16
Token cost75
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (6)

68 of 68 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: address_validate, base64, caption, case_convert, categorize and 63 more

68 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

106 parameter(s) across 63 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: address_validate, base64, caption, case_convert, categorize and 58 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: how_to_pay, redeem_payment, try_sample

Handshake + tools/list takes ~1,820 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 23 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 63 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.blixtworks.www%2Ftools/fixes

address_validate 1 change 
{
  "name": "address_validate",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "chain": {
        "type": "string"
      },
      "address": {
        "type": "string"
      },
      "paymentTx": {
        "type": "string",
        "description": "Transaction hash of your USDC payment on Base (see how_to_pay)"
      },
      "payerAddress": {
        "type": "string",
        "description": "Your wallet address, to spend existing credit without a new payment"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "address_validate ($0.005)"
}
case_convert 1 change 
{
  "name": "case_convert",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "to": {
        "type": "string"
      },
      "text": {
        "type": "string"
      },
      "paymentTx": {
        "type": "string",
        "description": "Transaction hash of your USDC payment on Base (see how_to_pay)"
      },
      "payerAddress": {
        "type": "string",
        "description": "Your wallet address, to spend existing credit without a new payment"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "case_convert ($0.005)"
}
check_credit 1 change 
{
  "name": "check_credit",
  "description": "Free: how much unspent credit a wallet address currently has with this endpoint.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "address"
    ],
    "properties": {
      "address": {
        "type": "string",
        "description": "Your wallet address"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check remaining credit (free)"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.blixtworks.www/tools"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.blixtworks.www/tools"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blixtworks.www%2Ftools.svg)](https://glimind.com/server/mcp-registry%2Fcom.blixtworks.www%2Ftools?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.blixtworks.www%2Ftools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blixtworks.www%2Ftools.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blixtworks.www%2Ftools.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.blixtworks.www%2Ftools?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:93ba9c29c957009e…, first seen 2026-10-17, included at leaf 1860 of 28,009. Version history · verify what your client received.

Tools (68)

Compare: most reliable blockchain servers · most reliable other servers · most reliable ml servers · most reliable data servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Blixtworks Tools MCP server down right now?

As of 2026-10-19 18:04 UTC, the Blixtworks Tools MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Blixtworks Tools MCP server provide?

Blixtworks Tools MCP server advertises 68 tools, including address_validate, base64, caption, case_convert, categorize.

How do I install Blixtworks Tools MCP server?

Point your MCP client at this streamable-http endpoint: https://www.blixtworks.com/mcp

Is the Blixtworks Tools MCP server safe to connect to an AI agent?

Glimind scanned all 68 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Blixtworks Tools MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve