Remote MCP · Endpoint

MentionFox MCP server

No. MentionFox answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://mentionfox.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.OsakaSaul/mentionfox
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
410 ms
Tools exposed
10 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Company and people checks: red flags, funding, leadership. Every claim cited. Free to try.
Listing
From the official MCP registry (active).
Recent checks of MentionFox
CheckedResultHandshake
56 minutes agoHandshake completed410 ms
3 days agoHandshake completed294 ms
12 days agoHandshake completed484 ms
13 days agoHandshake completed407 ms
15 days agoHandshake completed446 ms
15 days agoHandshake completed466 ms
17 days agoHandshake completed376 ms
18 days agoHandshake completed448 ms
18 days agoHandshake completed443 ms
20 days agoHandshake completed510 ms
22 days agoHandshake completed423 ms
25 days agoHandshake completed492 ms
27 days agoFailed - the check failed for an unclassified reason—
29 days agoFailed - the check failed for an unclassified reason—

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

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