Remote MCP · Endpoint

Debriefing MCP server

No. Debriefing answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://debriefing.io/mcp

The last check completed an MCP handshake.

Registry name
io.debriefing/debriefing
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
133 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards.
Listing
From the official MCP registry (active).
Recent checks of Debriefing
CheckedResultHandshake
1 hour agoHandshake completed133 ms
1 day agoHandshake completed219 ms
4 days agoHandshake completed134 ms
7 days agoHandshake completed216 ms
9 days agoHandshake completed129 ms
11 days agoHandshake completed153 ms
13 days agoHandshake completed130 ms
15 days agoHandshake completed214 ms
17 days agoHandshake completed225 ms
19 days agoHandshake completed144 ms
21 days agoHandshake completed125 ms
22 days agoHandshake completed144 ms
23 days agoHandshake completed229 ms

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

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