Remote MCP · Endpoint
rust.wiki MCP server
No. rust.wiki answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://rust.wiki/mcp
The last check completed an MCP handshake.
- Registry name
- wiki.rust/rust-wiki
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 184 ms
- Tools exposed
- 183 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Live data for the game Rust: skin prices and history, items, item store, loot tables, servers.
- Website
- https://rust.wiki/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 184 ms |
| 4 days ago | Handshake completed | 1.31 s |
| 14 days ago | Handshake completed | 147 ms |
| 15 days ago | Handshake completed | 251 ms |
| 15 days ago | Handshake completed | 347 ms |
| 17 days ago | Handshake completed | 325 ms |
| 18 days ago | Handshake completed | 317 ms |
| 19 days ago | Handshake completed | 314 ms |
| 20 days ago | Handshake completed | 462 ms |
| 21 days ago | Handshake completed | 316 ms |
| 23 days ago | Handshake completed | 167 ms |
| 25 days ago | Handshake completed | 324 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 rust.wiki and makes no claim about it beyond what these checks measured.