Remote MCP · Endpoint

Port 25 MCP server

No. Port 25 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/port-25/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/port-25
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
131 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Whether 25 is a common TCP/UDP port.
Listing
From the official MCP registry (active).
Recent checks of Port 25
CheckedResultHandshake
1 hour agoHandshake completed131 ms
2 days agoHandshake completed21 ms
4 days agoHandshake completed21 ms
6 days agoHandshake completed17 ms
7 days agoHandshake completed30 ms
8 days agoHandshake completed27 ms
9 days agoHandshake completed28 ms
12 days agoHandshake completed18 ms
14 days agoHandshake completed21 ms
15 days agoHandshake completed14 ms
17 days agoHandshake completed10 ms
18 days agoHandshake completed14 ms
19 days agoHandshake completed10 ms
20 days agoHandshake completed35 ms
21 days agoHandshake completed19 ms
22 days agoHandshake completed14 ms
23 days agoHandshake completed11 ms

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

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