Remote MCP · Endpoint

Imf MCP server

No. Imf answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://gateway.pipeworx.io/imf/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/imf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
IMF MCP — wraps the IMF SDMX 2.1 REST API (api.imf.org)
Listing
From the official MCP registry (active).
Recent checks of Imf
CheckedResultHandshake
2 days agoHandshake completed59 ms
4 days agoHandshake completed94 ms
5 days agoHandshake completed50 ms
7 days agoHandshake completed63 ms
8 days agoHandshake completed81 ms
9 days agoHandshake completed58 ms
12 days agoHandshake completed46 ms
13 days agoHandshake completed66 ms
15 days agoHandshake completed85 ms
17 days agoHandshake completed57 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed43 ms
20 days agoHandshake completed101 ms
20 days agoHandshake completed36 ms
21 days agoHandshake completed40 ms
23 days agoHandshake completed44 ms

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

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