JobYap Job Search
REMOTE · MCP.JOBYAP.COM · 2 COMPONENTS
Search job postings aggregated from companies' careers sites, plus each job's discussion thread.
Available components
Last scanned (13 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1326 tokens (~147/item across 9 items; 9 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (22% 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 9 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 current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Stability: 0.97 → pass security
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Probed https://mcp.jobyap.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobyap.com | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1ff16c428337914b0eb07b870a2b3a0d |
| SANs: jobyap.com, mcp.jobyap.com, *.mcp.jobyap.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 insecure
Validation of mcp.jobyap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| jobyap.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jobyap.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.jobyap.com/mcp | HTTPS enforced | 301 | https://mcp.jobyap.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 →
fetch Fetch JobYap document (deep research) ~59
Retrieve the full JobYap document for a search result id: the complete posting as markdown (description, salary, locations, apply link) plus top community comments, with a citable URL.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A result id returned by search. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_job Get job details ~83
Fetch one job posting in full: markdown description, salary ranges, locations with work mode, derived employment types, apply URL, posting dates and the canonical JobYap discussion URL. Works for expired jobs too (apply_url is null once inactive).
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Numeric JobYap job id, a full jobyap.com job URL, or a job page slug. |
No output schema declared.
No examples provided.
get_job_comments Get job discussion ~69
Fetch the community discussion thread for a job: chronological, threaded via parent_id, with like counts. Comments are user-generated content. Threads stay open after a job expires.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Numeric JobYap job id, a full jobyap.com job URL, or a job page slug. |
No output schema declared.
No examples provided.
get_job_stats JobYap stats ~25
Aggregate stats: companies tracked, active job count, and the newest posting date.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_companies List companies ~39
List every company JobYap tracks with its active job count and JobYap company-page URL. Use the exact names as search_jobs company filters.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
match_jobs Match jobs to a candidate ~554
Find and rank the best live postings for one specific candidate, such as someone who shared a resume or described their experience, skills or visa needs. Slow: it reads each posting's full description, so a call can take 10 to 15 seconds. For browsing, listing or counting postings, use search_jobs, which answers in under a second. Filters active jobs by title terms (any of them; a term matches when the title holds all its words), excluded title terms, companies, locations and posting window, then takes the newest 300 of that pool (pool_total says how many matched) and reads each full description. It drops postings with no usable description, postings whose stated minimum years of experience exceed candidate_years by more than 1, and, with needs_sponsorship, postings that refuse sponsorship or require citizenship or a clearance; dropped counts each reason. The rest are ranked by how many skills appear in the description, then newest first. Each result carries skills_matched, years_bar, flags and up to 6 requirement sentences. The screening is heuristic: read finalists in full with get_job.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_years | number | – | Candidate years of professional experience; drops postings that require more than one year beyond it. |
| companies | array | – | Exact company names from list_companies. With titles, a posting must match both. |
| exclude_companies | array | – | Company names to leave out, case-insensitive, e.g. the current employer. |
| exclude_titles | array | – | Title terms that remove a posting, matched like titles, e.g. "senior", "staff", "lead", "manager". |
| include_anywhere | boolean | – | With locations, also keep fully remote "Anywhere" postings. Default true. |
| limit | integer | – | Results to return, default 15. |
| locations | array | – | country-XX (ISO alpha-2) for a country, or state and city identifiers from search_locations. Omit for worldwide. |
| needs_sponsorship | boolean | – | Drop postings that refuse visa sponsorship or require citizenship or a security clearance. Default false. |
| posted_within | string | – | Posting window: 24h, 7d (default) or 30d. |
| skills | array | – | Specific skills and domain terms from the resume, as whole words or phrases. They rank results and never filter. |
| titles | array | – | Title terms, any of which may match. A term matches when the title contains all its words as whole words, in any order: "software engineer" also matches "Engineer, Software". Required unless companie… |
| work_mode | string | – | Only postings explicitly marked remote or hybrid. |
No output schema declared.
No examples provided.
search Search JobYap (deep research) ~71
Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_jobs Search jobs ~316
Search JobYap's aggregated job postings with structured filters. Fast (under a second): use it to browse, list, count or page through postings and to answer general questions about who is hiring. To find the best postings for one specific person (a resume, or their experience, skills or visa needs), use match_jobs instead. The text query matches job titles only (case-insensitive substring) — try synonyms or shorter tokens when results are thin. Company names must exactly match values from list_companies; locations must be identifiers from search_locations. work_mode matches jobs explicitly marked remote or hybrid (unmarked means unstated, not onsite). Results are active listings, newest first by default; sort=popular ranks by discussion activity. To paginate, pass next_cursor back as cursor and keep every other argument identical.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | – | Exact company names from list_companies. |
| cursor | string | – | Opaque cursor from a previous next_cursor. |
| has_comments | boolean | – | Only jobs with community discussion. |
| include_total | boolean | – | Also compute the total match count (slower). |
| locations | array | – | Location identifiers from search_locations, e.g. city-US-CA-san_francisco. |
| page_size | integer | – | – |
| posted_within | string | – | Hard freshness filter on the publish date. |
| query | string | – | Substring matched against job titles only. |
| sort | string | – | recent (default) or popular (most discussed). |
| work_mode | string | – | – |
No output schema declared.
No examples provided.
search_locations Search locations ~110
Resolve a free-text place name ("toronto", "Japan", "Texas") to the location identifiers search_jobs accepts (country-XX, state-XX-YY, city-XX-YY-name). Searches every place JobYap knows, not only those with current openings, so an identifier may match no jobs. City display omits the state, and the list can be shorter than limit.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Place name fragment, minimum 2 characters. |
No output schema declared.
No examples provided.
How do I install the JobYap Job Search MCP server?
JobYap Job Search is a hosted endpoint at https://mcp.jobyap.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 · mcp.jobyap.com
claude mcp add --transport http com-jobyap-jobs 'https://mcp.jobyap.com/mcp'
What is the JobYap Job Search MCP server?
JobYap Job Search is an MCP server listed in the public MCP registry as com.jobyap/jobs. Search job postings aggregated from companies' careers sites, plus each job's discussion thread. This page covers its hosted endpoint (https://mcp.jobyap.com/mcp).
Is the JobYap Job Search MCP server safe to use?
JobYap Job Search scores 84 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 JobYap Job Search MCP server expose?
JobYap Job Search exposes 9 tools: search_jobs, match_jobs, get_job, get_job_comments, search_locations, and 4 more. Their descriptions and schemas cost roughly 1,326 tokens of context every time the server is loaded.
Does the JobYap Job Search MCP server require authentication?
No. We connected to JobYap Job Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the JobYap Job Search MCP server still maintained?
JobYap Job Search is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the JobYap Job Search MCP server?
VerifyMCP ran 13 checks on JobYap Job Search, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.