VeritaHire Hiring Intelligence
For employers: how a job posting compares with the market nearby, by competitor; hiring reports.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'request_competitive_hiring_report' name length outside 3-30 rangein request_competitive_hiring_report
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"hiring-intelligence": {
"url": "https://veritahire.com/mcp/employers"
}
}
}Remote endpoints
https://veritahire.com/mcp/employersstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢compare_job_posting(job_url, job_id, employer, title, city, ...)
For the employer of one open US healthcare, finance, IT, engineering, science, HR, legal or marketing 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 retry_after_seconds.
Input Schema
{
"type": "object",
"properties": {
"job_url": {
"type": "string",
"description": "The posting's URL on the employer's careers site, or a veritahire.com/j/ URL"
},
"job_id": {
"type": "integer",
"description": "VeritaHire job id"
},
"employer": {
"type": "string"
},
"title": {
"type": "string"
},
"city": {
"type": "string"
},
"state": {
"type": "string",
"description": "Two-letter US state"
}
}
}🟢hiring_market(occupation, state)
The current US hiring market for one healthcare, finance, IT, engineering, science, HR, legal or marketing 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"); 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 Schema
{
"type": "object",
"properties": {
"occupation": {
"type": "string",
"description": "A healthcare, finance, IT, engineering, science, HR, legal or marketing occupation in plain words"
},
"state": {
"type": "string",
"description": "Two-letter US state, a state name, or US (the default)"
}
},
"required": [
"occupation"
]
}🟡request_competitive_hiring_report(email, job_url, job_id, employer, title, ...)
Emails one link to the work address given. The click creates a free VeritaHire account and opens the full Competitive Hiring Report for 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. Nothing more is sent unless the link is clicked. 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 Schema
{
"type": "object",
"properties": {
"email": {
"type": "string",
"description": "The hiring manager's work email address"
},
"job_url": {
"type": "string"
},
"job_id": {
"type": "integer"
},
"employer": {
"type": "string"
},
"title": {
"type": "string"
},
"city": {
"type": "string"
},
"state": {
"type": "string"
},
"location": {
"type": "string",
"description": "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": {
"type": "string",
"description": "For a role being planned: the pay being considered, yearly or hourly (\"95000\", \"$45 an hour\")"
}
},
"required": [
"email"
]
}🟢is_job_still_open(url, job_id)
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 Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The posting URL (careers site or veritahire.com/j/)"
},
"job_id": {
"type": "integer"
}
}
}Community
Evidence