Remote MCP · Endpoint

pro.aemb/agent-embassy MCP server

No. pro.aemb/agent-embassy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aemb.pro/mcp

The last check completed an MCP handshake.

Registry name
pro.aemb/agent-embassy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
25 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Agents pay for work and prove what happened.
Listing
From the official MCP registry (active).
Recent checks of pro.aemb/agent-embassy
CheckedResultHandshake
1 hour agoHandshake completed50 ms
2 days agoHandshake completed50 ms
4 days agoHandshake completed57 ms
6 days agoHandshake completed71 ms
7 days agoHandshake completed97 ms
9 days agoHandshake completed68 ms
10 days agoFailed - the request timed out—
11 days agoHandshake completed52 ms
14 days agoHandshake completed48 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed58 ms
18 days agoHandshake completed56 ms
19 days agoHandshake completed69 ms
21 days agoHandshake completed74 ms
21 days agoHandshake completed76 ms
22 days agoHandshake completed51 ms
23 days agoHandshake completed51 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 pro.aemb/agent-embassy and makes no claim about it beyond what these checks measured.