Remote MCP · Endpoint

io.github.HASAVAGE/teardrop MCP server

No. io.github.HASAVAGE/teardrop answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://api.teardrop.dev/tools/mcp

The last check completed an MCP handshake.

Registry name
io.github.HASAVAGE/teardrop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
573 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Teardrop MCP gateway: paid tools for autonomous agents (x402, credits).
Listing
From the official MCP registry (active).
Recent checks of io.github.HASAVAGE/teardrop
CheckedResultHandshake
36 minutes agoHandshake completed573 ms
8 days agoHandshake completed175 ms
9 days agoHandshake completed229 ms
11 days agoHandshake completed276 ms
12 days agoHandshake completed165 ms
12 days agoHandshake completed177 ms
14 days agoHandshake completed139 ms
14 days agoHandshake completed310 ms
16 days agoHandshake completed291 ms
19 days agoHandshake completed314 ms
21 days agoHandshake completed582 ms
24 days agoHandshake completed290 ms
26 days agoHandshake completed373 ms
28 days agoHandshake completed114 ms

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

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 io.github.HASAVAGE/teardrop and makes no claim about it beyond what these checks measured.