Remote MCP · Endpoint

io.github.dame-senders/senders-mcp MCP server

No — it is up, but it requires credentials. io.github.dame-senders/senders-mcp answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://mcp.senders.ai/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
io.github.dame-senders/senders-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Cold email infrastructure — campaigns, prospects, mailbox health and replies via Claude.
Listing
From the official MCP registry (active).
Recent checks of io.github.dame-senders/senders-mcp
CheckedResultHandshake
1 hour agoCredentials required—
1 day agoHandshake completed748 ms
3 days agoHandshake completed786 ms
3 days agoHandshake completed696 ms
4 days agoHandshake completed910 ms
5 days agoHandshake completed743 ms
7 days agoHandshake completed785 ms
10 days agoHandshake completed789 ms
12 days agoHandshake completed767 ms
15 days agoHandshake completed789 ms
17 days agoHandshake completed807 ms
19 days agoHandshake completed929 ms
21 days agoHandshake completed754 ms
23 days agoHandshake completed784 ms
25 days agoHandshake completed782 ms
26 days agoHandshake completed741 ms
28 days agoHandshake completed527 ms
29 days agoHandshake completed743 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 io.github.dame-senders/senders-mcp and makes no claim about it beyond what these checks measured.