Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
ENTRA Jobs 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
Verified AI/tech jobs from company ATSs: search, fit matching, salary stats; employer job posting
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user entra-jobs-mcp '--' npx -y entra-mcp
# 2 — ask your agent for something these tools do
# search_jobs, get_job, list_companies and 13 more
ENTRA Jobs 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 can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx 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 entra-jobs-mcp '--' npx -y entra-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://mcp.entracareers.com/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http entra-jobs-mcp https://mcp.entracareers.com/mcpNothing is required, but it can take ENTRA_API_KEY (Employer API key (entra_live_…) from https://entracareers.com/employer/profile?tab=api-keys — enables employer tools), ENTRA_API_URL (Override the ENTRA API base URL (default https://entracareers.com/api)) if you want to set them.
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.
16 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.
Search thousands of verified AI & tech jobs on ENTRA (aggregated directly from company hiring systems — zero ghost jobs). Filters: work location, country, company, annual salary, experience, posted_within_days. rank_by date | salary | fit (fit needs profile_keywords). Returns total_found and live…
No parameter schema on file.
Full details of one ENTRA job by id: description, requirements, skills, salary band, company, apply link.
No parameter schema on file.
List companies hiring on ENTRA (OpenAI, Anthropic, SpaceX, Stripe and 300+ more) with open-role counts and profile links.
No parameter schema on file.
AI matching, live: pass resume_text (free text) or skills[] plus optional target_role / remote_only / country / min_salary. Extracts skills, role and seniority deterministically, runs 2–4 searches, dedupes and ranks with an explainable fit_score (0–100), why[], matched_skills, skill_gaps, salary…
No parameter schema on file.
Backward-compatible alias of match_jobs: skills[] (+ role_hint, remote_only, limit) → ranked verified roles with fit explanation.
No parameter schema on file.
Salary statistics for a role query from ENTRA listings that publish a band (up to 150 most recent): count_with_salary, min / p25 / median / p75 / max per currency (annualized; USD reported as USD-equivalent, other currencies as-is), top 5 companies by count. Listed bands only — no estimates.
No parameter schema on file.
Which companies are hiring for a role right now: aggregates ENTRA search results (up to 300 most recent roles) into companies with open-role counts, sample titles, latest post date, verified flag and profile URLs.
No parameter schema on file.
Prepare an application for an ENTRA job: returns the direct apply link and a short checklist. The human reviews and applies — no auto-submission.
No parameter schema on file.
Identify the employer API key: company, key name/prefix, granted scopes and which employer tools are usable. Calls GET /employer/api-keys/me (cached). Start here in employer mode.
No parameter schema on file.
Publish a job on ENTRA for your company (scope jobs:write). Human-friendly input: title, description, employment_type, work_location (remote/onsite/hybrid), country + city (names; resolved to ENTRA ids), optional specialization (free text, best active match), experience_level, salary band,…
No parameter schema on file.
List your company's jobs (scope jobs:read): status active | closed | all, optional search, limit, page. Each job: status, location, salary, applications count, expiry, public + manage URLs.
No parameter schema on file.
Close (unpublish) one of your jobs (scope jobs:write). Without confirm:true it only returns a preview of the job that would be closed; with confirm:true it PATCHes isActive:false. Reversible with update_job {is_active:true}.
No parameter schema on file.
Update fields of one of your jobs (scope jobs:write): title, description, requirements, employment_type, work_location, experience_level, salary_*, benefits, internal_job_id, expires_in_days (extend), country+city, specialization, is_active (re-open/close). Only the fields you pass are changed.
No parameter schema on file.
Applications to your jobs (scope applications:read): pass job_id for one job or nothing for all company jobs; optional status filter (client-side), limit, page. Shows candidate name, resume headline, cover letter and contact details exactly as ENTRA returns them — never inferred.
No parameter schema on file.
Search published resumes on ENTRA (scope candidates:read): query (title/bio text), skills[] (names → ANY match), specialization, country/city, experience, work_location/remote_only, employment_type, ready_to_relocate, expected-salary bounds, has_linkedin/has_portfolio, published_within_days, limit…
No parameter schema on file.
Rank candidates for one of your jobs (scope candidates:read): pass job_id (or job_text). Extracts skills/role/seniority deterministically (same extractor as match_jobs), runs 2–3 resume searches, dedupes and scores 0–100 with why[] (skills overlap, headline vs role, seniority, location/remote).…
No parameter schema on 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 ENTRA Jobs 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 | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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 (16 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>".
8 of the 16 recovered tools are registered only when employer holds (dist/server.js:1873) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 8.
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. moderate is the level these add up to.
8 tools are registered unconditionally · 8 more only when employer holds (dist/server.js:1873) — typically when a key or option is configured. All 16 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_jobs | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_job | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_companies | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| match_jobs | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| match_profile | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| salary_stats | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| companies_hiring | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| prepare_application | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| employer_whoami conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| post_job conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| my_jobs conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| close_job conditional | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| update_job conditional | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| job_applications conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search_candidates conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| match_candidates conditional | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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.
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.4.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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 ENTRA Jobs 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.