Remote MCP · Endpoint
X1-BaaS Scraping API MCP server
No. X1-BaaS Scraping API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.tazpal.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.tazpal/x1-baas
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.03 s
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Stealth scraping API for AI agents. Clean Markdown from any URL. x402 crypto payments.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.03 s |
| 2 days ago | Handshake completed | 768 ms |
| 4 days ago | Handshake completed | 886 ms |
| 5 days ago | Handshake completed | 1.30 s |
| 7 days ago | Handshake completed | 865 ms |
| 8 days ago | Handshake completed | 843 ms |
| 9 days ago | Handshake completed | 914 ms |
| 12 days ago | Handshake completed | 910 ms |
| 13 days ago | Handshake completed | 829 ms |
| 15 days ago | Handshake completed | 707 ms |
| 16 days ago | Handshake completed | 789 ms |
| 17 days ago | Handshake completed | 707 ms |
| 18 days ago | Handshake completed | 921 ms |
| 19 days ago | Handshake completed | 760 ms |
| 20 days ago | Handshake completed | 780 ms |
| 21 days ago | Handshake completed | 801 ms |
| 22 days ago | Handshake completed | 5.11 s |
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 X1-BaaS Scraping API and makes no claim about it beyond what these checks measured.