
JobYap MCP server
Which MCP servers are JobYap's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.jobyap/jobsverified in the MCP registry
The registry name sits under jobyap.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools9
- Server calls itselfjobyap
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 335 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 4 of the 7 days it takes to judge reliability.
Once connected
- For "browse recent tech job listings by company", the likely first call is search_jobs.
- Parameters are untyped or undescribed in 3 of 9 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- Use20 npm downloads a week1 GitHub stars
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer306 ms
- Space in an agent's context≈ 2,326 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 94 of 100
- Typed results2 of 9 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 9
What an agent can do with it
- can do · browse recent tech job listings by company
- not sure · filter tech jobs by location and comments
- not sure · watch for new tech jobs as they appear
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_jobsSearch 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…
match_jobsFind 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…
get_jobFetch 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…
get_job_commentsFetch 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.
search_locationsResolve 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…
list_companiesList every company JobYap tracks with its active job count and JobYap company-page URL. Use the exact names as search_jobs company filters.
get_job_statsAggregate stats: companies tracked, active job count, and the newest posting date.
searchSearch 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…
fetchRetrieve 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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"jobs": {
"type": "http",
"url": "https://mcp.jobyap.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http jobyap https://mcp.jobyap.com/mcpclaude.ai, ChatGPT and other clients: add https://mcp.jobyap.com/mcp as a custom connector in the settings.
Also shipped through: npm
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.