Remote MCP · Endpoint

DalalOS MCP server

No. DalalOS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.dalalos.in/mcp

The last check completed an MCP handshake.

Registry name
io.github.aatharva16/dalalos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
333 ms
Tools exposed
61 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Indian NSE/BSE research data and mechanically-computed ratios; read-only market tools.
Listing
From the official MCP registry (active).
Recent checks of DalalOS
CheckedResultHandshake
1 hour agoHandshake completed333 ms
2 days agoHandshake completed340 ms
4 days agoHandshake completed333 ms
5 days agoHandshake completed352 ms
7 days agoHandshake completed590 ms
8 days agoHandshake completed341 ms
9 days agoHandshake completed367 ms
12 days agoHandshake completed385 ms
13 days agoHandshake completed343 ms
15 days agoHandshake completed343 ms
16 days agoHandshake completed345 ms
18 days agoHandshake completed359 ms
19 days agoHandshake completed340 ms
20 days agoHandshake completed342 ms
20 days agoHandshake completed341 ms
21 days agoHandshake completed367 ms
22 days agoHandshake completed373 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 DalalOS and makes no claim about it beyond what these checks measured.