Remote MCP · Endpoint

dev.workers.sebastiaan-ba3.signals/tools MCP server

No. dev.workers.sebastiaan-ba3.signals/tools answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://signals.sebastiaan-ba3.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.sebastiaan-ba3.signals/tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Lighter funding/volume snapshot and multi-chain wallet balance checks for AI agents.
Website
https://doormat.sebastiaan-ba3.workers.dev/
Listing
From the official MCP registry (active).
Recent checks of dev.workers.sebastiaan-ba3.signals/tools
CheckedResultHandshake
20 minutes agoHandshake completed125 ms
9 days agoHandshake completed159 ms
9 days agoHandshake completed77 ms
11 days agoHandshake completed79 ms
12 days agoHandshake completed96 ms
13 days agoHandshake completed141 ms
14 days agoHandshake completed87 ms
15 days agoHandshake completed110 ms
16 days agoHandshake completed124 ms
19 days agoHandshake completed189 ms
21 days agoHandshake completed192 ms
24 days agoHandshake completed571 ms
26 days agoHandshake completed116 ms
28 days agoHandshake completed120 ms

The last 14 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.

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 dev.workers.sebastiaan-ba3.signals/tools and makes no claim about it beyond what these checks measured.