Remote MCP · Endpoint

Outreach2day MCP server

No. Outreach2day answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://public.outreach2day.com/mcp

The last check completed an MCP handshake.

Registry name
com.outreach2day/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
427 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Cold email infrastructure: domains, mailboxes, warm-up and campaigns. Never charges a card.
Listing
From the official MCP registry (active).
Recent checks of Outreach2day
CheckedResultHandshake
2 hours agoHandshake completed427 ms
2 days agoHandshake completed417 ms
4 days agoHandshake completed471 ms
6 days agoHandshake completed438 ms
8 days agoHandshake completed397 ms
10 days agoHandshake completed404 ms
12 days agoHandshake completed465 ms
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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

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