# VeritaHire Hiring Intelligence (remote · veritahire.com)

For employers: how a job posting compares with the market nearby, by competitor; hiring reports.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `veritahire.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-veritahire-hiring-intelligence/mcp-employers.md), [page](https://verifymcp.io/servers/com-veritahire-hiring-intelligence/mcp-employers)

## Channel facts

- Endpoint: `https://veritahire.com/mcp/employers`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1552 tokens (~258/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 84/100
  - Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 2 additions.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 55% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 VeritaHire Hiring Intelligence MCP server?

VeritaHire Hiring Intelligence is a hosted endpoint at https://veritahire.com/mcp/employers, so there is nothing to install locally. 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 --transport http com-veritahire-hiring-intelligence 'https://veritahire.com/mcp/employers'
```

### Cursor

```json
{
  "mcpServers": {
    "com-veritahire-hiring-intelligence": {
      "url": "https://veritahire.com/mcp/employers"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-veritahire-hiring-intelligence": {
      "type": "http",
      "url": "https://veritahire.com/mcp/employers"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-veritahire-hiring-intelligence]
url = "https://veritahire.com/mcp/employers"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-veritahire-hiring-intelligence": {
      "type": "remote",
      "url": "https://veritahire.com/mcp/employers",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-veritahire-hiring-intelligence --url 'https://veritahire.com/mcp/employers' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-veritahire-hiring-intelligence:
    url: "https://veritahire.com/mcp/employers"
```

### Netclaw

```json
{
  "McpServers": {
    "com-veritahire-hiring-intelligence": {
      "Transport": "http",
      "Url": "https://veritahire.com/mcp/employers"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-veritahire-hiring-intelligence -t streamable-http -u 'https://veritahire.com/mcp/employers'
```

### Other

```json
{
  "mcpServers": {
    "com-veritahire-hiring-intelligence": {
      "type": "http",
      "url": "https://veritahire.com/mcp/employers"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 81 to 84.

### 2026-11-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 74 to 78.

### 2026-10-31 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 64 to 68.

### 2026-10-29 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 58 to 61.

### 2026-10-28 (score 77, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “compare_job_posting” rewrote its description, which is the text the model reads
- [security] Tool “hiring_market” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 992 → 1552
- [functional improvement] Tool coverage: 44% → 55%
- [functional] New tool “hiring_signals”
- [functional] New tool “job_openings_index”
- [cosmetic] “hiring_market” reworded the description of “occupation”

### 2026-10-26 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 48 to 51.

### 2026-10-24 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.

### 2026-10-21 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 31 to 34.

## MCP tools (6)

### `compare_job_posting` (~351 tokens)

How one job posting compares with the market

For the employer of one open US healthcare, finance, IT, engineering, science, HR, legal, marketing, sales, customer service, admin, operations and logistics, skilled trades, retail and food, or education posting (nurses, therapists, pharmacists, accountants, financial analysts, bankers, software engineers, data and security roles, engineers, scientists, attorneys, paralegals, recruiters, HR and marketing roles): free, the posted pay range for the role within 25 miles and how many employers are hiring it, competitors counted, not named. How fast roles like it close, where this posting's pay and time open sit against each competitor by name, how hard the role is to fill there and what reaching more applicants costs are in the Competitive Hiring Report (request_competitive_hiring_report; first report free). Identify the posting by its careers-site URL, a VeritaHire job id, or employer and title (and city, state). A posting not yet analysed returns status "building" with market_now (the role's market within 25 miles, counted that moment) and retry_after_seconds for the full summary. A posting we do not hold, named by title and city/state, returns status "not_held" with the same market_now and a link for a report on the role as planned.

Input parameters:

- `city` (string)
- `employer` (string)
- `job_id` (integer): VeritaHire job id
- `job_url` (string): The posting's URL on the employer's careers site, or a veritahire.com/j/ URL
- `state` (string): Two-letter US state
- `title` (string)

### `hiring_market` (~253 tokens)

Hiring market for an occupation

The current US hiring market for one healthcare, finance, IT, engineering, science, HR, legal, marketing, sales, customer service, admin, operations and logistics, skilled trades, retail and food, or education occupation, nationally or in one state: live postings, employers hiring, the posted pay range and employment type. Read from employers' own careers sites and rebuilt daily. Occupation in plain words (e.g. "registered nurse", "accountant", "software engineer", "truck driver", "warehouse", "cashier", "electrician", "teacher", "customer service"); state as a code or name, or US. Free; no employer is named. How fast employers close the role, what each requires, and one posting against every employer hiring it by name are in the Competitive Hiring Report (request_competitive_hiring_report; first report free).

Input parameters:

- `occupation` (string, required): A healthcare, finance, IT, engineering, science, HR, legal, marketing, sales, customer service, admin, operations and logistics, skilled trades, retail and food, or education occupation in plain words
- `state` (string): Two-letter US state, a state name, or US (the default)

### `request_competitive_hiring_report` (~300 tokens)

Get a link to the full Competitive Hiring Report

Returns a link for the hiring manager. They open it on veritahire.com with the posting already filled in, enter their own work email, and get the full Competitive Hiring Report (this tool sends no email and takes no email address; VeritaHire only emails the address they type there). The report covers that posting: every employer hiring the same role within 25 miles by name, with the pay each posts and how fast each closes it, the last roles like it to close nearby, competitors' pay changes, and what reaching more applicants would cost. The first report is free. For a role the employer is PLANNING to post (no posting yet, or one we do not hold): give title + location (+ the pay being considered) instead of a posting, and the report is built from the market around that place.

Input parameters:

- `city` (string)
- `employer` (string)
- `job_id` (integer)
- `job_url` (string)
- `location` (string): For a role being planned: a US city and state ("Stockton, CA") or a ZIP code. With title and no job_url/job_id, the report is for a planned role.
- `pay` (string): For a role being planned: the pay being considered, yearly or hourly ("95000", "$45 an hour")
- `state` (string)
- `title` (string)

### `hiring_signals` (~249 tokens)

Roles that are not filling, and employers reposting

Hiring Signals for a recruiter or staffing firm, read from employers' own careers sites: how many live roles have been open at least 3x longer than that same employer usually takes to close a role (stuck), how many roles employers took down and put back up in the last 30 days (reposts), with named examples (stated pay, top of $60K or more), nationally or for one state and one industry. Free counts and examples; the full row-level list is the Hiring Signals API, returned ready to call with the same filters.

Input parameters:

- `industry` (string): healthcare_clinical, software, engineering_hardware, finance_accounting, sales, skilled_trade, operations, admin_support, customer_service, retail_food, education, marketing, legal, data_or_analytics…
- `min_pay` (number): Only roles whose stated pay tops out at least this (annual, or hourly if under 300); roles with no stated pay are kept
- `state` (string): Two-letter US state, a state name, or US (the default)

### `job_openings_index` (~121 tokens)

Job Openings Index (open US job postings, daily)

The VeritaHire Job Openings Index: open US job postings measured every day from employers' own careers sites and published the next morning - the index (base 100), its 7-day average, its change over a day, a week and 28 days, the share of postings put up and taken down in the last week, the latest official JOLTS month for comparison, and the daily series. Free (CC BY 4.0).

Input parameters:

- `days` (integer): How many days of the series to return (default 30)

### `is_job_still_open` (~103 tokens)

Is this job posting still open?

Whether a job posting is still on the employer's own careers site (VeritaHire re-reads employer sites and marks a posting closed within about 36 hours of it leaving): open, closed or unknown, with the last time it was confirmed. Works for any employer's posting, given its careers-site link.

Input parameters:

- `job_id` (integer)
- `url` (string): The posting URL (careers site or veritahire.com/j/)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-veritahire-hiring-intelligence/mcp-employers#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 70
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-10: 71
- 2026-10-08: 70

## Common questions

### What is the VeritaHire Hiring Intelligence MCP server?

VeritaHire Hiring Intelligence is an MCP server listed in the public MCP registry as com.veritahire/hiring-intelligence. For employers: how a job posting compares with the market nearby, by competitor; hiring reports. This page covers its hosted endpoint (https://veritahire.com/mcp/employers).

### Is the VeritaHire Hiring Intelligence MCP server safe to use?

VeritaHire Hiring Intelligence scores 81 out of 100 on VerifyMCP. 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 VeritaHire Hiring Intelligence MCP server expose?

VeritaHire Hiring Intelligence exposes 6 tools: compare_job_posting, hiring_market, request_competitive_hiring_report, hiring_signals, job_openings_index, is_job_still_open. Their descriptions and schemas cost roughly 1,377 tokens of context every time the server is loaded.

### Does the VeritaHire Hiring Intelligence MCP server require authentication?

No. We connected to VeritaHire Hiring Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VeritaHire Hiring Intelligence MCP server still maintained?

VeritaHire Hiring Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://veritahire.com/mcp/employers
- Website: https://veritahire.com/for-ai/
- Changelog RSS feed: https://verifymcp.io/servers/com-veritahire-hiring-intelligence/mcp-employers.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-veritahire-hiring-intelligence/mcp-employers.json
- HTML version of this page: https://verifymcp.io/servers/com-veritahire-hiring-intelligence/mcp-employers