Remote MCP · Endpoint

Blue Dot Brdg (BLDT) MCP server

No. Blue Dot Brdg (BLDT) answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://bldt.in/mcp

The last check completed an MCP handshake.

Registry name
in.bldt/blue-dot-brdg
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
India market entry, ecommerce and fulfilment for consumer brands (Blue Dot Brdg, BLDT).
Listing
From the official MCP registry (active).
Recent checks of Blue Dot Brdg (BLDT)
CheckedResultHandshake
20 minutes agoHandshake completed307 ms
3 days agoHandshake completed288 ms
14 days agoHandshake completed289 ms
14 days agoHandshake completed284 ms
15 days agoHandshake completed297 ms
16 days agoHandshake completed281 ms
18 days agoHandshake completed288 ms
18 days agoHandshake completed297 ms
19 days agoHandshake completed306 ms
21 days agoHandshake completed497 ms
22 days agoHandshake completed298 ms
25 days agoHandshake completed293 ms

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

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 Blue Dot Brdg (BLDT) and makes no claim about it beyond what these checks measured.