io.github.smeet666/mcp-lever
NPM · MCP-LEVER · 2 COMPONENTS
Search public Lever job boards: resolve a company, read its openings, read one in full.
Available components
Last scanned (2 hours ago)
Scores higher than 95% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to smeet666/mcp-lever). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1060 tokens (~265/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% 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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 17 Oct 26 +1
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −2
- Stability: pass → 0.80 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- Stability: pass → 0.93 functional
- 6 Oct 26 0
- Stability: 0.97 → pass security
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 17 Oct 2026 · Analysed npm/mcp-lever@2.0.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | smeet666/mcp-lever |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/smeet666/mcp-lever/.github/workflows/publish.yml@refs/tags/v2.0.1 |
| Rekor log index | 2644863562 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:03b0ba47161800f492ea2a5dc3191870140d3492b92ab4bbaace5b4cf73f72574c7144cee82251ca580708aa6fecbe2baa04779de2e0c32e12c0f085a |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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 →
get_job Read one opening ~112
Read one Lever opening in full: the advert, its named sections, and the salary as published. company_slug and instance are the ones the row carried, and a site living on both instances holds different openings on each.
| Name | Type | Req | Description |
|---|---|---|---|
| company_slug | string | yes | The Lever site name, as resolve_company returns it. |
| instance | string | – | The Lever instance the row came from. Left out, the global one is read. |
| job_id | string | yes | The identifier of one opening, as a search returns it. |
| Name | Type | Req | Description |
|---|---|---|---|
| job | object | yes | – |
| notes | array | yes | – |
No examples provided.
list_filter_values List a company's filter wordings ~143
List the team, location and commitment wordings one company uses on Lever, so a filter can carry the words that company publishes. The vocabulary belongs to each company: one writes Full-time, another Full Time, another EE Full-Time. Lever publishes no vocabulary for department, so a department filter is checked against the openings a company has open right now.
| Name | Type | Req | Description |
|---|---|---|---|
| company_slug | string | yes | The Lever site name, as resolve_company returns it. |
| fields | array | – | Which vocabularies to read. Each costs one request. All three by default. |
| instance | string | – | The Lever instance this site lives on. Left out, the global one is read. |
| Name | Type | Req | Description |
|---|---|---|---|
| company_slug | string | yes | – |
| fields | object | yes | – |
| instance | string | yes | – |
| notes | array | yes | – |
No examples provided.
resolve_company Resolve company names to Lever boards ~100
Turn company names into the Lever site names that address their job boards, and report every instance that answered. search_jobs resolves names on its own, so reach for this to check which of several companies are on Lever at all: it probes names without reading a single board, where a search would read one per company.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | A list of a company name, or a Lever site name you already know, one to 25 of them. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | array | yes | – |
| resolved | array | yes | – |
No examples provided.
search_jobs Search openings at named companies ~454
Search the openings published by named companies on Lever. `companies` takes company names or Lever site names, and each name is turned into a site name here. A name found on the first spelling costs 3 requests, and one that resists costs up to 9, at one second each. location, team, department and commitment are sent to Lever and need its exact wording. keyword, workplace_type, country, salary and recency are applied here, because Lever accepts none of them as filters. limit applies per company, so a company whose openings fill it may publish more. posted_within_days walks up to 5 pages per company, because Lever pages by title and a recent opening sits anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| commitment | array | – | A list of a commitment exactly as Lever writes it, one to 20 of them. |
| companies | array | yes | A list of a company name or a Lever site name, one to 25 of them. |
| country | array | – | A list of a two-letter country code, as in FR or US, one to 20 of them. |
| currency | string | – | A three-letter currency code, as in EUR or USD. |
| department | array | – | A list of a department exactly as Lever writes it, one to 20 of them. |
| keyword | string | – | Words to look for in the title and the advert. |
| limit | integer | – | How many openings to read per company. |
| location | array | – | A list of a location exactly as Lever writes it, one to 20 of them. |
| posted_within_days | integer | – | How recent an opening must be. |
| salary_interval | string | – | The period salary_min is written in, as Lever writes it, such as per-year-salary or per-hour-wage. |
| salary_min | number | – | The lowest upper bound of a salary range to keep. |
| skip | integer | – | How many openings to step over per company. |
| team | array | – | A list of a team exactly as Lever writes it, one to 20 of them. |
| workplace_type | array | – | A list of remote, hybrid, onsite or unspecified, one to 4 of them. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobs | array | yes | – |
| notes | array | yes | – |
| per_company | array | yes | – |
| total_available | null | yes | Lever publishes no result count, so this is always null. |
No examples provided.
How do I install the io.github.smeet666/mcp-lever server?
io.github.smeet666/mcp-lever runs locally as an npm package, launched with npx -y mcp-lever. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-lever
claude mcp add smeet666-mcp-lever -- npx -y mcp-lever
What is the io.github.smeet666/mcp-lever server?
io.github.smeet666/mcp-lever is listed in the public MCP registry as io.github.smeet666/mcp-lever. Search public Lever job boards: resolve a company, read its openings, read one in full. This page covers its npm package (mcp-lever).
Is the io.github.smeet666/mcp-lever server safe to use?
io.github.smeet666/mcp-lever scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 io.github.smeet666/mcp-lever server expose?
io.github.smeet666/mcp-lever exposes 4 tools: resolve_company, search_jobs, get_job, list_filter_values. Their descriptions and schemas cost roughly 809 tokens of context every time the server is loaded.
Is the io.github.smeet666/mcp-lever server still maintained?
io.github.smeet666/mcp-lever is still listed as active in the MCP registry. We last reached this channel on 17 October 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 io.github.smeet666/mcp-lever server under?
io.github.smeet666/mcp-lever declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.