Remote MCP · Endpoint

AgentPixel MCP server

No. AgentPixel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentpixel.io/mcp

The last check completed an MCP handshake.

Registry name
io.agentpixel/agentpixel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
24 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Most visitors never fill out a form. Turn the ones who click Accept into contacts your agent reads.
Listing
From the official MCP registry (active).
Recent checks of AgentPixel
CheckedResultHandshake
1 hour agoHandshake completed24 ms
22 hours agoHandshake completed30 ms
1 day agoHandshake completed42 ms
2 days agoHandshake completed35 ms
4 days agoHandshake completed46 ms
7 days agoHandshake completed63 ms
9 days agoHandshake completed35 ms
12 days agoHandshake completed38 ms
14 days agoHandshake completed28 ms
16 days agoHandshake completed29 ms
18 days agoHandshake completed24 ms
20 days agoHandshake completed24 ms
22 days agoHandshake completed21 ms
23 days agoHandshake completed29 ms

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

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