Remote MCP · Endpoint

Outcomet MCP server

No. Outcomet answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.outcomet.app/mcp

The last check completed an MCP handshake.

Registry name
app.outcomet/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
107 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read customer feedback, problems and initiatives in Outcomet, and log new feedback from chat.
Listing
From the official MCP registry (active).
Recent checks of Outcomet
CheckedResultHandshake
1 hour agoHandshake completed159 ms
9 days agoHandshake completed315 ms
10 days agoHandshake completed321 ms
11 days agoHandshake completed152 ms
12 days agoCredentials required—
14 days agoCredentials required—
14 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
28 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 Outcomet and makes no claim about it beyond what these checks measured.