Remote MCP · Endpoint

Banxico (Banco de México) MCP server

No. Banxico (Banco de México) answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://banxico-mcp.duckdns.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.nanisadw3/banxico
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
297 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Mexico's official economic data from Banxico: USD/MXN, inflation, UDIS, TIIE and reserves.
Listing
From the official MCP registry (active).
Recent checks of Banxico (Banco de México)
CheckedResultHandshake
19 minutes agoHandshake completed297 ms
9 days agoHandshake completed241 ms
9 days agoHandshake completed250 ms
11 days agoHandshake completed272 ms
12 days agoHandshake completed251 ms
13 days agoHandshake completed302 ms
14 days agoHandshake completed413 ms
14 days agoHandshake completed251 ms
16 days agoHandshake completed268 ms
19 days agoHandshake completed277 ms
21 days agoHandshake completed264 ms
24 days agoHandshake completed379 ms
26 days agoHandshake completed529 ms
28 days agoHandshake completed276 ms

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

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 Banxico (Banco de México) and makes no claim about it beyond what these checks measured.