Remote MCP · Endpoint

Remote Impact Jobs MCP server

No. Remote Impact Jobs answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://remoteimpact.org/mcp/

The last check completed an MCP handshake.

Registry name
org.remoteimpact/jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
517 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified remote jobs at impact organizations: search by area, country eligibility, level and pay.
Listing
From the official MCP registry (active).
Recent checks of Remote Impact Jobs
CheckedResultHandshake
20 minutes agoHandshake completed517 ms
9 days agoHandshake completed167 ms
9 days agoHandshake completed225 ms
11 days agoHandshake completed180 ms
12 days agoHandshake completed338 ms
13 days agoHandshake completed178 ms
14 days agoHandshake completed226 ms
14 days agoHandshake completed250 ms
16 days agoHandshake completed182 ms
19 days agoHandshake completed200 ms
21 days agoHandshake completed185 ms
24 days agoHandshake completed963 ms
26 days agoHandshake completed222 ms
28 days agoHandshake completed183 ms

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

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 Remote Impact Jobs and makes no claim about it beyond what these checks measured.