Remote MCP · Endpoint

Agentel Network MCP server

No. Agentel Network answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentel.tech/mcp

The last check completed an MCP handshake.

Registry name
io.github.agentel-tech/agentel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
187 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Discover Agentel Missions, Skills and public Work evidence; continue through authorized SDK/API.
Listing
From the official MCP registry (active).
Recent checks of Agentel Network
CheckedResultHandshake
1 hour agoHandshake completed187 ms
18 hours agoHandshake completed44 ms
2 days agoHandshake completed308 ms
3 days agoHandshake completed54 ms
4 days agoHandshake completed789 ms
5 days agoHandshake completed455 ms
6 days agoHandshake completed73 ms
7 days agoHandshake completed159 ms
10 days agoHandshake completed270 ms
13 days agoHandshake completed221 ms
15 days agoHandshake completed261 ms
17 days agoHandshake completed363 ms
19 days agoHandshake completed198 ms
21 days agoHandshake completed209 ms
23 days agoHandshake completed203 ms
25 days agoHandshake completed189 ms

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

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