Remote MCP · Endpoint

Simafri Suite MCP server

No. Simafri Suite answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://suite-mcp.simafri.com/mcp

The last check completed an MCP handshake.

Registry name
com.simafri/professional-email
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
70 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Professional email, calendar, contacts and files on your own domain.
Listing
From the official MCP registry (active).
Recent checks of Simafri Suite
CheckedResultHandshake
1 hour agoHandshake completed159 ms
1 day agoHandshake completed146 ms
2 days agoHandshake completed127 ms
3 days agoHandshake completed333 ms
4 days agoHandshake completed299 ms
5 days agoHandshake completed142 ms
6 days agoHandshake completed377 ms
9 days agoHandshake completed350 ms
11 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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

Listing data comes from the official MCP registry. Glide is not affiliated with Simafri Suite and makes no claim about it beyond what these checks measured.