Remote MCP · Endpoint
Bowmark MCP server
No. Bowmark answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.bowmark.ai/mcp/registry
The last check completed an MCP handshake.
- Registry name
- ai.bowmark/bowmark
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 282 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Web scraping and automation for AI agents: live prices, quotes, bookings, anything behind a login.
- Website
- https://bowmark.ai/
- Repository
- https://github.com/bowmark-ai/skill
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 282 ms |
| 1 day ago | Handshake completed | 392 ms |
| 3 days ago | Handshake completed | 354 ms |
| 3 days ago | Handshake completed | 347 ms |
| 4 days ago | Handshake completed | 300 ms |
| 5 days ago | Handshake completed | 323 ms |
| 7 days ago | Handshake completed | 331 ms |
| 10 days ago | Handshake completed | 279 ms |
| 12 days ago | Handshake completed | 291 ms |
| 14 days ago | Handshake completed | 280 ms |
| 17 days ago | Handshake completed | 323 ms |
| 19 days ago | Handshake completed | 893 ms |
| 21 days ago | Handshake completed | 284 ms |
| 23 days ago | Handshake completed | 278 ms |
| 25 days ago | Handshake completed | 304 ms |
| 26 days ago | Handshake completed | 256 ms |
| 28 days ago | Handshake completed | 281 ms |
| 29 days ago | Handshake completed | 262 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.
Listing data comes from the official MCP registry. Glide is not affiliated with Bowmark and makes no claim about it beyond what these checks measured.