Remote MCP · Endpoint

rolefig MCP server

No. rolefig answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rolefig.com/mcp

The last check completed an MCP handshake.

Registry name
com.rolefig/rolefig
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search real job openings, check job posts and pay rules, and prepare California offer letters.
Listing
From the official MCP registry (active).
Recent checks of rolefig
CheckedResultHandshake
1 hour agoHandshake completed68 ms
1 day agoHandshake completed82 ms
2 days agoHandshake completed173 ms
3 days agoHandshake completed89 ms
4 days agoHandshake completed141 ms
5 days agoHandshake completed73 ms
6 days agoHandshake completed136 ms
9 days agoHandshake completed125 ms
12 days agoHandshake completed129 ms
14 days agoHandshake completed1.28 s
16 days agoHandshake completed167 ms
18 days agoHandshake completed112 ms
20 days agoHandshake completed91 ms
22 days agoHandshake completed70 ms
24 days agoHandshake completed78 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 rolefig and makes no claim about it beyond what these checks measured.