Remote MCP · Endpoint

Openings MCP server

No. Openings answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://openings.avagama.co/mcp

The last check completed an MCP handshake.

Registry name
co.avagama/openings
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
4 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Search jobs on verified employer job boards. Every link is the employer's own posting.
Listing
From the official MCP registry (active).
Recent checks of Openings
CheckedResultHandshake
1 hour agoHandshake completed124 ms
2 days agoHandshake completed137 ms
4 days agoHandshake completed216 ms
5 days agoFailed - the request timed out—
7 days agoHandshake completed200 ms
8 days agoHandshake completed922 ms
9 days agoCredentials required—
12 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
17 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—

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

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