Remote MCP · Endpoint

io.github.benji7891/macro-pulse-x402 MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://macro-pulse-x402.onrender.com/mcp/

The last check failed: the server returned an HTTP error.

Registry name
io.github.benji7891/macro-pulse-x402
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Country economic momentum score (GDP, inflation, unemployment) via x402 USDC micropayments.
Listing
From the official MCP registry (active).
Recent checks of io.github.benji7891/macro-pulse-x402
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoHandshake completed157 ms
2 days agoHandshake completed173 ms
3 days agoHandshake completed135 ms
4 days agoHandshake completed146 ms
5 days agoHandshake completed140 ms
6 days agoHandshake completed136 ms
9 days agoHandshake completed271 ms
12 days agoHandshake completed257 ms
14 days agoHandshake completed280 ms
16 days agoHandshake completed253 ms
18 days agoHandshake completed159 ms
20 days agoHandshake completed164 ms
22 days agoHandshake completed179 ms
24 days agoHandshake completed121 ms
26 days agoHandshake completed292 ms
27 days agoHandshake completed163 ms
29 days agoHandshake completed314 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 io.github.benji7891/macro-pulse-x402 and makes no claim about it beyond what these checks measured.