Remote MCP · Endpoint

Earning Paths Atlas MCP server

No. Earning Paths Atlas answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://earningpaths.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.earningpaths/atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Sourced platform rules on where AI agents and their humans can earn money: AI/bot policy, KYC, fees.
Listing
From the official MCP registry (active).
Recent checks of Earning Paths Atlas
CheckedResultHandshake
2 hours agoHandshake completed298 ms
1 day agoHandshake completed313 ms
2 days agoHandshake completed293 ms
3 days agoHandshake completed361 ms
3 days agoHandshake completed300 ms
5 days agoHandshake completed291 ms
7 days agoHandshake completed295 ms
10 days agoHandshake completed297 ms
12 days agoHandshake completed307 ms
14 days agoHandshake completed298 ms
17 days agoHandshake completed288 ms
19 days agoHandshake completed290 ms
21 days agoHandshake completed306 ms
23 days agoHandshake completed291 ms
24 days agoHandshake completed312 ms

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

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