Remote MCP · Endpoint

X1-BaaS Scraping API MCP server

No. X1-BaaS Scraping API answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
779 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 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).
Recent checks of X1-BaaS Scraping API
CheckedResultHandshake
2 hours agoHandshake completed779 ms
1 day agoHandshake completed719 ms
2 days agoHandshake completed842 ms
3 days agoHandshake completed1.21 s
4 days agoHandshake completed824 ms
5 days agoHandshake completed841 ms
7 days agoHandshake completed909 ms
9 days agoHandshake completed729 ms
12 days agoHandshake completed859 ms
14 days agoHandshake completed1.06 s
16 days agoHandshake completed731 ms
18 days agoHandshake completed718 ms
20 days agoHandshake completed1.03 s
22 days agoHandshake completed768 ms
25 days agoHandshake completed886 ms
26 days agoHandshake completed1.30 s
27 days agoHandshake completed865 ms
29 days agoHandshake completed843 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.