Remote MCP · Endpoint

MRR Ledger MCP server

No. MRR Ledger answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mrrledger.com/mcp

The last check completed an MCP handshake.

Registry name
com.mrrledger/mrrledger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
714 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free, no key: sourced, dated revenue of real AI-agent businesses. Start with search_businesses.
Listing
From the official MCP registry (active).
Recent checks of MRR Ledger
CheckedResultHandshake
4 hours agoHandshake completed714 ms
10 days agoHandshake completed477 ms
11 days agoHandshake completed444 ms
11 days agoHandshake completed344 ms
13 days agoHandshake completed272 ms
14 days agoHandshake completed266 ms
15 days agoHandshake completed279 ms
16 days agoHandshake completed249 ms
17 days agoHandshake completed314 ms
19 days agoHandshake completed451 ms
22 days agoHandshake completed808 ms
24 days agoHandshake completed662 ms
26 days agoHandshake completed474 ms
29 days agoHandshake completed95 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 MRR Ledger and makes no claim about it beyond what these checks measured.