Remote MCP · Endpoint

agentView MCP server

No. agentView answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentview.de/mcp

The last check completed an MCP handshake.

Registry name
de.agentview/agentview-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
57 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Display delivery platform for AI agents. Push HTML, dashboards and live data to screens.
Listing
From the official MCP registry (active).
Recent checks of agentView
CheckedResultHandshake
1 hour agoHandshake completed294 ms
2 days agoHandshake completed298 ms
4 days agoHandshake completed313 ms
5 days agoHandshake completed294 ms
7 days agoHandshake completed312 ms
8 days agoHandshake completed292 ms
9 days agoHandshake completed302 ms
12 days agoHandshake completed292 ms
13 days agoHandshake completed290 ms
15 days agoHandshake completed312 ms
16 days agoHandshake completed300 ms
18 days agoHandshake completed299 ms
19 days agoHandshake completed295 ms
20 days agoHandshake completed327 ms
20 days agoHandshake completed315 ms
21 days agoHandshake completed393 ms
22 days agoHandshake completed297 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 agentView and makes no claim about it beyond what these checks measured.