Remote MCP · Endpoint

pixserp MCP server

No. pixserp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pixserp.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.pixserp/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Listing
From the official MCP registry (active).
Recent checks of pixserp
CheckedResultHandshake
1 hour agoHandshake completed71 ms
2 days agoHandshake completed75 ms
4 days agoHandshake completed1.07 s
5 days agoHandshake completed1.10 s
7 days agoHandshake completed75 ms
8 days agoHandshake completed449 ms
9 days agoHandshake completed4.47 s
12 days agoHandshake completed44 ms
13 days agoHandshake completed129 ms
15 days agoHandshake completed69 ms
16 days agoHandshake completed101 ms
17 days agoHandshake completed68 ms
18 days agoHandshake completed50 ms
19 days agoHandshake completed66 ms
20 days agoHandshake completed59 ms
21 days agoHandshake completed86 ms
22 days agoHandshake completed107 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 pixserp and makes no claim about it beyond what these checks measured.