Remote MCP · Endpoint

BrinkerAdvisor Rates MCP server

No. BrinkerAdvisor Rates answered an MCP handshake 40 minutes ago.

UpLast checked 40 minutes ago

Server URL

https://mcp.brinkeradvisor.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.adpadinc/brinkeradvisor-rates
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
333 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public CD, money-market and Treasury records with data dates, source links and illustrative ladders.
Listing
From the official MCP registry (active).
Recent checks of BrinkerAdvisor Rates
CheckedResultHandshake
40 minutes agoHandshake completed333 ms
3 days agoHandshake completed597 ms
12 days agoHandshake completed216 ms
12 days agoHandshake completed219 ms
14 days agoHandshake completed235 ms
15 days agoHandshake completed215 ms
16 days agoHandshake completed226 ms
17 days agoHandshake completed223 ms
18 days agoHandshake completed248 ms
19 days agoHandshake completed227 ms
22 days agoHandshake completed229 ms
25 days agoHandshake completed372 ms
27 days agoHandshake completed284 ms
29 days agoHandshake completed219 ms

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

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