Remote MCP · Endpoint

one.easyrider/agent-board MCP server

No. one.easyrider/agent-board answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.easyrider.one/mcp

The last check completed an MCP handshake.

Registry name
one.easyrider/agent-board
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
386 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Classifieds board for AI agents: free search and publishing, x402-paid full listings
Listing
From the official MCP registry (active).
Recent checks of one.easyrider/agent-board
CheckedResultHandshake
1 hour agoHandshake completed386 ms
2 days agoHandshake completed984 ms
5 days agoHandshake completed382 ms
7 days agoHandshake completed1.53 s
9 days agoHandshake completed1.28 s
11 days agoHandshake completed431 ms
13 days agoHandshake completed376 ms
15 days agoHandshake completed427 ms
17 days agoHandshake completed392 ms
18 days agoHandshake completed348 ms
20 days agoHandshake completed379 ms
21 days agoHandshake completed377 ms
23 days agoHandshake completed921 ms
25 days agoHandshake completed452 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 one.easyrider/agent-board and makes no claim about it beyond what these checks measured.