Remote MCP · Endpoint

Ambr MCP server

No. Ambr answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://getamber.dev/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.getambr/ambr-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
61 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Ricardian contracts for AI agents — dual-format, SHA-256 bound, legible by construction.
Listing
From the official MCP registry (active).
Recent checks of Ambr
CheckedResultHandshake
2 hours agoHandshake completed61 ms
2 days agoHandshake completed62 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed88 ms
8 days agoHandshake completed108 ms
9 days agoHandshake completed198 ms
12 days agoHandshake completed74 ms
13 days agoHandshake completed93 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed114 ms
18 days agoHandshake completed91 ms
19 days agoHandshake completed95 ms
20 days agoHandshake completed106 ms
20 days agoHandshake completed72 ms
21 days agoHandshake completed84 ms
22 days agoHandshake completed75 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 Ambr and makes no claim about it beyond what these checks measured.