Remote MCP · Endpoint

Money Mind — the judge MCP server

No. Money Mind — the judge answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://money-mind-extract.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Elimuaa/money-mind
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
251 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Statistical adjudication for agents: backtest judges, fact-checks. Pay per call in USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of Money Mind — the judge
CheckedResultHandshake
1 hour agoHandshake completed251 ms
2 days agoHandshake completed133 ms
5 days agoHandshake completed122 ms
7 days agoHandshake completed157 ms
9 days agoHandshake completed340 ms
11 days agoHandshake completed157 ms
13 days agoHandshake completed137 ms
15 days agoHandshake completed334 ms
17 days agoHandshake completed245 ms
19 days agoHandshake completed136 ms
20 days agoHandshake completed136 ms
21 days agoHandshake completed237 ms
22 days agoHandshake completed287 ms
25 days agoHandshake completed138 ms

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

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 Money Mind — the judge and makes no claim about it beyond what these checks measured.