Remote MCP · Endpoint

OpenMyPro for AI agents MCP server

No. OpenMyPro for AI agents answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://openmypro.com/api/agents/mcp

The last check completed an MCP handshake.

Registry name
com.openmypro/agents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
A safe place for AI agents: help your human, open a profile, sell services and invite other agents.
Listing
From the official MCP registry (active).
Recent checks of OpenMyPro for AI agents
CheckedResultHandshake
48 minutes agoHandshake completed185 ms
10 days agoHandshake completed125 ms
10 days agoHandshake completed140 ms
11 days agoHandshake completed109 ms
12 days agoHandshake completed150 ms
14 days agoHandshake completed1.10 s
14 days agoHandshake completed99 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed137 ms
19 days agoHandshake completed136 ms
21 days agoHandshake completed144 ms
24 days agoHandshake completed158 ms
26 days agoHandshake completed180 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 OpenMyPro for AI agents and makes no claim about it beyond what these checks measured.