Remote MCP · Endpoint

Confirme, by Synapse MCP server

No. Confirme, by Synapse answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.synapseconnexion.com/ia/mcp

The last check completed an MCP handshake.

Registry name
com.synapseconnexion.www/confirme
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Did it really happen? Independent signed receipts for AI agents: page, domain, email, heartbeat.
Listing
From the official MCP registry (active).
Recent checks of Confirme, by Synapse
CheckedResultHandshake
1 hour agoHandshake completed151 ms
2 days agoHandshake completed69 ms
4 days agoHandshake completed70 ms
6 days agoHandshake completed71 ms
8 days agoFailed - the hostname does not resolve—
10 days agoHandshake completed144 ms
12 days agoHandshake completed136 ms
14 days agoHandshake completed171 ms
15 days agoHandshake completed82 ms
17 days agoHandshake completed66 ms
18 days agoHandshake completed140 ms
20 days agoHandshake completed137 ms
22 days agoHandshake completed68 ms
24 days agoHandshake completed95 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Confirme, by Synapse and makes no claim about it beyond what these checks measured.