Remote MCP · Endpoint

Plate Website Source MCP server

No. Plate Website Source answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://getplate.pages.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ohad6k/plate-website-source
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
91 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only catalog of free Plate website source projects a coding agent can adapt.
Listing
From the official MCP registry (active).
Recent checks of Plate Website Source
CheckedResultHandshake
2 hours agoHandshake completed91 ms
2 days agoHandshake completed111 ms
4 days agoHandshake completed110 ms
6 days agoHandshake completed98 ms
9 days agoHandshake completed62 ms
11 days agoHandshake completed91 ms
13 days agoHandshake completed68 ms
14 days agoHandshake completed82 ms
16 days agoHandshake completed78 ms
17 days agoHandshake completed87 ms
18 days agoHandshake completed112 ms
21 days agoHandshake completed72 ms
22 days agoHandshake completed80 ms
24 days agoHandshake completed111 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 Plate Website Source and makes no claim about it beyond what these checks measured.