Remote MCP · Endpoint

Ambolt MCP server

No. Ambolt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.ambolt.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.ambolt/ambolt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
401 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Company registers, financials, funding rounds, tenders and industry codes. Sourced and dated.
Website
https://ambolt.dev/
Listing
From the official MCP registry (active).
Recent checks of Ambolt
CheckedResultHandshake
1 hour agoHandshake completed401 ms
2 days agoHandshake completed320 ms
5 days agoHandshake completed362 ms
7 days agoHandshake completed356 ms
9 days agoHandshake completed366 ms
11 days agoHandshake completed336 ms
13 days agoHandshake completed335 ms
15 days agoHandshake completed496 ms
17 days agoHandshake completed335 ms
18 days agoHandshake completed313 ms
20 days agoHandshake completed360 ms
21 days agoHandshake completed400 ms
23 days agoHandshake completed322 ms
25 days agoHandshake completed353 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.

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 Ambolt and makes no claim about it beyond what these checks measured.