Remote MCP · Endpoint

Idb MCP server

No. Idb answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/idb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
IDB (Inter-American Development Bank) Procurement MCP.
Listing
From the official MCP registry (active).
Recent checks of Idb
CheckedResultHandshake
1 hour agoHandshake completed87 ms
1 day agoHandshake completed151 ms
2 days agoHandshake completed350 ms
3 days agoHandshake completed720 ms
4 days agoHandshake completed192 ms
5 days agoHandshake completed64 ms
6 days agoHandshake completed314 ms
9 days agoHandshake completed110 ms
12 days agoHandshake completed71 ms
14 days agoHandshake completed100 ms
16 days agoHandshake completed169 ms
18 days agoHandshake completed61 ms
21 days agoHandshake completed505 ms
23 days agoHandshake completed65 ms
25 days agoHandshake completed53 ms
26 days agoHandshake completed68 ms
28 days agoHandshake completed52 ms
29 days agoHandshake completed202 ms

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

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