Remote MCP · Endpoint

Opafex MCP server

No. Opafex answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://opafex.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.opafex/business-automation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Helps UK small business owners decide where AI fits: what to automate first, data checks, payback.
Listing
From the official MCP registry (active).
Recent checks of Opafex
CheckedResultHandshake
1 hour agoHandshake completed79 ms
20 hours agoHandshake completed88 ms
2 days agoHandshake completed508 ms
3 days agoHandshake completed645 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed421 ms
6 days agoHandshake completed935 ms
8 days agoHandshake completed83 ms
11 days agoHandshake completed1.05 s
13 days agoHandshake completed883 ms
15 days agoHandshake completed954 ms
18 days agoHandshake completed128 ms
19 days agoHandshake completed132 ms
22 days agoHandshake completed71 ms

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