Remote MCP · Endpoint
Rust Crate Security Advisories — buy per-query in-session (rustsecwatch) MCP server
No. Rust Crate Security Advisories — buy per-query in-session (rustsecwatch) answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://a2awire.com/mcp/data/rustsecwatch-rustsec-crate-security-advisories-0f9271/http
The last check completed an MCP handshake.
- Registry name
- com.a2awire/data-rust-security-crate-vulnerability
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 104 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Rust crate vulns: CVEs, patched versions. $0.01/query. Register in-session — free testnet funds.
- Repository
- https://github.com/ee324/a2awire
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 104 ms |
| 1 day ago | Handshake completed | 34 ms |
| 2 days ago | Handshake completed | 51 ms |
| 3 days ago | Handshake completed | 114 ms |
| 4 days ago | Handshake completed | 510 ms |
| 5 days ago | Handshake completed | 182 ms |
| 6 days ago | Handshake completed | 123 ms |
| 9 days ago | Handshake completed | 330 ms |
| 12 days ago | Handshake completed | 224 ms |
| 14 days ago | Handshake completed | 398 ms |
| 16 days ago | Handshake completed | 160 ms |
| 18 days ago | Handshake completed | 130 ms |
| 20 days ago | Handshake completed | 89 ms |
| 23 days ago | Handshake completed | 166 ms |
| 25 days ago | Handshake completed | 75 ms |
| 26 days ago | Handshake completed | 103 ms |
| 28 days ago | Handshake completed | 180 ms |
| 29 days ago | Handshake completed | 46 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 Rust Crate Security Advisories — buy per-query in-session (rustsecwatch) and makes no claim about it beyond what these checks measured.