# io.github.smeet666/mcp-lever (mcpb · mcp-lever.mcpb)

Search public Lever job boards: resolve a company, read its openings, read one in full.

- Trust score: 46/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- mcpb · `mcp-lever.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/smeet666-mcp-lever/https-github-com-smeet666-mcp-lever-releases-download-v1-0-1-mcp-lever-mcpb.md), [page](https://verifymcp.io/servers/smeet666-mcp-lever/https-github-com-smeet666-mcp-lever-releases-download-v1-0-1-mcp-lever-mcpb)
- npm · `mcp-lever`: 82/100, [markdown](https://verifymcp.io/servers/smeet666-mcp-lever/mcp-lever.md), [page](https://verifymcp.io/servers/smeet666-mcp-lever/mcp-lever)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/smeet666/mcp-lever/releases/download/v1.0.1/mcp-lever.mcpb`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 13/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

- Download bundle: `https://github.com/smeet666/mcp-lever/releases/download/v1.0.1/mcp-lever.mcpb`

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-22 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-21 (score 45, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-14 (score 42)

First indexed and scored.

## MCP tools (4)

### `resolve_company` (~100 tokens)

Resolve company names to Lever boards

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.

Input parameters:

- `names` (array, required): A list of a company name, or a Lever site name you already know, one to 25 of them.

Output parameters:

- `notes` (array)
- `resolved` (array)

### `search_jobs` (~454 tokens)

Search openings at named companies

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.

Input parameters:

- `commitment` (array): A list of a commitment exactly as Lever writes it, one to 20 of them.
- `companies` (array, required): 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.

Output parameters:

- `jobs` (array)
- `notes` (array)
- `per_company` (array)
- `total_available` (null): Lever publishes no result count, so this is always null.

### `get_job` (~112 tokens)

Read one opening

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.

Input parameters:

- `company_slug` (string, required): 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, required): The identifier of one opening, as a search returns it.

Output parameters:

- `job` (object)
- `notes` (array)

### `list_filter_values` (~143 tokens)

List a company's filter wordings

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.

Input parameters:

- `company_slug` (string, required): 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.

Output parameters:

- `company_slug` (string)
- `fields` (object)
- `instance` (string)
- `notes` (array)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/smeet666-mcp-lever/https-github-com-smeet666-mcp-lever-releases-download-v1-0-1-mcp-lever-mcpb#diagnostics

## Score history

- 2026-08-22: 46
- 2026-08-21: 45
- 2026-08-20: 42
- 2026-08-19: 42
- 2026-08-18: 42
- 2026-08-17: 42
- 2026-08-16: 42
- 2026-08-15: 42
- 2026-08-14: 42

## Common questions

### 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 MCPB bundle (https://github.com/smeet666/mcp-lever/releases/download/v1.0.1/mcp-lever.mcpb).

### Is the io.github.smeet666/mcp-lever server safe to use?

io.github.smeet666/mcp-lever scores 46 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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.

### 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.

## Links

- Repository: https://github.com/smeet666/mcp-lever
- Changelog RSS feed: https://verifymcp.io/servers/smeet666-mcp-lever/https-github-com-smeet666-mcp-lever-releases-download-v1-0-1-mcp-lever-mcpb.xml
- Changelog JSON feed: https://verifymcp.io/servers/smeet666-mcp-lever/https-github-com-smeet666-mcp-lever-releases-download-v1-0-1-mcp-lever-mcpb.json
- HTML version of this page: https://verifymcp.io/servers/smeet666-mcp-lever/https-github-com-smeet666-mcp-lever-releases-download-v1-0-1-mcp-lever-mcpb