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.

JobYap Job Search

REMOTE · MCP.JOBYAP.COM · 2 COMPONENTS · SCANNED SEP 21

Search job postings aggregated from companies' careers sites, plus each job's discussion thread.

0 this week 85 Trust /100
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 Security74
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 718 tokens (~89/item across 8 items; 8 tools + 0 resources), lean.Pass
  • 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 Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
  • Structured output schemas are declared (25% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Install

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

# add to Claude Code
claude mcp add --transport http com-jobyap-jobs 'https://mcp.jobyap.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-jobyap-jobs": {
      "url": "https://mcp.jobyap.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-jobyap-jobs": {
      "type": "http",
      "url": "https://mcp.jobyap.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-jobyap-jobs]
url = "https://mcp.jobyap.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jobyap-jobs": {
      "type": "remote",
      "url": "https://mcp.jobyap.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-jobyap-jobs --url 'https://mcp.jobyap.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-jobyap-jobs:
    url: "https://mcp.jobyap.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-jobyap-jobs": {
      "Transport": "http",
      "Url": "https://mcp.jobyap.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-jobyap-jobs -t streamable-http -u 'https://mcp.jobyap.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-jobyap-jobs": {
      "type": "http",
      "url": "https://mcp.jobyap.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 4 Sept 26 0
    • Tool “search_locations” rewrote its description, which is the text the model reads security
    • Tool “list_companies” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
  • 31 Aug 26 0
    • Stability: 0.97 → pass security
  • 30 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 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
  • 25 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
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 21 Sept 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 1 Aug 2026 30 Oct 2026 ECDSA 256 ECDSA-SHA256 400b8bc24b859655136c3f1f2002c01f
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. present 19718 13 Verified
jobyap.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

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
MCP tools · 8 exposed · ~718 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
fetch ~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.

NameTypeReqDescription
idstringyesA result id returned by search.
NameTypeReqDescription
idstringyes
metadataobjectyes
textstringyes
titlestringyes
urlstringyes

No examples provided.

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

NameTypeReqDescription
idyesNumeric JobYap job id, a full jobyap.com job URL, or a job page slug.

No output schema declared.

No examples provided.

get_job_comments ~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.

NameTypeReqDescription
idyesNumeric JobYap job id, a full jobyap.com job URL, or a job page slug.

No output schema declared.

No examples provided.

get_job_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 ~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.

search ~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.

NameTypeReqDescription
querystringyes
NameTypeReqDescription
resultsarrayyes

No examples provided.

search_jobs ~261

Search JobYap's aggregated job postings with structured filters. 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.

NameTypeReqDescription
companiesarrayExact company names from list_companies.
cursorstringOpaque cursor from a previous next_cursor.
has_commentsbooleanOnly jobs with community discussion.
include_totalbooleanAlso compute the total match count (slower).
locationsarrayLocation identifiers from search_locations, e.g. city-US-CA-san_francisco.
page_sizeinteger
posted_withinstringHard freshness filter on the publish date.
querystringSubstring matched against job titles only.
sortstringrecent (default) or popular (most discussed).
work_modestring

No output schema declared.

No examples provided.

search_locations ~111

Resolve a free-text place name ("bay area", "Germany", "berlin") 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.

NameTypeReqDescription
limitinteger
querystringyesPlace name fragment, minimum 2 characters.

No output schema declared.

No examples provided.

Common questions

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 85 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 8 tools: search_jobs, get_job, get_job_comments, search_locations, list_companies, and 3 more. Their descriptions and schemas cost roughly 718 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.