jobContext

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as app.jobcontext/jobcontext and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 3 Nov 2026. Not supplied by the maker.

• search_jobs

  Keyword search over the title and full text of job postings of large companies in Japan (141322 postings from 7739 companies). Best matches first; each result has id, title, company, company_type (kin

• get_job

  Read one job posting by id (from search_jobs, filter_jobs, search_by_meaning, similar_jobs or get_company). Returns the fields of a result of search_jobs (prefectures, location_scope, place_estimated;

• get_company

  Get what the data says about one company, with where each fact is from: use it when the user names a company. Takes a company as in search_jobs; several matches return a list to choose from. Returns t

• filter_jobs

  Count and list job postings by conditions, all optional, all of which must hold (the arguments below, and a keyword query as in search_jobs). Returns total (with a query at most 5000 are counted; tota

• similar_jobs

  Find postings like ones the user liked, by meaning: the stored vectors of 1 to 5 postings (ids from search_jobs, filter_jobs, search_by_meaning, similar_jobs or get_company) are averaged and compared

• search_by_meaning

  Find postings by the meaning of one short request about the job to find, ranked by how close their text is to it: the work, the skills or tools, the level, the place, in Japanese, Chinese or English,

• job_search_guide

  job_search_guide: the usage guide of this server. Call it before the first search and when unsure how to go on: asking the user, writing requests, choosing tools, reading results and notices, showing