Remote MCP · Endpoint

CutGPT Research & Fact-Check MCP server

No. CutGPT Research & Fact-Check answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://mcp.cutgpt.app/mcp

The last check completed an MCP handshake.

Registry name
app.cutgpt/research
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free fact-checks, papers, source vetting, plus verified AI pricing, comparisons, guides, and tools.
Listing
From the official MCP registry (active).
Recent checks of CutGPT Research & Fact-Check
CheckedResultHandshake
42 minutes agoHandshake completed100 ms
3 days agoHandshake completed81 ms
13 days agoHandshake completed88 ms
13 days agoHandshake completed94 ms
15 days agoHandshake completed90 ms
15 days agoHandshake completed86 ms
17 days agoHandshake completed81 ms
18 days agoHandshake completed77 ms
18 days agoHandshake completed73 ms
20 days agoHandshake completed77 ms
22 days agoHandshake completed232 ms
25 days agoHandshake completed74 ms
27 days agoHandshake completed69 ms
30 days agoHandshake completed79 ms

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

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 CutGPT Research & Fact-Check and makes no claim about it beyond what these checks measured.