Remote MCP · Endpoint
oassis — web scraping, crawling and browser control for AI agents MCP server
No. oassis — web scraping, crawling and browser control for AI agents answered an MCP handshake 6 days ago.
UpLast checked 6 days ago
Server URL
https://api.oassis.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.oassis/scraper-crawler
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 564 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Web Tools and Web Tasks for AI agents. 100-credit MCP trial; API-key credits or x402.
- Website
- https://oassis.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 6 days ago | Handshake completed | 564 ms |
| 7 days ago | Handshake completed | 376 ms |
| 7 days ago | Handshake completed | 330 ms |
| 9 days ago | Handshake completed | 300 ms |
| 10 days ago | Handshake completed | 414 ms |
| 11 days ago | Handshake completed | 674 ms |
| 12 days ago | Handshake completed | 483 ms |
| 13 days ago | Handshake completed | 585 ms |
| 15 days ago | Handshake completed | 448 ms |
| 17 days ago | Handshake completed | 215 ms |
| 20 days ago | Handshake completed | 471 ms |
| 22 days ago | Handshake completed | 291 ms |
| 24 days ago | Handshake completed | 337 ms |
| 26 days ago | Handshake completed | 313 ms |
| 28 days ago | Handshake completed | 327 ms |
| 30 days ago | Handshake completed | 217 ms |
| 32 days ago | Handshake completed | 209 ms |
| 34 days ago | Handshake completed | 226 ms |
| 35 days ago | Handshake completed | 246 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.
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 oassis — web scraping, crawling and browser control for AI agents and makes no claim about it beyond what these checks measured.