Remote MCP · Endpoint

Jawne Stawki MCP server

No. Jawne Stawki answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://jawnestawki.pl/mcp

The last check completed an MCP handshake.

Registry name
pl.jawnestawki/salaries
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
256 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Salaries in Poland from public job ads: occupations, cities, contract types, experience.
Website
https://jawnestawki.pl/api
Listing
From the official MCP registry (active).
Recent checks of Jawne Stawki
CheckedResultHandshake
1 hour agoHandshake completed256 ms
2 days agoHandshake completed363 ms
5 days agoHandshake completed440 ms
7 days agoHandshake completed350 ms
9 days agoHandshake completed225 ms
11 days agoHandshake completed242 ms
13 days agoHandshake completed253 ms
15 days agoHandshake completed204 ms
17 days agoHandshake completed104 ms
19 days agoHandshake completed203 ms
20 days agoHandshake completed331 ms
21 days agoHandshake completed216 ms
23 days agoHandshake completed202 ms

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Jawne Stawki and makes no claim about it beyond what these checks measured.