Remote MCP · Endpoint
Blixtworks MCP server
No. Blixtworks answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.blixtworks.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.blixtworks.www/tools
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 136 ms
- Tools exposed
- 68 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- 63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.
- Website
- https://www.blixtworks.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 136 ms |
| 2 days ago | Handshake completed | 283 ms |
| 4 days ago | Handshake completed | 140 ms |
| 5 days ago | Handshake completed | 156 ms |
| 7 days ago | Handshake completed | 315 ms |
| 8 days ago | Handshake completed | 255 ms |
| 9 days ago | Handshake completed | 148 ms |
| 12 days ago | Handshake completed | 139 ms |
| 13 days ago | Handshake completed | 145 ms |
| 15 days ago | Handshake completed | 146 ms |
| 16 days ago | Handshake completed | 139 ms |
| 17 days ago | Handshake completed | 252 ms |
| 18 days ago | Handshake completed | 237 ms |
| 19 days ago | Handshake completed | 255 ms |
| 20 days ago | Handshake completed | 107 ms |
| 21 days ago | Handshake completed | 277 ms |
| 22 days ago | Handshake completed | 210 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Blixtworks and makes no claim about it beyond what these checks measured.