Remote MCP · Endpoint

Agent Connectors MCP server

No. Agent Connectors answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://agentconnectors.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.JaniJegoroff/agent-connectors-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
441 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only search of the Agent Connectors MCP directory.
Listing
From the official MCP registry (active).
Recent checks of Agent Connectors
CheckedResultHandshake
34 minutes agoHandshake completed441 ms
8 days agoHandshake completed111 ms
9 days agoHandshake completed143 ms
11 days agoHandshake completed799 ms
12 days agoHandshake completed1.06 s
12 days agoHandshake completed1.02 s
14 days agoHandshake completed989 ms
14 days agoHandshake completed821 ms
16 days agoHandshake completed168 ms
19 days agoHandshake completed102 ms
21 days agoHandshake completed996 ms
24 days agoHandshake completed1.11 s
26 days agoHandshake completed140 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 Agent Connectors and makes no claim about it beyond what these checks measured.