Remote MCP · Endpoint

com.pirchjobs/pirch MCP server

No. com.pirchjobs/pirch answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pirchjobs.com/mcp

The last check completed an MCP handshake.

Registry name
com.pirchjobs/pirch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
285 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verified job search: every listing confirmed live and accepting applicants within the last 72h.
Website
https://pirchjobs.com/
Listing
From the official MCP registry (active).
Recent checks of com.pirchjobs/pirch
CheckedResultHandshake
1 hour agoHandshake completed285 ms
2 days agoHandshake completed380 ms
4 days agoHandshake completed353 ms
5 days agoHandshake completed1.02 s
7 days agoHandshake completed349 ms
8 days agoHandshake completed301 ms
9 days agoHandshake completed290 ms
12 days agoHandshake completed766 ms
13 days agoHandshake completed2.38 s
15 days agoHandshake completed359 ms
16 days agoHandshake completed478 ms
17 days agoHandshake completed388 ms
18 days agoHandshake completed467 ms
19 days agoHandshake completed321 ms
20 days agoHandshake completed510 ms
21 days agoHandshake completed830 ms
22 days agoHandshake completed578 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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.

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