Remote MCP · Endpoint

cc.accrue/mcp MCP server

No. cc.accrue/mcp answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://accrue.cc/mcp

The last check completed an MCP handshake.

Registry name
cc.accrue/mcp
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
78 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Stablecoin Yield Index (SYX) and live USDC vault APYs across Ethereum, Base, Arbitrum.
Listing
From the official MCP registry (active).
Recent checks of cc.accrue/mcp
CheckedResultHandshake
9 hours agoHandshake completed78 ms
2 days agoHandshake completed119 ms
4 days agoHandshake completed321 ms
5 days agoHandshake completed105 ms
7 days agoHandshake completed70 ms
8 days agoHandshake completed64 ms
9 days agoHandshake completed101 ms
12 days agoHandshake completed58 ms
14 days agoHandshake completed110 ms
15 days agoHandshake completed118 ms
16 days agoHandshake completed63 ms
18 days agoHandshake completed78 ms
19 days agoHandshake completed165 ms
19 days agoHandshake completed130 ms
20 days agoHandshake completed89 ms
21 days agoHandshake completed62 ms
23 days agoHandshake completed56 ms

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

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 cc.accrue/mcp and makes no claim about it beyond what these checks measured.