Remote MCP · Endpoint

Find My Money MCP server

No. Find My Money answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://goodturn-mcp.pages.dev/findmymoney/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/findmymoney
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
40 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find unclaimed money in the US and UK: the official free searches and how to claim.
Listing
From the official MCP registry (active).
Recent checks of Find My Money
CheckedResultHandshake
56 minutes agoHandshake completed40 ms
3 days agoHandshake completed310 ms
12 days agoHandshake completed142 ms
13 days agoHandshake completed73 ms
15 days agoHandshake completed69 ms
15 days agoHandshake completed83 ms
17 days agoHandshake completed59 ms
18 days agoHandshake completed69 ms
18 days agoHandshake completed56 ms
20 days agoHandshake completed76 ms
22 days agoHandshake completed60 ms
25 days agoHandshake completed52 ms
27 days agoHandshake completed49 ms
29 days agoHandshake completed94 ms

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

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