Remote MCP · Endpoint
io.github.SirCharan/ipoallotment MCP server
No. io.github.SirCharan/ipoallotment answered an MCP handshake 1 day ago.
UpLast checked 1 day ago
Server URL
https://ipoallotmentcheck.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.SirCharan/ipoallotment
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 112 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 10 checks
- Described by its publisher as
- Check Indian IPO allotment by PAN and list mainboard and SME IPOs with listing gains.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 day ago | Handshake completed | 112 ms |
| 5 days ago | Handshake completed | 159 ms |
| 16 days ago | Handshake completed | 1.44 s |
| 16 days ago | Handshake completed | 231 ms |
| 17 days ago | Handshake completed | 115 ms |
| 19 days ago | Handshake completed | 162 ms |
| 20 days ago | Handshake completed | 139 ms |
| 21 days ago | Handshake completed | 102 ms |
| 22 days ago | Handshake completed | 143 ms |
| 23 days ago | Handshake completed | 119 ms |
The last 10 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 10.
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 io.github.SirCharan/ipoallotment and makes no claim about it beyond what these checks measured.