_ registry / mcp streamable-http · checked 1h ago

veritahire

https://veritahire.com

Registry code: 9648b2f3853b59b6

api record

VeritaHire reads US jobs directly from employers' own careers sites: live job search with posted pay and apply links, full postings, whether a posting is still open, daily job alerts by email, problem reports, and a free Competitive Hiring Report for one healthcare, finance, IT, engineering, science, HR, legal, marketing, sales, customer service, admin, operations and logistics, skilled trades, retail and food, or education role: how fast competitors nearby close the same role, what each pays, who else is hiring it, and whether the market is tightening.

endpoint
https://veritahire.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is veritahire live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is veritahire free to use?
Not measured yet.
What tools does veritahire have?
8 tools: save_search, benchmark_role, request_full_report, job_openings_index, is_job_still_open, search_live_jobs, get_job, report_problem.
Is veritahire safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 97.9%· all time 97.9%

latency
472ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 289 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search live us jobs from employer sites
  • check if a job posting is still open
  • benchmark healthcare role pay
  • set up daily job alert emails
takes → gives
text → data
tools
4 reads1 changes data2 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
8 never probed 0 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • save_search sends messages unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "what": {
          "type": "string"
        },
        "where": {
          "type": "string",
          "description": "\"City, ST\", a ZIP, a state (\"VA\"), or \"US\""
        },
        "remote_only": {
          "type": "boolean"
        },
        "radius_miles": {
          "enum": [
            10,
            25,
            30,
            50,
            100
          ],
          "type": "integer"
        },
        "employment_type": {
          "enum": [
            "full_time",
            "part_time",
            "contract",
            "seasonal",
            "temporary"
          ],
          "type": "string"
        }
      }
    }
    arguments 35 lines
  • benchmark_role reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string"
        },
        "state": {
          "type": "string",
          "description": "Two-letter US state"
        },
        "title": {
          "type": "string"
        },
        "job_id": {
          "type": "integer",
          "description": "VeritaHire job id"
        },
        "job_url": {
          "type": "string",
          "description": "The posting's URL on the employer's careers site, or a veritahire.com/j/ URL"
        },
        "employer": {
          "type": "string"
        }
      }
    }
    arguments 26 lines
  • request_full_report sends messages unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string"
        },
        "state": {
          "type": "string"
        },
        "title": {
          "type": "string"
        },
        "job_id": {
          "type": "integer"
        },
        "job_url": {
          "type": "string"
        },
        "employer": {
          "type": "string"
        }
      }
    }
    arguments 23 lines
  • job_openings_index unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "maximum": 120,
          "minimum": 1,
          "description": "How many days of the series to return (default 30)"
        }
      }
    }
    arguments 11 lines
  • is_job_still_open reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "url": {
          "type": "string",
          "description": "The posting URL (careers site or veritahire.com/j/)"
        },
        "job_id": {
          "type": "integer"
        }
      }
    }
    arguments 12 lines
  • search_live_jobs reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "integer",
          "minimum": 1,
          "description": "25 jobs a page; pass next_page from the previous result"
        },
        "sort": {
          "enum": [
            "new",
            "pay",
            "near"
          ],
          "type": "string",
          "description": "Default: best match"
        },
        "what": {
          "type": "string",
          "description": "Job title, keywords or employer, e.g. \"registered nurse\", \"forklift\", \"Kaiser Permanente\""
        },
        "where": {
          "type": "string",
          "description": "\"City, ST\" or a 5-digit ZIP (radius applies); a state, e.g. \"Virginia\" or \"VA\" (the whole state); or \"US\" (nationwide)"
        },
        "min_pay": {
          "type": "number",
          "description": "Minimum pay: annual, or hourly if under 300. Jobs that do not post pay are kept, listed last."
        },
        "remote_only": {
          "type": "boolean"
        },
        "radius_miles": {
          "enum": [
            10,
            25,
            30,
            50,
            100
          ],
          "type": "integer",
          "default": 25
        },
        "title_exclude": {
          "type": "string",
          "description": "Comma-separated words; jobs whose title contains any of them are left out, e.g. \"senior, travel\""
        },
        "employment_type": {
          "enum": [
            "full_time",
            "part_time",
            "contract",
            "seasonal",
            "temporary"
          ],
          "type": "string"
        },
        "posted_within_days": {
          "enum": [
            1,
            3,
            7,
            14,
            30
          ],
          "type": "integer"
        }
      }
    }
    arguments 69 lines
  • get_job reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "url": {
          "type": "string"
        },
        "job_id": {
          "type": "integer",
          "description": "VeritaHire job id, as returned in search results"
        }
      }
    }
    arguments 12 lines
  • report_problem changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "kind"
      ],
      "properties": {
        "kind": {
          "enum": [
            "job_closed",
            "wrong_location",
            "wrong_pay",
            "wrong_employer",
            "irrelevant_results",
            "missing_jobs",
            "duplicate",
            "other"
          ],
          "type": "string"
        },
        "detail": {
          "type": "string",
          "description": "What was wrong, in a sentence or two"
        },
        "job_id": {
          "type": "integer"
        },
        "search": {
          "type": "object",
          "description": "The search arguments that produced the problem"
        }
      }
    }
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9648b2f3853b59b6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9648b2f3853b59b6/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9648b2f3853b59b6/badge.svg)](https://brick.blue/agent/9648b2f3853b59b6?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.