Remote MCP · Endpoint

BR Intelligence MCP server

No. BR Intelligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
179 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Brazil PTAX, CNPJ/KYB, CEIS-CNEP sanctions, PIX and boleto. Paid x402 MCP API (USDC on Base).
Listing
From the official MCP registry (active).
Recent checks of BR Intelligence
CheckedResultHandshake
1 hour agoHandshake completed179 ms
10 days agoHandshake completed232 ms
10 days agoHandshake completed231 ms
11 days agoHandshake completed352 ms
12 days agoHandshake completed184 ms
14 days agoHandshake completed236 ms
14 days agoHandshake completed193 ms
15 days agoHandshake completed168 ms
17 days agoHandshake completed220 ms
19 days agoHandshake completed315 ms
21 days agoHandshake completed152 ms
24 days agoHandshake completed204 ms
26 days agoHandshake completed437 ms
28 days agoHandshake completed61 ms

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

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.