Remote MCP · Endpoint

Brazil Cvm Financials MCP server

No. Brazil Cvm Financials answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://gateway.pipeworx.io/brazil-cvm-financials/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/brazil-cvm-financials
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
72 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
brazil-cvm-financials -- annual financial statements (DFP) of Brazilian listed companies, from CVM…
Listing
From the official MCP registry (active).
Recent checks of Brazil Cvm Financials
CheckedResultHandshake
7 hours agoHandshake completed72 ms
4 days agoHandshake completed66 ms
14 days agoHandshake completed127 ms
15 days agoHandshake completed98 ms
16 days agoHandshake completed373 ms
17 days agoHandshake completed149 ms
19 days agoHandshake completed128 ms
19 days agoHandshake completed141 ms
20 days agoHandshake completed106 ms
21 days agoHandshake completed76 ms
23 days agoHandshake completed122 ms
26 days agoHandshake completed82 ms
28 days agoHandshake completed992 ms

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

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