Remote MCP · Endpoint
bitfence Risk Oracle MCP server
No. bitfence Risk Oracle answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.bitfence.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.bitfenceai/bitfence
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 395 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.
- Website
- https://www.bitfence.ai/
- Repository
- https://github.com/bitfenceai/bitfence
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 395 ms |
| 2 days ago | Handshake completed | 496 ms |
| 4 days ago | Handshake completed | 324 ms |
| 5 days ago | Handshake completed | 328 ms |
| 7 days ago | Handshake completed | 401 ms |
| 8 days ago | Handshake completed | 329 ms |
| 9 days ago | Handshake completed | 342 ms |
| 12 days ago | Handshake completed | 326 ms |
| 13 days ago | Handshake completed | 330 ms |
| 15 days ago | Handshake completed | 359 ms |
| 16 days ago | Handshake completed | 333 ms |
| 18 days ago | Handshake completed | 328 ms |
| 19 days ago | Handshake completed | 328 ms |
| 20 days ago | Handshake completed | 329 ms |
| 20 days ago | Handshake completed | 329 ms |
| 21 days ago | Handshake completed | 358 ms |
| 22 days ago | Handshake completed | 357 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 bitfence Risk Oracle and makes no claim about it beyond what these checks measured.