Jobherder job search
REMOTE · JOBHERDER.COM · SCANNED OCT 1
Paid job search: 7 matched roles, each with a tailored CV and cover letter.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 871 tokens (~174/item across 5 items; 5 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Jobherder job search MCP server?
Jobherder job search is a hosted endpoint at https://jobherder.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 · jobherder.com
claude mcp add --transport http com-jobherder-job-search 'https://jobherder.com/mcp'
{
"mcpServers": {
"com-jobherder-job-search": {
"url": "https://jobherder.com/mcp"
}
}
} {
"servers": {
"com-jobherder-job-search": {
"type": "http",
"url": "https://jobherder.com/mcp"
}
}
} [mcp_servers.com-jobherder-job-search] url = "https://jobherder.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-jobherder-job-search": {
"type": "remote",
"url": "https://jobherder.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-jobherder-job-search --url 'https://jobherder.com/mcp' --transport streamable-http
mcp_servers:
com-jobherder-job-search:
url: "https://jobherder.com/mcp" {
"McpServers": {
"com-jobherder-job-search": {
"Transport": "http",
"Url": "https://jobherder.com/mcp"
}
}
} assistant mcp add com-jobherder-job-search -t streamable-http -u 'https://jobherder.com/mcp'
{
"mcpServers": {
"com-jobherder-job-search": {
"type": "http",
"url": "https://jobherder.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 1 Oct 2026 · Probed https://jobherder.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobherder.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a347f85543eebf290ede782595e90a21 |
| SANs: jobherder.com, *.jobherder.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of jobherder.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jobherder.com. | present | 2371 | 13 | Verified |
| jobherder.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobherder.com/mcp | Verified | 200 | |
| http (plaintext) | http://jobherder.com/mcp | HTTPS enforced | 301 | https://jobherder.com/mcp |
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 →
get_pricing Get pricing ~34
What a Jobherder search costs and how to pay for it, in card and stablecoin terms. No auth required.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| card_checkout | string | yes | URL for card payment |
| credits_are_per_product | boolean | yes | Always true: a quick credit cannot pay for a full search |
| free_searches | boolean | yes | Always false: registration grants no credits |
| packs | array | yes | Buyable credit packs |
| products | array | yes | The two things Jobherder sells |
| service | string | yes | Service name |
| x402 | – | yes | Stablecoin payment terms, null if x402 is not configured |
No examples provided.
get_search_status Check a search ~60
Progress of a search, and the matched roles with the reason each was picked once it finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | – | The run_id returned by start_job_search or quick_job_search. Omit to get the most recent run for this account |
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | – | True once the run has finished, whether or not it found anything |
| error | string | – | Present only on failure, e.g. "unauthorized" or "payment_required" |
| finished_at | – | – | – |
| matches | array | – | The delivered roles, each with its tailored documents. Absent until the run succeeds |
| message | string | – | Progress in plain language while running, or what to do about the error |
| plan | string | – | Which product this run was: one_off or agent_quick |
| run_id | string | – | – |
| started_at | – | – | – |
| status | string | – | running, success, no_matches or failed |
| target_jobs | number | – | How many roles this run is meant to deliver |
No examples provided.
quick_job_search Quick job match ~269
The single best current role for a profile, with a tailored CV and cover letter, in minutes rather than an hour. $2.50 in USDC. Use this when you want one answer fast; use start_job_search when you want a shortlist of 7 to choose from. With no credit it returns an x402 PaymentRequired; retry the same call with the signed payment in _meta["x402/payment"].
| Name | Type | Req | Description |
|---|---|---|---|
| cv_base64 | string | – | The job seeker's existing CV as a file, base64 encoded. PDF, DOCX or plain text, up to 10MB. Use cv_json instead if you have the CV as data rather than a file |
| cv_json | object | – | The job seeker's existing CV as structured data, in the JSON Resume schema (jsonresume.org): basics, work, education, skills. Prefer this when you hold the CV as data — you do not need to render a fi… |
| cv_type | string | – | Format of cv_base64: "pdf", "docx" or "txt". Ignored when cv_json is supplied |
| profile | object | yes | Who the job seeker is and what they want. Every field shapes matching, so guessing is worse than asking |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | Credits left for this product after the spend |
| error | string | – | Present only on failure, e.g. "unauthorized" or "payment_required" |
| message | string | – | What happens next and roughly when, or what to do about the error |
| run_id | string | – | Pass this to get_search_status to poll |
| status | string | – | Run state at the moment of starting, normally "running" |
No examples provided.
register_agent Register for an API key ~85
Create an agent identity and receive an API key. Registration is free and includes no free searches.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email that will own the account and receive results. Must be the job seeker's own address, and must match cfg_email on every later search | |
| name | string | – | Display name for the account. Optional; the profile name is used on documents regardless |
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Bearer token for every later call. Shown once and never again |
| string | – | The address the account is registered to | |
| error | string | – | Present only on failure, e.g. "unauthorized" or "payment_required" |
| message | string | – | What to do about the error, when one is present |
| next | string | – | Suggested next call |
| note | string | – | – |
| owner_action_url | string | – | Present only on account_owned_by_human. A person already owns this address, so no key can be issued here. Send them to this page to create one and paste it back |
No examples provided.
start_job_search Start a job search ~263
Spend one credit to run a full search: 7 roles matched to the profile, each with a tailored CV and cover letter returned as markdown by get_search_status and emailed as PDFs. Requires an API key. With no credit left it returns an x402 PaymentRequired; retry the same call with the signed payment in _meta["x402/payment"] to pay in USDC and run immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| cv_base64 | string | – | The job seeker's existing CV as a file, base64 encoded. PDF, DOCX or plain text, up to 10MB. Use cv_json instead if you have the CV as data rather than a file |
| cv_json | object | – | The job seeker's existing CV as structured data, in the JSON Resume schema (jsonresume.org): basics, work, education, skills. Prefer this when you hold the CV as data — you do not need to render a fi… |
| cv_type | string | – | Format of cv_base64: "pdf", "docx" or "txt". Ignored when cv_json is supplied |
| profile | object | yes | Who the job seeker is and what they want. Every field shapes matching, so guessing is worse than asking |
| Name | Type | Req | Description |
|---|---|---|---|
| credits_remaining | number | – | Credits left for this product after the spend |
| error | string | – | Present only on failure, e.g. "unauthorized" or "payment_required" |
| message | string | – | What happens next and roughly when, or what to do about the error |
| run_id | string | – | Pass this to get_search_status to poll |
| status | string | – | Run state at the moment of starting, normally "running" |
No examples provided.
What is the Jobherder job search MCP server?
Jobherder job search is an MCP server listed in the public MCP registry as com.jobherder/job-search. Paid job search: 7 matched roles, each with a tailored CV and cover letter. This page covers its hosted endpoint (https://jobherder.com/mcp).
Is the Jobherder job search MCP server safe to use?
Jobherder job search scores 82 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 Jobherder job search MCP server expose?
Jobherder job search exposes 5 tools: get_pricing, register_agent, start_job_search, quick_job_search, get_search_status. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.
Does the Jobherder job search MCP server require authentication?
No. We connected to Jobherder job search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jobherder job search MCP server still maintained?
Jobherder job search is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.