Remote MCP · Endpoint

Nber Macrohistory MCP server

No. Nber Macrohistory answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/nber-macrohistory/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nber-macrohistory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
63 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
NBER Macrohistory Database — the National Bureau of Economic Research's 'Public Use Data Archive'…
Listing
From the official MCP registry (active).
Recent checks of Nber Macrohistory
CheckedResultHandshake
1 hour agoHandshake completed63 ms
10 days agoHandshake completed1.38 s
10 days agoHandshake completed93 ms
11 days agoHandshake completed125 ms
12 days agoHandshake completed205 ms
14 days agoHandshake completed103 ms
14 days agoHandshake completed229 ms
15 days agoHandshake completed67 ms
17 days agoHandshake completed212 ms
19 days agoHandshake completed93 ms
21 days agoHandshake completed65 ms
24 days agoHandshake completed142 ms
26 days agoHandshake completed403 ms
28 days agoHandshake completed69 ms

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

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