openroles
PYPI · OPENROLES
Open roles from employers' own job boards: Greenhouse, Lever, Ashby, Workday and 12 more.
Available components
Last scanned (2 hours ago)
Scores higher than 81% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aranculleton/openroles). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 311 tokens (~155/item across 2 items; 2 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.3.0 functional
- 20 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Package version: 0.1.2 → 0.2.0 functional
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 62
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 23 Oct 2026 · Analysed pypi/openroles@0.3.0
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 | aranculleton/openroles |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aranculleton/openroles/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3366833554 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4e3e85728913efdeab6c876641b2bd01cf293beb813b055c8d8c3dd106d52268 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
find_job_board ~111
Find which applicant tracking system (Greenhouse, Lever, Ashby, Workday, Workable, Teamtailor, Personio, Recruitee, Rippling, JazzHR, Gem, Polymer, Manatal, Homerun or ClearCompany) an employer posts its jobs on. Give a company name, its careers page URL or a job board URL. Returns boards as ats:token, which list_open_roles accepts.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | company name, careers page URL or board URL |
No output schema declared.
No examples provided.
list_open_roles ~176
List an employer's open roles straight from its own job board, newest first: title, location, remote, posted date, department, pay where posted, and the URL to apply. Filter by title words, location and remote. Descriptions are left out unless asked for, to keep the answer short.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Workday only: narrow to one country by name |
| include_descriptions | boolean | – | – |
| limit | integer | – | – |
| location | string | – | text that must appear in a location, e.g. London or Remote |
| query | string | – | words that must all appear in the title |
| remote_only | boolean | – | – |
| since_days | integer | – | – |
| target | string | yes | ats:token, a board or careers URL, or a company name |
No output schema declared.
No examples provided.
How do I install the openroles MCP server?
openroles runs locally as a PyPI package, launched with uvx openroles. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · openroles
claude mcp add aranculleton-openroles -- uvx openroles
What is the openroles MCP server?
openroles is an MCP server listed in the public MCP registry as io.github.aranculleton/openroles. Open roles from employers' own job boards: Greenhouse, Lever, Ashby, Workday and 12 more. This page covers its PyPI package (openroles).
Is the openroles MCP server safe to use?
openroles scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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 openroles MCP server expose?
openroles exposes 2 tools: find_job_board, list_open_roles. Their descriptions and schemas cost roughly 287 tokens of context every time the server is loaded.
Is the openroles MCP server still maintained?
openroles is still listed as active in the MCP registry. We last reached this channel on 23 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 openroles MCP server under?
openroles declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.