# Fairquery Company Jobs Feed (npm · @fairquery/company-jobs-feed-mcp)

Live jobs from company Greenhouse, Lever and Ashby boards with age, long-open and repost signals.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- npm · `@fairquery/company-jobs-feed-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-getfairquery-company-jobs-feed-mcp/fairquery-company-jobs-feed-mcp.md), [page](https://verifymcp.io/servers/com-getfairquery-company-jobs-feed-mcp/fairquery-company-jobs-feed-mcp)

## Channel facts

- Registry: `npm`
- Package: `@fairquery/company-jobs-feed-mcp`
- Version: `1.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3719 tokens (~743/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Fairquery Company Jobs Feed MCP server?

Fairquery Company Jobs Feed runs locally as an npm package, launched with npx -y @fairquery/company-jobs-feed-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-getfairquery-company-jobs-feed-mcp -- npx -y @fairquery/company-jobs-feed-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-getfairquery-company-jobs-feed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fairquery/company-jobs-feed-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getfairquery-company-jobs-feed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fairquery/company-jobs-feed-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-getfairquery-company-jobs-feed-mcp -- npx -y @fairquery/company-jobs-feed-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getfairquery-company-jobs-feed-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@fairquery/company-jobs-feed-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getfairquery-company-jobs-feed-mcp --command npx --arg -y --arg @fairquery/company-jobs-feed-mcp
```

### Hermes

```yaml
mcp_servers:
  com-getfairquery-company-jobs-feed-mcp:
    command: "npx"
    args: ["-y", "@fairquery/company-jobs-feed-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-getfairquery-company-jobs-feed-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@fairquery/company-jobs-feed-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getfairquery-company-jobs-feed-mcp -t stdio -c npx -a -y @fairquery/company-jobs-feed-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-getfairquery-company-jobs-feed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fairquery/company-jobs-feed-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-20 (score 48, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.1.3 → 1.1.4

### 2026-10-19 (score 62)

First indexed and scored.

## MCP tools (5)

### `jobs_get_board` (~847 tokens)

Get live jobs from one ATS board (free)

WHAT: Fetch every job currently published on ONE company board from its official public ATS API (Greenhouse, Lever or Ashby), normalize it and filter it locally.
WHEN: You know the board (ats + slug), e.g. from jobs_find_board or a careers-page link, and want its live openings now.
WHEN NOT: Many companies at once, history (new/closed/reposted since last run), or careers-page discovery at scale: use jobs_search_companies (paid). Unknown board: use jobs_find_board first. SmartRecruiters, LinkedIn, Workday, Workable and Recruitee are not supported and never contacted.
BEHAVIOR: Runs on your machine; one GET to the documented API host only (very large Greenhouse boards: a second, lighter GET). Nothing stored, no history: first_seen_at = now and change = null. Any HTTP 403/429 stops that host for the session (kill switch, HOST_BLOCKED error). Lever requests are spaced 1 s apart (its robots.txt Crawl-delay).
COST: No APIFY_TOKEN, no billing.
RETURNS: Paged "job" rows. compensation only when the ATS publishes it; posted_at is the ATS date or null (never guessed); age_basis says how age_days was derived.
PARAMETERS: All filters are AND-ed; values inside one filter are OR-ed. titleIncludes/titleExcludes match whole words ("engineer" does not match "Engineering"). countries uses the ATS's structured country where present (Lever, Ashby) and a place-name list otherwise; rows without any country are dropped when countries is set. postedWithinDays drops rows with posted_at = null. Paging re-fetches the board, so pages from different calls can shift if the employer edits the board in between.
EXAMPLE: {"ats":"ashby","slug":"ramp","titleIncludes":["engineer"],"remote":"only"} -> remote engineering roles at Ramp with salary ranges.

Input parameters:

- `ats` (string, required): Required. The applicant-tracking system hosting the board: "greenhouse" | "lever" | "ashby". Example: "ashby"
- `countries` (array): Optional ISO-3166 alpha-2 codes, any-of, case-insensitive. Example: ["US","DE"]
- `includeDescription` (boolean): Optional boolean, default false. true adds description_text (plain text, <= 20,000 chars, e-mails/phones removed)
- `limit` (integer): Optional page size, integer 1-500, default 50
- `locations` (array): Optional, 0-50 strings, any-of. Substring match on location text; "remote" also matches ATS remote flags. Example: ["new york","berlin"]
- `longOpenDays` (integer): Optional integer, default 60: rows older than this get long_open = true (a heuristic, not proof of a ghost job)
- `offset` (integer): Optional items to skip, integer >= 0, default 0; pass nextOffset from the previous response
- `postedWithinDays` (integer): Optional integer 1-3650: keep jobs whose ATS publish date is at most this many days old. Example: 14
- `remote` (string): Optional, "any" | "only" | "exclude", default "any"
- `slug` (string, required): Required. Board slug as it appears in the public board URL (case-insensitive): boards.greenhouse.io/{slug}, jobs.lever.co/{slug}, jobs.ashbyhq.com/{slug}; 1-100 chars: a letter or digit, then letters…
- `titleExcludes` (array): Optional, 0-50 strings, any-of. Drop titles containing any of these. Example: ["intern","manager"]
- `titleIncludes` (array): Optional, 0-50 strings, any-of. Keep titles containing any of these whole words/phrases, case-insensitive. Example: ["engineer","data scientist"]

Output parameters:

- `count` (integer): Number of items in this page
- `hasMore` (boolean): True if more items exist after this page
- `items` (array): Result rows. Each has "type": "job" (job_key, title, company, locations, countries, remote, posted_at, verified_open_at, age_days, long_open, apply_url, source_url, ...), "board", "company", "seed_bo…
- `meta` (object): Tool-specific context: board totals, request counts, cost notes
- `nextOffset`: Offset to pass for the next page, or null when done
- `offset` (integer): Offset of the first item in this page
- `total` (integer): Total items after filters, before paging

### `jobs_find_board` (~651 tokens)

Find which ATS board a company uses (free)

WHAT: Resolve a company name, domain or careers/board URL to its public job board(s) on Greenhouse, Lever or Ashby.
WHEN: Before jobs_get_board when you only know the company ("Ramp", "sentry.io", "https://stripe.com/jobs").
WHEN NOT: You already have ats + slug (call jobs_get_board). For many companies plus their jobs in one step use jobs_search_companies (paid). It cannot find Workday, Workable, Recruitee or LinkedIn pages.
BEHAVIOR: Runs on your machine. Order: board-URL parsing -> verified starter list -> the company's own website (only for a domain/URL input; robots.txt respected, <= 3 pages, private/internal IPs refused) -> at most 6 GETs against the documented ATS APIs with slug guesses. Stops at the first hit. Nothing is cached or stored. Rate limits: max 2 parallel requests per host, Lever spaced 1 s apart, 15 s timeout per GET; ATS API network errors and HTTP 5xx are retried at most twice with backoff (0.5-1.6 s). Any HTTP 403/429 (or an HTML block page from an ATS API) stops that host for the session (kill switch, never retried, also for the other free tools): the call does not fail but adds a HOST_BLOCKED note to meta.notes, stops the careers-page step when the company site is blocked, and skips later slug probes on a stopped ATS host without sending them.
COST: No APIFY_TOKEN and no billing; worst case about 4 website requests (robots.txt + 3 pages) and 6 ATS API GETs per call.
RETURNS: "board" rows, or one NO_BOARD_FOUND error row. via (board_url | seed_list | careers_page | slug_probe) says how the board was found; confidence is "high" except for slug_probe hits ("medium": the slug exists but may belong to a different company with the same name, so check the jobs or pass the URL from the careers page).
PARAMETERS: company accepts three forms with different behavior: a board URL is parsed with no network call; a domain or https URL enables the careers-page step; a plain name only uses the starter list and slug probes. Slug guesses for a name drop lega…

Input parameters:

- `company` (string, required): Required. Company name, domain or URL, 2-300 chars. Examples: "Ramp", "sentry.io", "https://jobs.lever.co/palantir"

Output parameters:

- `count` (integer): Number of items in this page
- `hasMore` (boolean): True if more items exist after this page
- `items` (array): Result rows. Each has "type": "job" (job_key, title, company, locations, countries, remote, posted_at, verified_open_at, age_days, long_open, apply_url, source_url, ...), "board", "company", "seed_bo…
- `meta` (object): Tool-specific context: board totals, request counts, cost notes
- `nextOffset`: Offset to pass for the next page, or null when done
- `offset` (integer): Offset of the first item in this page
- `total` (integer): Total items after filters, before paging

### `jobs_check_open` (~743 tokens)

Re-check whether one job is still published (free)

WHAT: Re-check ONE job on the employer's ATS right now and report open or closed; optionally return that job's full row with its description.
WHEN: Before applying, alerting or contacting about a specific job you got earlier (job_key or ats + slug + jobId), or to read one job's full details (includeDescription=true).
WHEN NOT: Listing jobs (jobs_get_board) or checking many jobs at once (jobs_search_companies with confirmOpen, paid).
BEHAVIOR: Greenhouse, Lever: one GET to the documented per-job endpoint; HTTP 404 = closed. Ashby has no per-job endpoint, so the whole board is fetched once and searched for the id (method "board_listing"). "open" means currently published by the employer; it does not prove the role is still being filled.
COST: No APIFY_TOKEN, no billing.
RETURNS: One "open_check" row (job = the full "job" row when includeDescription=true and the job is open, else null), or a tool error: INVALID_INPUT, BOARD_NOT_FOUND, HOST_BLOCKED or NETWORK_ERROR (the last two retryable).
PARAMETERS: A malformed jobKey, or neither jobKey nor a complete ats + slug + jobId, returns INVALID_INPUT without a request. An Ashby id costs one full board download (the same request as jobs_get_board); on Greenhouse and Lever a 404 triggers one extra board request so a closed job (status closed) is told apart from a missing board (BOARD_NOT_FOUND). includeDescription adds no request on Greenhouse and Lever (the per-job response already holds the text) and makes the Ashby board download include descriptions; description_text is plain text, <= 20,000 chars, e-mails/phones removed, exactly as in jobs_get_board.
EXAMPLE: {"jobKey":"greenhouse:stripe:8172503"} -> {"status":"open","method":"detail_endpoint"}.

Input parameters:

- `ats` (string): Required unless jobKey is given. The applicant-tracking system hosting the board: "greenhouse" | "lever" | "ashby" (the first part of job_key). Example: "greenhouse"
- `includeDescription` (boolean): Optional boolean, default false. true adds job: the full job row (title, location, compensation, posted_at, description_text, ...) when the job is open. Example: true
- `jobId` (string): Required unless jobKey is given. The ATS job id (job_id field, the last part of job_key), 1-100 chars: numeric on Greenhouse, a UUID on Lever and Ashby. Example: "8172503"
- `jobKey` (string): Optional if ats + slug + jobId are given; wins when both are given. The job_key field of a job row, format "{ats}:{slug}:{job_id}" with ats in lowercase (greenhouse | lever | ashby); any other shape…
- `slug` (string): Required unless jobKey is given. Board slug from the public board URL (boards.greenhouse.io/{slug}, jobs.lever.co/{slug}, jobs.ashbyhq.com/{slug}; the middle part of job_key), case-insensitive, 1-100…

Output parameters:

- `count` (integer): Number of items in this page
- `hasMore` (boolean): True if more items exist after this page
- `items` (array): Result rows. Each has "type": "job" (job_key, title, company, locations, countries, remote, posted_at, verified_open_at, age_days, long_open, apply_url, source_url, ...), "board", "company", "seed_bo…
- `meta` (object): Tool-specific context: board totals, request counts, cost notes
- `nextOffset`: Offset to pass for the next page, or null when done
- `offset` (integer): Offset of the first item in this page
- `total` (integer): Total items after filters, before paging

### `jobs_list_seed_boards` (~317 tokens)

List the verified starter boards (free, offline)

WHAT: List the bundled starter list of company job boards that Fairquery verified on their official ATS APIs (company, domain, ats, slug, verified_at, jobs_at_verification).
WHEN: To pick companies to scan, or to know which names jobs_find_board resolves instantly.
WHEN NOT: Live job data (jobs_get_board) or companies not in the list (jobs_find_board). The list is a starting point, not a global index of employers.
BEHAVIOR: Offline: reads a static list compiled into the server; no network call. jobs_at_verification is a snapshot from verified_at and goes stale.
COST: No APIFY_TOKEN, no billing.
RETURNS: Paged "seed_board" rows in the fixed bundled order (grouped by ATS, so offsets are stable).
PARAMETERS: ats narrows the list; omit it for all three systems. meta.by_ats always counts the whole list per ATS and ignores ats, so take paging totals from total. Feed ats + slug of any item straight into jobs_get_board.
EXAMPLE: {"ats":"lever"} -> Palantir, Spotify, Zoox, Ro.

Input parameters:

- `ats` (string): Optional filter: "greenhouse" | "lever" | "ashby"; default all
- `limit` (integer): Optional page size, integer 1-500, default 100
- `offset` (integer): Optional items to skip, integer >= 0, default 0; pass nextOffset from the previous response

Output parameters:

- `count` (integer): Number of items in this page
- `hasMore` (boolean): True if more items exist after this page
- `items` (array): Result rows. Each has "type": "job" (job_key, title, company, locations, countries, remote, posted_at, verified_open_at, age_days, long_open, apply_url, source_url, ...), "board", "company", "seed_bo…
- `meta` (object): Tool-specific context: board totals, request counts, cost notes
- `nextOffset`: Offset to pass for the next page, or null when done
- `offset` (integer): Offset of the first item in this page
- `total` (integer): Total items after filters, before paging

### `jobs_search_companies` (~1161 tokens)

Search and monitor jobs across many companies (paid Apify Actor)

WHAT: Run the Fairquery Apify Actor fairquery/company-jobs-feed over many companies or boards: board discovery, search filters, per-board history (first_seen/last_seen, new/updated/closed, repost detection), optional per-job re-checks and descriptions.
WHEN: Monitoring a company list ("what is new since yesterday?"), searching the verified starter list, or anything that needs history, closed/repost signals or more than a few boards.
WHEN NOT: One board right now (jobs_get_board, free) or one job (jobs_check_open, free).
BEHAVIOR: Read-only on job sites; requires APIFY_TOKEN and runs in YOUR Apify account (waits up to 300 s; history is kept in a named key-value store there). Same politeness rules as the free tools: documented ATS APIs only, 403/429 kill switch, robots.txt on careers pages.
COST: Paid, pay-per-event, billed to your Apify account: $0.00099 per job row, $0.0005 per board scanned, $0.00029 per re-check (confirmOpen), $0.0019 per company found by discovery; no start fee. Error, closed and merged rows are free. Example: 3 boards, 300 jobs = about $0.30.
RETURNS: Paged dataset rows: "job" rows (as jobs_get_board plus first_seen_at, last_seen_at, change, reposted, repost_of, stale_signal, duplicate_of), one "board" row per board (jobs_total, new, updated, closed), "company" rows for discovery, "error" rows (code, message, retryable).
PARAMETERS: companies, boards and useSeedList: at least one is required although the schema marks all optional (none -> INPUT_EMPTY, not billed). onlyNew implies history and compares with the last run that used the same stateStoreName, so use one name per saved search; the first run returns everything as new. limit/offset page the returned rows locally; every call starts a new billed run, so fetch the pages you need from one result instead of re-calling.
EXAMPLE: {"companies":["stripe.com","ramp.com"],"titleIncludes":["engineer"],"countries":["US"],"onlyNew":true}.

Input parameters:

- `boards` (array): Optional. 0-500 exact boards. Example: [{"ats":"lever","slug":"palantir"}]
- `companies` (array): Optional (see PARAMETERS). 0-200 names, domains or board URLs. Example: ["stripe.com","Ramp","https://jobs.lever.co/palantir"]
- `confirmOpen` (boolean): Optional boolean, default false: re-check each emitted job on its detail endpoint ($0.00029 each, max 200 per run)
- `countries` (array): Optional ISO-2 codes, any-of. Example: ["US","GB"]
- `departments` (array): Optional, 0-50 strings, any-of. Department/team substring match. Example: ["engineering"]
- `excludeStale` (boolean): Optional boolean, default false. true drops job rows with long_open = true (age_days > 60, counted from posted_at, or from first_seen_at when the ATS gives no date) or reposted = true (a new job id m…
- `includeDescription` (boolean): Optional boolean, default false: add plain-text descriptions (PII-scrubbed)
- `limit` (integer): Optional page size, integer 1-500, default 50
- `locations` (array): Optional, 0-50 strings, any-of. Location substring match. Example: ["london"]
- `maxJobs` (integer): Optional integer 1-50000, default 5000: spend cap on billed job rows
- `offset` (integer): Optional items to skip, integer >= 0, default 0; pass nextOffset from the previous response
- `onlyNew` (boolean): Optional boolean, default false: only new/changed jobs since the last tracked run (plus free closed rows)
- `postedWithinDays` (integer): Optional integer 1-3650, default off: keep only job rows whose ATS publish date (posted_at) is at most this many whole days old; rows without an ATS publish date (posted_at = null) are dropped. Free…
- `remote` (string): Optional, "any" | "only" | "exclude", default "any" (no remote filter). "only" keeps job rows with remote = true (an ATS remote flag, or remote wording such as "Remote" or "Anywhere" in the location…
- `stateStoreName` (string): Optional, default "fairquery-jobs-feed-state": named key-value store for history in your Apify account
- `titleExcludes` (array): Optional, 0-50 strings, any-of. Whole-word title exclusion. Example: ["intern"]
- `titleIncludes` (array): Optional, 0-50 strings, any-of. Whole-word title match. Example: ["engineer"]
- `useSeedList` (boolean): Optional boolean, default false: also scan all verified starter boards (each billed as a board)

Output parameters:

- `count` (integer): Number of items in this page
- `hasMore` (boolean): True if more items exist after this page
- `items` (array): Result rows. Each has "type": "job" (job_key, title, company, locations, countries, remote, posted_at, verified_open_at, age_days, long_open, apply_url, source_url, ...), "board", "company", "seed_bo…
- `meta` (object): Tool-specific context: board totals, request counts, cost notes
- `nextOffset`: Offset to pass for the next page, or null when done
- `offset` (integer): Offset of the first item in this page
- `total` (integer): Total items after filters, before paging

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-getfairquery-company-jobs-feed-mcp/fairquery-company-jobs-feed-mcp#diagnostics

## Score history

- 2026-10-22: 64
- 2026-10-21: 63
- 2026-10-20: 48
- 2026-10-19: 62

## Common questions

### What is the Fairquery Company Jobs Feed MCP server?

Fairquery Company Jobs Feed is an MCP server listed in the public MCP registry as com.getfairquery/company-jobs-feed-mcp. Live jobs from company Greenhouse, Lever and Ashby boards with age, long-open and repost signals. This page covers its npm package (@fairquery/company-jobs-feed-mcp).

### Is the Fairquery Company Jobs Feed MCP server safe to use?

Fairquery Company Jobs Feed scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Fairquery Company Jobs Feed MCP server expose?

Fairquery Company Jobs Feed exposes 5 tools: jobs_get_board, jobs_find_board, jobs_check_open, jobs_list_seed_boards, jobs_search_companies. Their descriptions and schemas cost roughly 3,719 tokens of context every time the server is loaded.

### Is the Fairquery Company Jobs Feed MCP server still maintained?

Fairquery Company Jobs Feed is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Fairquery Company Jobs Feed MCP server under?

Fairquery Company Jobs Feed declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@fairquery/company-jobs-feed-mcp
- Socket report: https://socket.dev/npm/package/@fairquery/company-jobs-feed-mcp
- Website: https://getfairquery.com/posts/live-job-listings-api-greenhouse-lever-ashby/
- Changelog RSS feed: https://verifymcp.io/servers/com-getfairquery-company-jobs-feed-mcp/fairquery-company-jobs-feed-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getfairquery-company-jobs-feed-mcp/fairquery-company-jobs-feed-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-getfairquery-company-jobs-feed-mcp/fairquery-company-jobs-feed-mcp