# McpStamp Onboarding (mcpb · onboarding.mcpb)

New-hire onboarding plans from role templates: tasks with due dates, progress, overdue items.

- Trust score: 50/100 (low)
- Change this week: +45
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.zovo.one`: 95/100, [markdown](https://verifymcp.io/servers/theluckystrike-onboarding/mcp-onboarding.md), [page](https://verifymcp.io/servers/theluckystrike-onboarding/mcp-onboarding)
- mcpb · `onboarding.mcpb`: 50/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-onboarding/onboarding.md), [page](https://verifymcp.io/servers/theluckystrike-onboarding/onboarding)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/onboarding.mcpb`
- Version: `0.22.0`
- Transport: `stdio`
- SHA-256: `7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9`

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

- **Supply Chain Security**: 23/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 57 of 153 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/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 49 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1015 tokens (~101/item across 10 items; 9 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### How do I install the McpStamp Onboarding MCP server?

McpStamp Onboarding ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/onboarding.mcpb`
- SHA-256: `7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9`

### Verify on macOS / Linux

```bash
echo "7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9  onboarding.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\onboarding.mcpb).Hash -eq "7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9"
```

## 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-11-02 (score 50, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Dependency health: unverified → 0.81
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: excellent
- [functional] Licence: MIT
- [functional] Package version: 0.22.5 → 0.22.0

### 2026-10-14 (score 5, 0)

- [security] Stability: Stability not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no schema to assess.
- [functional] Tool coverage: Tool coverage not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we have no tool definitions to assess.
- [functional] Capabilities: Protocol version not yet verified: the bundle we downloaded does not match the SHA-256 its registry entry declares, and we do not run a bundle that fails that check, so we never saw its MCP handshake.
- [functional] Package version: 0.22.1 → 0.22.5

### 2026-10-10 (score 5)

First indexed and scored.

## MCP tools (9)

### `onboarding_hire_add` (~133 tokens)

Add a hire

Add a new hire and return its H-NNNN id: a name, a role and the day they start. The role is a grouping key, lower-cased and hyphenated. Add tasks with onboarding_task_add, or apply a role template with onboarding_template_apply.

Input parameters:

- `name` (string, required): The hire's name, e.g. Ada Lovelace
- `role` (string, required): The role, e.g. engineer or sales. Lower-cased and hyphenated
- `start_date` (string, required): The day they start, YYYY-MM-DD. Task due dates are counted from here

### `onboarding_hire_list` (~96 tokens)

List hires

Every hire with their role, start date, task counts, percent complete and overdue count. Filter by role or by a word in the name. Returns at most 500 rows, newest change first.

Input parameters:

- `contains` (string): Only hires whose name contains this text, matched case-insensitively
- `role` (string): Only hires in this role, matched after the same lower-case hyphenation applied on add

### `onboarding_task_add` (~158 tokens)

Add a task to a hire

Add one task to a hire's plan and return its K01-style id: the text, who owns it (hr, manager or it) and how many days after the start date it is due. The due date is counted from the hire's start date.

Input parameters:

- `due_offset` (integer, required): Days after the hire's start date the task is due. 0 is day one
- `hire` (string, required): The hire id, e.g. H-0001, or the name when only one carries it
- `owner` (string, required): Who owns the task: hr, manager or it
- `text` (string, required): The task, as the person doing it will read it, e.g. Issue laptop and security badge

### `onboarding_task_done` (~142 tokens)

Mark a task done or skipped

Mark one task on a hire done or skipped, with the day it happened. done counts toward the percent complete; skipped is a deliberate dismissal and never counts as done. A task can be set back to todo to reopen it.

Input parameters:

- `date` (string): The day it was completed, YYYY-MM-DD. Default today
- `hire` (string, required): The hire id, e.g. H-0001, or the name when only one carries it
- `status` (string, required): done, skipped, or todo to put it back to outstanding
- `task` (string, required): The task id, e.g. K03, as shown by onboarding_progress

### `onboarding_template_apply` (~168 tokens)

Apply a role template to a hire

Apply a role template to one hire (free) or many (Pro), copying the template's tasks into each hire with the template's version recorded. Editing the template afterwards never changes a hire already under way. If no template exists for the role, one is created from the tasks you pass.

Input parameters:

- `hire` (string, required): The hire to apply the template to. Pro: pass a comma-separated list of hire ids or names to apply to many at once
- `role` (string): The role template to apply, by id (T-0001) or role. If omitted, the hire's own role is used
- `tasks` (array): When no template exists for the role, create one from these tasks and apply it. Pro only when applying to more than one hire

### `onboarding_progress` (~98 tokens)

Show a hire's progress

One hire's whole plan: every task with its owner, due date and status, plus the percent complete, the overdue count and what is still outstanding. Pass as_csv for a Pro-only CSV export of the plan.

Input parameters:

- `as_csv` (boolean): Return the plan as CSV. Pro only. Default false
- `hire` (string, required): The hire id, e.g. H-0001, or the name when only one carries it

### `onboarding_overdue` (~63 tokens)

List overdue tasks

Every task that is still outstanding past its due date, across all hires or one hire, with how many days late. Returns at most 500 rows, most overdue first.

Input parameters:

- `hire` (string): Only this hire's overdue tasks. Omit for every hire

### `license_status` (~54 tokens)

License status

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

### `license_activate` (~71 tokens)

Activate license

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-onboarding/onboarding#diagnostics

## Score history

- 2026-11-06: 50
- 2026-11-05: 50
- 2026-11-04: 50
- 2026-11-03: 50
- 2026-11-02: 50
- 2026-11-01: 5
- 2026-10-31: 5
- 2026-10-30: 5
- 2026-10-29: 5
- 2026-10-28: 5
- 2026-10-27: 5
- 2026-10-26: 5
- 2026-10-25: 5
- 2026-10-24: 5
- 2026-10-23: 5
- 2026-10-22: 5
- 2026-10-21: 5
- 2026-10-20: 5
- 2026-10-19: 5
- 2026-10-18: 5
- 2026-10-17: 5
- 2026-10-16: 5
- 2026-10-15: 5
- 2026-10-14: 5
- 2026-10-13: 5
- 2026-10-12: 5
- 2026-10-10: 5

## Common questions

### What is the McpStamp Onboarding MCP server?

McpStamp Onboarding is an MCP server listed in the public MCP registry as io.github.theluckystrike/onboarding. New-hire onboarding plans from role templates: tasks with due dates, progress, overdue items. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/onboarding.mcpb).

### Is the McpStamp Onboarding MCP server safe to use?

McpStamp Onboarding scores 50 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 McpStamp Onboarding MCP server expose?

McpStamp Onboarding exposes 9 tools: onboarding_hire_add, onboarding_hire_list, onboarding_task_add, onboarding_task_done, onboarding_template_apply, and 4 more. Their descriptions and schemas cost roughly 983 tokens of context every time the server is loaded.

### What licence is the McpStamp Onboarding MCP server under?

McpStamp Onboarding declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the McpStamp Onboarding MCP server?

VerifyMCP ran 14 checks on McpStamp Onboarding, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about McpStamp Onboarding: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://www.mcpstamp.com/servers/onboarding/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-onboarding/onboarding.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-onboarding/onboarding/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-onboarding/onboarding.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-onboarding/onboarding