pirch — verified jobs MCP server

A public, read-only MCP server for verified job listings. Every job it returns was opened and confirmed live and accepting applicants within the last 72 hours, and re-verified on a rolling clock — so agents can recommend jobs without ghost-job or dead-link risk.

Remote endpoint (streamable HTTP, no auth, no API key):

https://pirchjobs.com/mcp

Tools

tool	what it does
`get_jobs_overview`	pool stats: how many verified jobs, by role/region
`search_verified_jobs`	search the verified pool (role, location, workmode)
`get_verified_job`	full detail for one listing, incl. direct apply URL

Use it

Remote (recommended) — any client that speaks remote MCP:

{ "mcpServers": { "pirch": { "url": "https://pirchjobs.com/mcp" } } }

stdio bridge — for clients and runners that only speak stdio, this repo ships a tiny dependency-free bridge that forwards stdio JSON-RPC to the remote endpoint:

{ "mcpServers": { "pirch": { "command": "npx", "args": ["-y", "github:rinohed/pirch-mcp"] } } }

or run it directly:

node proxy.mjs                     # defaults to https://pirchjobs.com/mcp
PIRCH_MCP_URL=… node proxy.mjs     # or point it somewhere else

Docker — same bridge, containerised:

docker build -t pirch-mcp . && docker run -i --rm pirch-mcp

Why "verified"

Job listings decay fast. We re-opened 1,165 listings we had previously confirmed live: 27% of the checkable ones were already deleted, and 1 in 8 died within three days of a live check. Freshness is a process, not a property — so pirch keeps re-checking, and anything it can't confirm falls out of the pool.

Method and raw data: why job postings disappear

pirch — verified jobs MCP server

Tools

Use it

Why "verified"

Links