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
340 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Pre-transaction token risk checks for autonomous agents on six chains. Read-only; paid via x402.
Listing
From the official MCP registry (active).
Recent checks of bitfence Risk Oracle
CheckedResultHandshake
1 hour agoHandshake completed340 ms
1 day agoHandshake completed358 ms
2 days agoHandshake completed328 ms
3 days agoHandshake completed337 ms
4 days agoHandshake completed328 ms
5 days agoHandshake completed340 ms
6 days agoHandshake completed387 ms
9 days agoHandshake completed330 ms
12 days agoHandshake completed388 ms
14 days agoHandshake completed330 ms
16 days agoHandshake completed338 ms
18 days agoHandshake completed359 ms
20 days agoHandshake completed395 ms
22 days agoHandshake completed496 ms
24 days agoHandshake completed324 ms
26 days agoHandshake completed328 ms
27 days agoHandshake completed401 ms
29 days agoHandshake completed329 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 bitfence Risk Oracle and makes no claim about it beyond what these checks measured.