Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VeritaHire live jobs

REMOTE · VERITAHIRE.COM

Live US jobs from employers' own career sites, still-open checks, competitive hiring reports.

Available components

+2 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1647 tokens (~205/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management81
  • Stability check failed: schema churn in the 29 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “benchmark_role” rewrote its description, which is the text the model reads security
    • Tool “search_live_jobs” rewrote its description, which is the text the model reads security
    • Schema quality: 1310 → 1647 ▼ functional
    • New tool “job_openings_index” functional
    • “save_search” reworded the description of “where” cosmetic
    • “search_live_jobs” reworded the description of “what” cosmetic
    • “search_live_jobs” reworded the description of “where” cosmetic
  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://veritahire.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.veritahire.com CN=YR1,O=Let's Encrypt,C=US 23 Oct 2026 21 Jan 2027 RSA 2048 SHA256-RSA 63cfa2d8cbb08be2819236b6b42022ba97a
SANs: veritahire.com, www.veritahire.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of veritahire.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
veritahire.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'nonce-398lkrydTNaOYMACWnCELQ' https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'nonce-398lkrydTNaOYMACWnCELQ' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https:; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://stats.g.doubleclick.net https://www.googletagmanager.com https://www.google.com; object-src 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; frame-ancestors 'self'; report-uri /csp-report.php
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://veritahire.com/mcp Verified 200
http (plaintext) http://veritahire.com/mcp HTTPS enforced 301 https://veritahire.com/mcp.php
MCP tools · 8 exposed · ~1,529 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
benchmark_role ~357

Competitive Hiring Report, free summary, for the employer of one US healthcare, finance, IT, engineering, science, HR, legal, marketing, sales, customer service, admin, operations and logistics, skilled trades, retail and food, or education job posting (nurses, therapists, pharmacists, accountants, bankers, software engineers, data roles, engineers, scientists, attorneys, recruiters, marketers) that is not filling: the posted pay range in that market (salary benchmarking) and how many employers are hiring it. The full report, first one free (request_full_report), names each competitor with the pay it posts and how fast it closes the role (posting up to posting down), and shows where this posting sits and how hard the role is to fill there. Measured from employers' own careers sites. Identify the posting by job_url (the careers-site link, or a veritahire.com/j/ link), job_id, or employer + title (+ city, state). A role not yet benchmarked returns status "building" with market_now (the role's market within 25 miles, counted that moment) and retry_after_seconds, the time until the full summary is ready. A posting we do not hold, named by title and city/state, returns status "not_held" with market_now and a link for a report on the role as planned.

NameTypeReqDescription
citystring––
employerstring––
job_idinteger–VeritaHire job id
job_urlstring–The posting's URL on the employer's careers site, or a veritahire.com/j/ URL
statestring–Two-letter US state
titlestring––

No output schema declared.

No examples provided.

get_job ~87

The whole posting text from the employer, its requirement facts (education, licences, years required and preferred, skills), pay, any sign-on bonus it offers (the amount, quoted from the posting), benefits, whether it is still open, and the apply link.

NameTypeReqDescription
job_idinteger–VeritaHire job id, as returned in search results
urlstring––

No output schema declared.

No examples provided.

is_job_still_open ~106

Checks 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). Returns open, closed or unknown, with the last time it was confirmed. Works for postings found anywhere, given the employer's careers-site link.

NameTypeReqDescription
job_idinteger––
urlstring–The posting URL (careers site or veritahire.com/j/)

No output schema declared.

No examples provided.

job_openings_index ~121

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).

NameTypeReqDescription
daysinteger–How many days of the series to return (default 30)

No output schema declared.

No examples provided.

report_problem ~140

Records a problem with VeritaHire data: a job listed as open that the employer's site shows closed (job_closed), wrong place, wrong pay, wrong employer name, a search that returned irrelevant results or missed jobs it should have found, or duplicates. job_id identifies one job; search holds the search arguments for a results problem. Reports are about data, not people, and a person at VeritaHire reads every one.

