Remote MCP · Endpoint

Amazap MCP server

No. Amazap answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://amazap.com/mcp

The last check completed an MCP handshake.

Registry name
com.amazap/amazap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Save money on AI spend. Starter credit for eligible new accounts. Details at amazap.com/credits.
Website
https://amazap.com/
Listing
From the official MCP registry (active).
Recent checks of Amazap
CheckedResultHandshake
12 minutes agoHandshake completed80 ms
9 days agoHandshake completed109 ms
9 days agoHandshake completed66 ms
11 days agoHandshake completed73 ms
12 days agoHandshake completed105 ms
13 days agoHandshake completed75 ms
14 days agoHandshake completed77 ms
14 days agoHandshake completed130 ms
16 days agoHandshake completed50 ms
19 days agoHandshake completed80 ms
21 days agoHandshake completed59 ms
24 days agoHandshake completed46 ms
26 days agoCredentials required—
28 days agoCredentials required—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Amazap and makes no claim about it beyond what these checks measured.