Remote MCP · Endpoint

Owid MCP server

No. Owid answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/owid
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
OWID MCP — Our World in Data chart/indicator access (free, no auth)
Listing
From the official MCP registry (active).
Recent checks of Owid
CheckedResultHandshake
3 hours agoHandshake completed151 ms
1 day agoHandshake completed152 ms
3 days agoHandshake completed98 ms
3 days agoHandshake completed129 ms
4 days agoHandshake completed101 ms
6 days agoHandshake completed1.90 s
7 days agoHandshake completed113 ms
10 days agoHandshake completed135 ms
13 days agoHandshake completed78 ms
15 days agoHandshake completed64 ms
17 days agoHandshake completed66 ms
19 days agoHandshake completed61 ms
21 days agoHandshake completed48 ms
23 days agoHandshake completed57 ms
25 days agoHandshake completed71 ms
27 days agoHandshake completed50 ms
28 days agoHandshake completed67 ms
29 days agoHandshake completed79 ms

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

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