Remote MCP · Endpoint

AnywhereRoles remote jobs MCP server

No. AnywhereRoles remote jobs answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://anywhereroles.com/mcp

The last check completed an MCP handshake.

Registry name
com.anywhereroles/jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
387 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Remote job search as MCP tools: jobs, companies, categories, salaries. Links to original postings.
Listing
From the official MCP registry (active).
Recent checks of AnywhereRoles remote jobs
CheckedResultHandshake
2 hours agoHandshake completed387 ms
2 days agoHandshake completed408 ms
4 days agoHandshake completed159 ms
7 days agoHandshake completed188 ms
9 days agoHandshake completed140 ms
11 days agoHandshake completed148 ms
13 days agoHandshake completed196 ms
15 days agoHandshake completed166 ms
16 days agoHandshake completed295 ms
18 days agoHandshake completed171 ms
19 days agoHandshake completed292 ms
20 days agoHandshake completed172 ms
23 days agoHandshake completed396 ms
24 days agoHandshake completed190 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 AnywhereRoles remote jobs and makes no claim about it beyond what these checks measured.