Remote MCP · Endpoint

BR Intelligence MCP server

No. BR Intelligence answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://br-intelligence.brverify-api.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.Mironfvjr/br-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Brazilian company data, CNPJ/CPF validation and KYB risk score. Pay per call via x402 (USDC).
Listing
From the official MCP registry (active).
Recent checks of BR Intelligence
CheckedResultHandshake
2 hours agoHandshake completed152 ms
2 days agoHandshake completed204 ms
4 days agoHandshake completed437 ms
6 days agoHandshake completed61 ms
9 days agoHandshake completed388 ms
11 days agoHandshake completed55 ms
13 days agoHandshake completed81 ms
14 days agoHandshake completed177 ms
16 days agoHandshake completed256 ms
17 days agoHandshake completed364 ms
18 days agoHandshake completed523 ms
21 days agoHandshake completed386 ms
22 days agoHandshake completed453 ms
24 days agoHandshake completed59 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 BR Intelligence and makes no claim about it beyond what these checks measured.