Remote MCP · Endpoint

ScrapeMole Pulse MCP server

No. ScrapeMole Pulse answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pulse.scrapemole.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.pages.scrapemole/pulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.48 s
Tools exposed
17 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
x402 FX, time, weather, US NWS alerts, HN, holidays, geocoding for agents.
Listing
From the official MCP registry (active).
Recent checks of ScrapeMole Pulse
CheckedResultHandshake
1 hour agoHandshake completed1.48 s
1 day agoHandshake completed551 ms
2 days agoHandshake completed709 ms
3 days agoHandshake completed1.33 s
4 days agoHandshake completed575 ms
5 days agoHandshake completed539 ms
6 days agoHandshake completed648 ms
8 days agoHandshake completed568 ms
11 days agoHandshake completed853 ms
13 days agoHandshake completed684 ms
16 days agoHandshake completed63 ms
18 days agoHandshake completed445 ms
20 days agoHandshake completed339 ms
22 days agoHandshake completed638 ms
24 days agoHandshake completed46 ms

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

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 ScrapeMole Pulse and makes no claim about it beyond what these checks measured.