Jobero job search
REMOTE · JOBERO.AI · SCANNED AUG 3
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 →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 869 tokens (~173/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 Management10
- Stability observed for 3 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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · jobero.ai
claude mcp add --transport http ai-jobero-job-search https://jobero.ai/mcp
[mcp_servers.ai-jobero-job-search] url = "https://jobero.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-jobero-job-search": {
"type": "remote",
"url": "https://jobero.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-jobero-job-search --url https://jobero.ai/mcp --transport streamable-http
mcp_servers:
ai-jobero-job-search:
url: "https://jobero.ai/mcp" {
"mcpServers": {
"ai-jobero-job-search": {
"type": "http",
"url": "https://jobero.ai/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Tool “start_job_search” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 67% → 100% ▲ functional
- Tool “get_pricing” now declares an output schema ▲ functional
- Tool “get_search_status” now declares an output schema ▲ functional
- Tool “register_agent” now declares an output schema ▲ functional
- Tool “start_job_search” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: fair → good functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “quick_job_search” functional
- “start_job_search” added an optional parameter “cv_json” cosmetic
- “get_search_status” reworded the description of “run_id” cosmetic
- “register_agent” reworded the description of “email” cosmetic
- “register_agent” reworded the description of “name” cosmetic
- “start_job_search” reworded the description of “cv_base64” cosmetic
- “start_job_search” reworded the description of “cv_type” cosmetic
- “start_job_search” reworded the description of “profile” cosmetic
- “start_job_search” made “cv_base64” optional cosmetic
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 55
First indexed and scored.
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 3 Aug 2026 · Probed https://jobero.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobero.ai | CN=YE2,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5e63eebe5c8cf987f9258c798f58c56ba76 |
| SANs: *.jobero.ai, jobero.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of jobero.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| jobero.ai. | present | 2371 | 13 | Verified |
| jobero.ai. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobero.ai/mcp | Verified | 200 | |
| http (plaintext) | http://jobero.ai/mcp | Inconclusive | 405 |
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.
get_pricing Get pricing ~33
What a Jobero 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 Jobero 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.