NameTypeReqDescription
detailstring–What was wrong, in a sentence or two
job_idinteger––
kindstringyes–
searchobject–The search arguments that produced the problem

No output schema declared.

No examples provided.

request_full_report ~125

Returns a link for the person who will use the full Competitive Hiring Report for a posting (first report free). They open it on veritahire.com with the posting already filled in, enter their own work email, and get the report. This tool sends no email and takes no email address: VeritaHire only emails the address the person types there.

NameTypeReqDescription
citystring––
employerstring––
job_idinteger––
job_urlstring––
statestring––
titlestring––

No output schema declared.

No examples provided.

save_search ~134

Returns a link for the person. They open it on veritahire.com, enter their own email address and confirm; after that they get a daily email of new jobs matching this search (still live on employers' own careers sites). This tool sends no email and takes no email address: VeritaHire only emails the address the person types there.

NameTypeReqDescription
employment_typestring––
radius_milesinteger––
remote_onlyboolean––
whatstring––
wherestring–"City, ST", a ZIP, a state ("VA"), or "US"

No output schema declared.

No examples provided.

search_live_jobs ~459

Search US jobs that are live right now on employers' own careers sites (re-read on a schedule, retired within about 36 hours of leaving). Give what (title, keywords or an employer name) and where: "City, ST" or a ZIP (with radius_miles), a state ("Virginia" or "VA": the whole state plus remote jobs open to anyone in the US), or "US" for the whole country; or remote_only. Results lead with jobs whose title holds the words given, newest first; one requisition listed in several places comes back once, with also_listed_in. Returns up to 25 jobs with posted pay, what each posting asks for (education, licences, years), distance, when it was last confirmed, the employer's industry and size, the employer's own apply link, and a job_id for the whole posting. Only the filters given are applied; the "asks" are listed, never used to drop a job. To keep a daily feed for one person (e.g. from their resume), run the same search each day with posted_within_days=1, title_exclude for titles they do not want, and page through next_page.

NameTypeReqDescription
employment_typestring––
min_paynumber–Minimum pay: annual, or hourly if under 300. Jobs that do not post pay are kept, listed last.
pageinteger–25 jobs a page; pass next_page from the previous result
posted_within_daysinteger––
radius_milesinteger––
remote_onlyboolean––
sortstring–Default: best match
title_excludestring–Comma-separated words; jobs whose title contains any of them are left out, e.g. "senior, travel"
whatstring–Job title, keywords or employer, e.g. "registered nurse", "forklift", "Kaiser Permanente"
wherestring–"City, ST" or a 5-digit ZIP (radius applies); a state, e.g. "Virginia" or "VA" (the whole state); or "US" (nationwide)

No output schema declared.

No examples provided.

Install

How do I install the VeritaHire live jobs MCP server?

VeritaHire live jobs is a hosted endpoint at https://veritahire.com/mcp, 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.

remote · veritahire.com

# add to Claude Code
claude mcp add --transport http com-veritahire-jobs 'https://veritahire.com/mcp'
Common questions

What is the VeritaHire live jobs MCP server?

VeritaHire live jobs is an MCP server listed in the public MCP registry as com.veritahire/jobs. Live US jobs from employers' own career sites, still-open checks, competitive hiring reports. This page covers its hosted endpoint (https://veritahire.com/mcp).

Is the VeritaHire live jobs MCP server safe to use?

VeritaHire live jobs scores 80 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 live jobs MCP server expose?

VeritaHire live jobs exposes 8 tools: search_live_jobs, get_job, save_search, report_problem, benchmark_role, and 3 more. Their descriptions and schemas cost roughly 1,529 tokens of context every time the server is loaded.

Does the VeritaHire live jobs MCP server require authentication?

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

Is the VeritaHire live jobs MCP server still maintained?

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