Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
jobContext is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Job postings from company career sites in Japan, with company facts. Public beta, no sign-in.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jobcontext-mcp https://beta.jobcontext.app/mcp
# 2 — ask your agent for something these tools do
# search_jobs, get_job, get_company and 4 more
jobContext costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
JOAll 1 server
jobcontext1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http jobcontext-mcp https://beta.jobcontext.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 (kind of business), location, prefectures, place_estimated (the head office, an estimate: the posting states no place), employment_type (as written), employment (the types it offers), date_posted (the day
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search terms, e.g. 経理 東京 or "data engineer" python |
| company | string | no | Companies whose name contains this text (トヨタ finds トヨタ紡織; 株式会社 and width do not matter; at most 100). The text may also be the company's reading in katakana (ミクシィ finds 株式会社ＭＩＸＩ), its English name, or |
| sources | array | no | Only postings collected from these sources: airwork, avature, eightfold, engage, greenhouse, herp, hrmos, html, i-web, jobcan, jposting, json_ld, lever, oracle, smartrecruiters, talentio, workable, wo |
| employment | array | no | Only postings that offer any of these employment types: regular 正社員, contract 契約社員, part_time パート・アルバイト, dispatch 派遣, outsourcing 業務委託, intern, other. A posting that does not say what it offers is not |
| filter | no | The conditions of filter_jobs, as an object. employment, company, sources and limit are arguments of their own next to filter, not conditions (employment inside filter is read as the argument). A sala | |
| limit | integer | no | Most postings to return (default 10) |
| offset | integer | no | Where the page starts, in postings from 0 (default 0): the next_offset of the previous page |
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; extracted with machine_extracted: true (read by a model: the posting at its url is the truth) or not_extracted: true), requirements (the lines under its heading of must-haves, as written) and require
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The posting id, e.g. 1010001000006-dd671a3c2e34 |
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 the company; facts by source (gBizINFO, しょくばらぼ), each block with as_of (the day the data was taken), updated (the day the source changed its record: an old record, the representative's above all, may b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company | string | yes | Company name part, katakana reading or website name, or 13-digit 法人番号, as in search_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; total_is_lower_bound says there are more) and a page of up to limit postings as in search_jobs, without the snippet, from offset (more: true: a next page, from next_offset); limit 0 returns the total only
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employment | array | no | as in search_jobs |
| location | string | no | Work location contains this text, as the page writes it; width and case ignored, nothing translated (東京 does not find Tokyo) |
| salary | array | no | Pay in yen that reaches at_least in its period. A floor the user states (年収600万以上) is basis min, the default (the bottom of the stated range reaches it); basis max (the top reaches it, so a range that |
| japanese | array | no | Japanese requirement (either: Japanese or English will do) |
| english | array | no | English requirement (either: as for japanese) |
| remote | array | no | Remote work: any of these |
| visa | boolean | no | true: postings that say they sponsor a visa (not those that say they do not or say nothing) |
| overtime | object | no | Fixed overtime stated as at most max_hours hours a month (0: states none) |
| average_overtime | object | no | Overtime worked, as stated: the monthly average is at most max_hours (0: states none; a company-wide average counts (average_overtime_scope: company); ほぼなし and 少なめ are not stated) |
| experience | object | no | The years of experience the user has in the kind of work they look for. years: names them; every result then shows experience_gap (years asked less these), nothing is left out. max_years: leaves out p |
| engagement | array | no | Who the work is done for, stated by the posting itself (explicit statements only; accuracy is not measured yet): in_house the employer's own product or service, client_site placement at a client's sit |
| prefecture | array | no | Postings located in any of these prefectures (the normalised place): 東京都, 東京 and Tokyo are the same. A nationwide, remote or place-less posting names none and needs include_unstated, which adds a plac |
| company_type | array | no | Only companies of these types: product (own product or service), si_contract (SI, contract work), staffing (dispatch, SES), other_industry, unknown. Judged once per company by a model, about 96% preci |
| exclude_company_type | array | no | Drop companies of these types, judged as above (["staffing"] removes dispatch and SES firms). No tag passes |
| new_grad | boolean | no | true: only postings aimed at new graduates (the title says 新卒, 27卒, 卒業予定, 第二新卒, or is a selection internship, インターン); new_grad_kind says which. Use it only when the user says they are a new graduate |
| include_unstated | boolean | no | true: also postings that state nothing for the field, and those not processed (not_extracted). Default: only those that state it and match; experience and english let through those that state nothing, |
| company | string | no | Company, as in search_jobs |
| sources | array | no | as in search_jobs |
| query | string | no | Keywords as in search_jobs; leave out to count by the conditions alone |
| sort | string | no | salary: annual pay, high to low, by the bottom of the stated range; postings that state no pay last. newest: by date_posted, newest first; known for 106760 of the 141322 postings served (76%), the oth |
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 with every other posting. Nothing is sent to an embedding service or paid for: use it freely to widen a search from a posting the user liked. The seed postings and exact copies of them are never liste
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | 1 to 5 posting ids the user liked or wants more of (named in the description) |
| scope | string | no | other_companies (default): postings of other companies than the seeds'; same_company: only postings of the seeds' companies; any: all |
| sources | array | no | as in search_jobs |
| employment | array | no | as in search_jobs |
| filter | no | The conditions of filter_jobs, as an object. employment, sources and limit are arguments of their own next to it. A salary condition leaves out postings that state no salary; a pay floor the user stat | |
| limit | integer | no | as in search_jobs |
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, at most 200 characters on at most 3 lines (for example 経理 月次決算 東京 リモート可). Use it once for each direction the user wants to look in. When the user gives you a resume or asks you to find jobs, read the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request | string | yes | One short request about one direction: the role, the level wanted (シニア, リード, 未経験歓迎) and the user's first preference (at most 200 characters on 3 lines) |
| keywords | string | no | Words the posting must say, as in search_jobs (every term must occur; "double quotes" keep a phrase together). Searched on the server, not sent to the embedding service |
| keywords_mode | string | no | boost (default): the postings the keywords find rise in the ranking, those the meaning finds stay. require: only postings that have every keyword; the meaning ranks within that set and the order is as |
| company | string | no | Company, as in search_jobs |
| sources | array | no | as in search_jobs |
| employment | array | no | as in search_jobs |
| filter | no | The conditions of filter_jobs, as an object. employment, company, sources and limit are arguments of their own next to it. A salary condition leaves out postings that state no salary; a pay floor the | |
| limit | integer | no | as in search_jobs |
| offset | integer | no | Where the page starts among the postings the request ranked, from 0 (default 0): the next_offset of the previous page |
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 the shortlist, checking a company, what never to do. No topic: the overview and the list of topics; a topic: that section.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | One of: overview, coverage, interview, requests, directions, results, notices, present, companies, privacy, rules, failures, examples |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install jobContext or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.1.0 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest8f798579df1566607cc6bb3934e3beec04157d9e8ea21543edca9f97b6cc2818
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_jobs | no tags | |
| get_job | no tags | |
| get_company | no tags | |
| filter_jobs | no tags | |
| similar_jobs | no tags | |
| search_by_meaning | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| job_search_guide | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8f798579df156660
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish jobContext can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.