Remote MCP · Endpoint

Amendor MCP server

No. Amendor answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://amendor.site/mcp

The last check completed an MCP handshake.

Registry name
io.github.deslay1/amendor-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Pull change requests from your Amendor board into your coding agent to build and open PRs.
Listing
From the official MCP registry (active).
Recent checks of Amendor
CheckedResultHandshake
2 hours agoHandshake completed122 ms
2 days agoHandshake completed119 ms
4 days agoHandshake completed126 ms
5 days agoHandshake completed128 ms
7 days agoHandshake completed136 ms
8 days agoHandshake completed105 ms
9 days agoHandshake completed119 ms
12 days agoHandshake completed141 ms
13 days agoHandshake completed116 ms
15 days agoHandshake completed125 ms
17 days agoHandshake completed109 ms
18 days agoHandshake completed133 ms
19 days agoHandshake completed129 ms
20 days agoHandshake completed123 ms
20 days agoHandshake completed127 ms
21 days agoHandshake completed131 ms
23 days agoHandshake completed105 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 Amendor and makes no claim about it beyond what these checks measured.