Remote MCP · Endpoint
ai.ironscout/ironscout MCP server
No. ai.ironscout/ironscout answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://mcp.ironscout.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.ironscout/ironscout
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 162 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Read-only ammo pricing: offer search, caliber market snapshots, retailer directory. Descriptive.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 162 ms |
| 1 day ago | Handshake completed | 140 ms |
| 3 days ago | Handshake completed | 120 ms |
| 3 days ago | Handshake completed | 116 ms |
| 4 days ago | Handshake completed | 134 ms |
| 5 days ago | Handshake completed | 123 ms |
| 7 days ago | Handshake completed | 141 ms |
| 10 days ago | Handshake completed | 164 ms |
| 12 days ago | Handshake completed | 126 ms |
| 15 days ago | Handshake completed | 197 ms |
| 17 days ago | Handshake completed | 497 ms |
| 19 days ago | Handshake completed | 166 ms |
| 21 days ago | Handshake completed | 219 ms |
| 23 days ago | Handshake completed | 139 ms |
| 25 days ago | Handshake completed | 216 ms |
| 26 days ago | Handshake completed | 137 ms |
| 28 days ago | Handshake completed | 132 ms |
| 29 days ago | Handshake completed | 386 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 ai.ironscout/ironscout and makes no claim about it beyond what these checks measured.