Remote MCP · Endpoint

CheckMyPayRate MCP server

No. CheckMyPayRate answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://checkmypayrate.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.markopints34-tech/checkmypayrate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.15 s
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Salary benchmarks for 20 countries and 13 sectors from OECD and Eurostat data.
Listing
From the official MCP registry (active).
Recent checks of CheckMyPayRate
CheckedResultHandshake
6 hours agoHandshake completed1.15 s
2 days agoHandshake completed772 ms
5 days agoHandshake completed912 ms
7 days agoHandshake completed1.17 s
9 days agoHandshake completed2.11 s
11 days agoHandshake completed1.41 s
13 days agoHandshake completed1.22 s
15 days agoHandshake completed1.27 s
17 days agoHandshake completed693 ms
18 days agoHandshake completed845 ms
20 days agoHandshake completed778 ms
21 days agoHandshake completed717 ms
23 days agoHandshake completed1.81 s

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

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