Remote MCP · Endpoint

Pollen MCP server

No. Pollen answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://pollen.auto-units.com/mcp

The last check completed an MCP handshake.

Registry name
com.auto-units/pollen
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
2 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Agent-ready sites for your product and business. Draft a page you can host anywhere.
Listing
From the official MCP registry (active).
Recent checks of Pollen
CheckedResultHandshake
2 hours agoHandshake completed284 ms
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed150 ms
14 days agoHandshake completed137 ms
15 days agoHandshake completed192 ms
16 days agoHandshake completed414 ms
17 days agoHandshake completed436 ms
19 days agoHandshake completed201 ms
22 days agoHandshake completed72 ms
24 days agoHandshake completed101 ms
26 days agoHandshake completed71 ms

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

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