io.github.smeet666/mcp-ashby
NPM · MCP-ASHBY · 2 COMPONENTS
Search public Ashby job boards: resolve a company, read its openings and the pay it publishes.
Available components
Last scanned (21 hours ago)
Scores higher than 93% 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-ashby). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 47 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1109 tokens (~221/item across 5 items; 5 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 −3
- Stability: pass → 0.80 functional
- 12 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Security disclosure: pass → unverified ▼ functional
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 4 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 16 Oct 2026 · Analysed npm/mcp-ashby@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-ashby |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/smeet666/mcp-ashby/.github/workflows/publish.yml@refs/tags/v2.0.1 |
| Rekor log index | 2644859336 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9729925189a9f2e50352f1bd7d3a7a73e4faa851800707a9edae5ee66af2e533fe05634a682938467cc3a73eea529b6098e368046b109375f1bfee703 |
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 →
compare_compensation Compare published pay on one board ~193
Put the pay ranges of one Ashby board side by side, one component at a time and one period at a time. Nothing is converted between currencies, summed across components or averaged: a third of the postings publish no range at all, and they are named rather than dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | A company name, or an Ashby board token. |
| component | string | – | One component at a time: a share of capital and a salary do not add up. |
| department | – | – | – |
| interval | string | – | The period compared, 1 YEAR unless named. Postings on another period are listed apart, unconverted. |
| job_ids | array | – | A list of posting identifiers search_jobs returned, one to 50 of them. |
| limit | integer | – | How many postings to compare. |
| query | string | – | Words to look for in the titles. |
| team | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | – |
| component | string | yes | – |
| currencies_present | array | yes | Named, because rows in different currencies do not rank against each other. |
| interval | string | yes | – |
| not_published | array | yes | Postings whose company publishes no range, named rather than dropped. |
| notes | array | yes | – |
| other_intervals | array | yes | Postings on another period, left unconverted. |
| rows | array | yes | – |
No examples provided.
get_job Read one posting ~113
Read one Ashby posting in full: its locations, its description and the pay ranges its company published. Ashby addresses a posting by board and identifier, both of which search_jobs returns.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | A company name, or an Ashby board token. |
| description | string | – | The description runs to thousands of characters. html is the company's own markup, unrewritten. |
| include_compensation | boolean | – | – |
| job_id | string | yes | The identifier search_jobs returned for this posting. |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string | yes | – |
| board | string | yes | – |
| compensation | – | yes | Null when the caller asked for no compensation, which states nothing about the company. |
| compensation_summary | string|null | yes | Null when the company withholds its pay ranges, which is never zero. |
| department | string | yes | – |
| description | – | yes | Null when the caller asked for no description. |
| employment_type | string | yes | – |
| id | string | yes | – |
| is_listed | boolean | yes | False marks a posting Ashby serves by direct link alone rather than on the board. |
| is_remote | boolean|null | yes | – |
| job_url | string | yes | – |
| location | object | yes | – |
| notes | array | yes | – |
| published_at | string | yes | ISO 8601 with the offset Ashby publishes. |
| secondary_locations | array | yes | – |
| source | object | yes | – |
| team | string | yes | – |
| title | string | yes | – |
| workplace_type | string|null | yes | Null when the company records none, which is never the same as on site. |
No examples provided.
list_filter_values List a board's filter wordings ~79
List the words one Ashby board actually uses, with how many postings carry each, and how many declare nothing. Every board keeps its own departments and teams, so a filter written from another board's vocabulary narrows to nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | A company name, or an Ashby board token. |
| facet | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | – |
| facets | object | yes | – |
| notes | array | yes | – |
| sibling_spellings | array | yes | Spellings on this board that name what looks like one place, so a caller asks for both rather than picking one. |
| total_jobs | integer | yes | – |
| undeclared | object | yes | Postings a criterion could say nothing about, counted per field. A posting that records no workplace is not a posting on site. |
No examples provided.
resolve_board Resolve company names to Ashby boards ~78
Turn a company name into the token that addresses its Ashby job board, and report every form that answered. search_jobs does this on its own, so call this when a name returns nothing and you want to see the spellings that were tried.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A company name, or an Ashby board token you already know. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | array | yes | – |
| input | string | yes | – |
| notes | array | yes | – |
| tried | array | yes | The forms actually sent, in order. |
No examples provided.
search_jobs Search postings at named companies ~339
Search the open postings of named companies on Ashby. Ashby publishes no index across its customers, so companies are required. Every filter runs here rather than at the source, and the answer reports how many postings declared nothing about a field it filtered on. Rows carry no description: read one posting with get_job.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | Company names or board tokens, one to 10. Each costs a request and a whole board, which is why 5 at a time is the comfortable number. |
| country | – | – | – |
| currency | string | – | A three-letter currency code, as in EUR or USD. |
| department | – | – | – |
| employment_type | – | – | – |
| has_compensation | boolean | – | Keeps only postings whose company publishes a pay range. |
| is_remote | boolean | – | Keeps only postings that declare it. Postings recording nothing are counted in undeclared rather than treated as on site. |
| limit | integer | – | How many postings to return. |
| location_contains | string | – | Part of a location line. |
| offset | integer | – | How many postings to skip. |
| published_after | string | – | An ISO 8601 date. |
| query | string | – | Words to look for. |
| salary_interval | string | – | The period salary_min belongs to, 1 YEAR unless named. An hourly amount is never weighed against a yearly floor. |
| salary_min | number | – | A floor for the salary component. |
| search_in | string | – | Where query is looked for. Descriptions run to thousands of characters each. |
| sort | string | – | – |
| team | – | – | – |
| workplace_type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| filters_applied | object | yes | – |
| jobs | array | yes | No descriptions, at any limit. |
| notes | array | yes | – |
| per_company | array | yes | – |
| returned | integer | yes | Postings in this answer, after limit and offset. |
| total_matched | integer | yes | Postings the criteria kept. |
| total_on_board | integer | yes | Postings the boards read hold, all of them. |
| undeclared | object | yes | Postings a criterion could say nothing about, counted per field. A posting that records no workplace is not a posting on site. |
No examples provided.
How do I install the io.github.smeet666/mcp-ashby server?
io.github.smeet666/mcp-ashby runs locally as an npm package, launched with npx -y mcp-ashby. 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-ashby
claude mcp add smeet666-mcp-ashby -- npx -y mcp-ashby
What is the io.github.smeet666/mcp-ashby server?
io.github.smeet666/mcp-ashby is listed in the public MCP registry as io.github.smeet666/mcp-ashby. Search public Ashby job boards: resolve a company, read its openings and the pay it publishes. This page covers its npm package (mcp-ashby).
Is the io.github.smeet666/mcp-ashby server safe to use?
io.github.smeet666/mcp-ashby scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 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-ashby server expose?
io.github.smeet666/mcp-ashby exposes 5 tools: resolve_board, search_jobs, get_job, list_filter_values, compare_compensation. Their descriptions and schemas cost roughly 802 tokens of context every time the server is loaded.
Is the io.github.smeet666/mcp-ashby server still maintained?
io.github.smeet666/mcp-ashby is still listed as active in the MCP registry. We last reached this channel on 16 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-ashby server under?
io.github.smeet666/mcp-ashby declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.