Grey Ridge Jobs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Fetch live, normalized open job postings for one or more companies across 7 ATS platforms (Greenhouse, Lever, Ashby, SmartRecruiters, Workday, Recruitee, Workable). Each company may be given as a bare slug ("stripe"), a domain ("stripe.com"), or an explicit "platform:token" ("greenhouse:stripe", "lever:palantir", "workday:nvidia.wd5:NVIDIAExternalCareerSite"). The ATS and board token are auto-detected for slugs/domains. Returns a unified schema: title, company, location, remote, employment_type, department, posted_at (ISO), salary, url, source_platform. |
| detect_atsA | Resolve which applicant-tracking system a company uses and its board token, from a bare slug or domain, without pulling the full posting list. Returns {platform, token} or a not-detected result. Cheap probe — use before search_jobs when you only need to know the ATS. |
| list_platformsA | List the ATS platforms this server supports and how to address each one (token format, whether auto-detect covers it). No network call. |
| search_hn_hiringA | Search the CURRENT month's Hacker News "Ask HN: Who is hiring?" thread for live job postings, normalized into the same unified schema as search_jobs (title, company, location, remote, employment_type, salary, url, source_platform). The monthly thread id is auto-discovered (it rotates on the 1st of every month) and each free-text post header is parsed into structured fields. Optionally filter by a keyword and/or remote-only. No company list needed — this is the whole thread. source_platform is "hn"; url is the apply link when present, else the HN permalink. |
| get_premium_accessA | Describe the metered depth endpoints available beyond this free server: a normalized cross-ATS compensation layer, a per-company hiring-intent signal, and a hosted high-volume multi-ATS search. These are served pay-per-call over x402 (USDC on Base, no account/API key — the caller's wallet pays the 402 inline). Returns the base URL, each endpoint's path + USD price + what it adds, and the exact payment parameters (network, asset, pay-to, handshake). No network call, no payment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: detect_ats is a cheap probe, search_jobs fetches company postings, search_hn_hiring pulls a different source, list_platforms is static metadata, and get_premium_access is informational. The only mild overlap is that search_jobs already auto-detects the ATS, which makes detect_ats somewhat redundant unless the caller explicitly wants the probe — but the descriptions call this out clearly.
All five names follow a clean verb_noun snake_case convention (detect_ats, search_jobs, list_platforms, search_hn_hiring, get_premium_access) with no mixed styles or vague verbs.
Five tools is well within the sweet spot and each one earns its place: ATS detection, ATS job search, platform enumeration, HN thread search, and premium-tier discovery. Nothing feels padded or missing at the count level.
Core discovery workflows are covered — search across 7 ATS platforms plus HN, with a unified schema that includes url, salary, and remote flags. Minor gaps: search_jobs doesn't advertise keyword/location/remote filters (unlike search_hn_hiring), and there's no job-detail or company-listing operation, though agents can work around these via the returned urls.