Remote MCP · Endpoint

Ask Bob: Moneytalk Archive MCP server

No. Ask Bob: Moneytalk Archive answered an MCP handshake 22 hours ago.

UpLast checked 22 hours ago

Server URL

https://mcp.brinkeradvisor.com/mcp/audio

The last check completed an MCP handshake.

Registry name
io.github.adpadinc/brinkeradvisor-moneytalk-archive
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
218 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search reviewed Moneytalk topic and date metadata through September 30, 2018.
Listing
From the official MCP registry (active).
Recent checks of Ask Bob: Moneytalk Archive
CheckedResultHandshake
22 hours agoHandshake completed218 ms
11 days agoHandshake completed227 ms
11 days agoHandshake completed236 ms
12 days agoHandshake completed280 ms
14 days agoHandshake completed221 ms
15 days agoHandshake completed219 ms
15 days agoHandshake completed215 ms
16 days agoHandshake completed216 ms
18 days agoHandshake completed248 ms
20 days agoHandshake completed231 ms
22 days agoHandshake completed229 ms
25 days agoHandshake completed226 ms
27 days agoHandshake completed234 ms
29 days agoHandshake completed234 ms

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

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 Ask Bob: Moneytalk Archive and makes no claim about it beyond what these checks measured.