Jobinja Employer
PYPI · JOBINJA-EMPLOYER-MCP
Review and shortlist resumes received in the Jobinja employer panel with low token use.
Available components
Last scanned (5 hours ago)
Scores higher than 59% of PyPI servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to saeedsepehr/jobinja-employer-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1431 tokens (~75/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (11% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 77
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/jobinja-employer-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | saeedsepehr/jobinja-employer-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/saeedsepehr/jobinja-employer-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 3619780082 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c8d96d6b2ed00bd5bacdee4c65214817096064e6bb0654b487274cd3924a6308 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_note Add team note ~56
Add a confidential team note to an applicant (visible to company members only, not to the candidate).
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| page_hint | – | – | – |
| post | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
create_folder Create resume folder ~38
Create a new resume folder and return its id. If a folder with this exact title exists, returns it instead.
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | – |
No output schema declared.
No examples provided.
delete_note Delete team note ~67
Delete one team note whose text contains `text_contains` (e.g. to fix a mistaken note). Only notes you can delete in the panel.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| page_hint | – | – | – |
| post | string | yes | – |
| text_contains | string | yes | – |
No output schema declared.
No examples provided.
download_resume Download resume ~69
Download an applicant's attached resume file (usually PDF) and return its local path, ready to be read. Default folder: JOBINJA_DOWNLOAD_DIR/<post>/.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| dest_dir | – | – | – |
| page_hint | – | – | – |
| post | string | yes | – |
No output schema declared.
No examples provided.
download_resumes Download resumes in bulk ~99
Bulk-download resumes for a job ad, newest first, optionally filtered by status / starred (see list_applicants). Downloads at most `limit` files into JOBINJA_DOWNLOAD_DIR/<post>/ (or dest_dir). Viewing pending applicants marks them as seen, as in the panel.
| Name | Type | Req | Description |
|---|---|---|---|
| dest_dir | – | – | – |
| limit | integer | – | – |
| post | string | yes | – |
| starred | boolean | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
get_applicant Get applicant details ~101
Get one applicant: contact info, profile fields, Jobinja profile text, star, team notes, current decision and rejection reason. applicant_id comes from list_applicants; page_hint (the list page it was on) makes lookup faster. Like opening it in the panel, viewing an unreviewed (pending) applicant marks it as seen.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| page_hint | – | – | – |
| post | string | yes | – |
No output schema declared.
No examples provided.
get_resume_text Get resume text ~83
Extracted plain text of an applicant's PDF resume, truncated to max_chars. Much cheaper in tokens than reading the PDF itself. Scanned (image-only) PDFs give little or no text; use download_resume for those.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| max_chars | integer | – | – |
| page_hint | – | – | – |
| post | string | yes | – |
No output schema declared.
No examples provided.
jobinja_status Check Jobinja session ~27
Check whether the saved Jobinja session is still logged in and which company panel it uses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_applicants List applicants ~169
List applicants of a job ad, 25 per page (newest first by default). post: short id from list_posts (e.g. "tMEO"). status: pending (unreviewed) | read (awaiting decision) | interview | hired | dismissed | expired | canceled. starred / has_notes: only starred applicants / only those with team notes. sort: id (newest) | id_asc (oldest) | relevance. Each row has `applicant_id` (for the other tools), status, starred flag, note count and folders.
| Name | Type | Req | Description |
|---|---|---|---|
| has_notes | boolean | – | – |
| page | integer | – | – |
| post | string | yes | – |
| sort | string | – | – |
| starred | boolean | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
list_folder_applicants List applicants in folder ~50
List applicants saved in a resume folder, 25 per page. Each row includes the `post` it applied to.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
list_folders List resume folders ~31
List the company's resume folders (پوشههای رزومه) with their ids and per-stage counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_posts List job ads ~75
List the company's job ads with applicant counts. status: all | active | rejected | draft | closed | archived. Each item has `post` (short id such as "tMEO", used by the other tools), numeric `post_numeric_id`, title, publish state and per-stage counts.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_rejection_reasons List rejection reasons ~25
Rejection reasons accepted by reject_applicant (code -> panel label).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_login_window Open Jobinja login window ~55
Open a browser window on the user's screen to sign in to the Jobinja employer panel (first use, or when jobinja_status reports the session expired). The user types their own credentials; waits up to 10 minutes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reject_applicant Reject applicant ~119
Mark an applicant as rejected (نامناسب) with a reason code from list_rejection_reasons. Jobinja notifies the candidate of the rejection; `message` is optional extra text sent to the candidate with it (not an internal note: use add_note for that). dry_run=true fills the rejection form without submitting it.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| dry_run | boolean | – | – |
| message | string | – | – |
| page_hint | – | – | – |
| post | string | yes | – |
| reason | integer | yes | – |
No output schema declared.
No examples provided.
restore_applicant Restore applicant to awaiting decision ~57
Undo a decision: move an applicant back to "awaiting decision" (در انتظار تعیین وضعیت). Jobinja notifies the candidate.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| page_hint | – | – | – |
| post | string | yes | – |
No output schema declared.
No examples provided.
screen_applicants Screen applicants (compact digest) ~160
Compact screening digest of one page (up to 25) of applicants, for fast, low-token shortlisting. For each applicant: headline, status, star, notes, folders, key profile fields (work history, education, skills) and the first `resume_chars` characters of the PDF resume text. Gender, birth year, marital status and contact details are left out on purpose. Read the digests, then use get_resume_text / get_applicant only for the promising ones. Takes about a minute per page; opening pending applicants marks them as seen.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| post | string | yes | – |
| profile_chars | integer | – | – |
| resume_chars | integer | – | – |
| status | – | – | – |
No output schema declared.
No examples provided.
set_applicant_folders Add or remove applicant from folders ~90
Add an applicant to and/or remove it from resume folders. `add` / `remove` take folder ids or exact titles (see list_folders; use create_folder first for a new one). Returns the applicant's folders afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| add | – | – | – |
| applicant_id | string | yes | – |
| page_hint | – | – | – |
| post | string | yes | – |
| remove | – | – | – |
No output schema declared.
No examples provided.
set_star Star or unstar applicant ~60
Star (starred=true) or unstar (starred=false) an applicant. Stars are internal to the company.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant_id | string | yes | – |
| page_hint | – | – | – |
| post | string | yes | – |
| starred | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the Jobinja Employer MCP server?
Jobinja Employer runs locally as a PyPI package, launched with uvx jobinja-employer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · jobinja-employer-mcp
claude mcp add saeedsepehr-jobinja-employer-mcp -- uvx jobinja-employer-mcp
What is the Jobinja Employer MCP server?
Jobinja Employer is an MCP server listed in the public MCP registry as io.github.saeedsepehr/jobinja-employer-mcp. Review and shortlist resumes received in the Jobinja employer panel with low token use. This page covers its PyPI package (jobinja-employer-mcp).
Is the Jobinja Employer MCP server safe to use?
Jobinja Employer scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jobinja Employer MCP server expose?
Jobinja Employer exposes 19 tools: jobinja_status, list_posts, list_applicants, get_applicant, download_resume, and 14 more. Their descriptions and schemas cost roughly 1,431 tokens of context every time the server is loaded.
Is the Jobinja Employer MCP server still maintained?
Jobinja Employer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Jobinja Employer MCP server under?
Jobinja Employer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.