Remote MCP · Endpoint

EmailOctopus MCP by usefulapi MCP server

No. EmailOctopus MCP by usefulapi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://emailoctopus.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/emailoctopus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
164 ms
Tools exposed
13 tools
Uptime, last 30 days
50.0% from 18 checks
Described by its publisher as
Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus.
Website
https://usefulapi.io/emailoctopus/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of EmailOctopus MCP by usefulapi
CheckedResultHandshake
1 hour agoHandshake completed164 ms
2 days agoHandshake completed471 ms
4 days agoHandshake completed179 ms
6 days agoHandshake completed184 ms
7 days agoHandshake completed262 ms
9 days agoHandshake completed200 ms
10 days agoHandshake completed182 ms
11 days agoHandshake completed347 ms
14 days agoFailed - the check failed for an unclassified reason—
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed300 ms
19 days agoFailed - the check failed for an unclassified reason—
20 days agoFailed - the check failed for an unclassified reason—
21 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—
25 days agoFailed - the check failed for an unclassified reason—

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

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