A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Job Search 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.
What it does
Job search mechanics for an AI assistant: search, fetch postings, render CVs, lint, log.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user michalper-job-search-mcp '--' uvx --from mcp-job-search-mp mcp-job-search
# 2 — ask your agent for something these tools do
# search_jobs, fetch_job_posting, render_pdf and 4 more
Job Search costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Job Search as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user michalper-job-search-mcp '--' uvx --from mcp-job-search-mp mcp-job-searchReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
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.
Searches real job-board APIs (Arbeitnow — free, always on; Adzuna and JSearch — only if their API keys are configured via environment variables). Returns normalized jobs plus a list of source errors (e.g. a source skipped because its key isn't set) — never raises on a single source's failure.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | string | yes | Keywords to match, e.g. 'PHP Magento backend'. |
| location | string | no | Free-text location filter, e.g. 'Poland'. |
| remote_only | boolean | no | Only return remote-flagged postings. |
| sources | array | no | Limit to these source names, e.g. ['arbeitnow']. Default: all. |
| use_cache | boolean | no | Reuse a cached result. False forces a fresh query. |
Fetches ONE job-posting URL you already found (any job board, including ones with no public API) and extracts its readable text generically. This is for a single posting a human found manually — never call it in a loop to enumerate a site's listings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | A single job-posting URL. |
Renders one CV/cover-letter HTML file to PDF via headless Chrome, using the exact flags known not to hang or silently drop output. Checks both the exit code and the actual PDF page count — call this once per file, never in a batch loop on the same Chrome profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| html_path | string | yes | Path to the source HTML file. |
| pdf_path | string | no | Output PDF path; defaults to the HTML path with .pdf. |
Read-only — never modifies html_path, pdf_path, or any other file. Lints a CV/cover-letter HTML file against YOUR OWN configurable rule set (banned phrases, skills-section bans, achievement-weight overclaims, title/GDPR/link checks, page-count limits), read from LINT_RULES_PATH (an env var, not a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| html_path | string | yes | Path to the HTML file to lint, as currently saved on disk. |
| pdf_path | string | no | Optional. Omit to run only the HTML-based checks (content, skills, weight, title, links). Pass the already-rendered PDF's path to ALSO check its page count against your configured page_limits and conf |
Mutates the registry file — appends one new row, it does not check for an existing one first. Call list_applications(company=...) beforehand if you need to avoid logging a duplicate. Target file and column layout come from REGISTRY_CONFIG_PATH (default: the bundled generic example). Never invents…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portal | string | yes | Section heading to log under, e.g. 'justjoin.it'. |
| date | string | yes | ISO date (YYYY-MM-DD) of the application. |
| company | string | yes | Company name. |
| role | string | yes | Role/title applied for. |
| rate | string | no | Rate/salary as free text. |
| mode | string | no | Work mode, e.g. 'Remote'. |
| level | string | no | Seniority/contract level, e.g. 'Senior B2B'. |
| status_note | string | no | Free-text status/notes — placed verbatim. |
| dry_run | boolean | no | Preview without writing to the file. |
Read-only — never modifies the registry file. Returns rows from your application registry, optionally filtered by portal (exact, case-insensitive section heading) and/or company (case-insensitive substring match). Call this before log_application to check whether you've already applied to a…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portal | string | no | Exact portal section name, e.g. 'justjoin.it'. Omit for all. |
| company | string | no | Case-insensitive substring match on the company field. |
Mutates the registry file — rewrites one row's status cell in place, leaving every other cell and the file's row order untouched. Finds the row by portal (exact) + company (case- insensitive substring); if more than one row matches, nothing is written and the error lists the matching line numbers…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| portal | string | yes | Exact portal section name, e.g. 'justjoin.it'. |
| company | string | yes | Case-insensitive substring match on the company field. |
| new_status | string | yes | Replacement text for the Status cell, placed verbatim. |
| role | string | no | Case-insensitive substring match on the role field, to disambiguate. |
| dry_run | boolean | no | Preview without writing to the file. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Job Search or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_jobs | no tags | |
| fetch_job_posting | untrusted-input | untrusted-input: keyword "fetch" |
| render_pdf | no tags | |
| lint_cv | no tags | |
| log_application | no tags | |
| list_applications | no tags | |
| update_application_status | 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
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
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.
Any signed-in account that does not publish Job Search can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.