McpStamp Onboarding
MCPB · ONBOARDING.MCPB · 2 COMPONENTS
New-hire onboarding plans from role templates: tasks with due dates, progress, overdue items.
Available components
Last scanned (9 hours ago)
Scores higher than 81% of MCPB servers
Category Project Management
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 Security23
- 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.Unverified
- Known CVEs were checked across the 153 of 153 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 57 of 153 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1015 tokens (~101/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
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.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityNo 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.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 +45
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- 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). security
- Dependency health: unverified → 0.81 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 14 Oct 26 0
- 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. security
- 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 functional
- 10 Oct 26 5
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 5 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/onboarding.mcpb@0.22.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Deprecated | 2 |
| Stale | 57 |
| 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 →
license_activate Activate license ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
onboarding_hire_add Add a hire ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The hire's name, e.g. Ada Lovelace |
| role | string | yes | The role, e.g. engineer or sales. Lower-cased and hyphenated |
| start_date | string | yes | The day they start, YYYY-MM-DD. Task due dates are counted from here |
No output schema declared.
No examples provided.
onboarding_hire_list List hires ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
onboarding_overdue List overdue tasks ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hire | string | – | Only this hire's overdue tasks. Omit for every hire |
No output schema declared.
No examples provided.
onboarding_progress Show a hire's progress ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_csv | boolean | – | Return the plan as CSV. Pro only. Default false |
| hire | string | yes | The hire id, e.g. H-0001, or the name when only one carries it |
No output schema declared.
No examples provided.
onboarding_task_add Add a task to a hire ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| due_offset | integer | yes | Days after the hire's start date the task is due. 0 is day one |
| hire | string | yes | The hire id, e.g. H-0001, or the name when only one carries it |
| owner | string | yes | Who owns the task: hr, manager or it |
| text | string | yes | The task, as the person doing it will read it, e.g. Issue laptop and security badge |
No output schema declared.
No examples provided.
onboarding_task_done Mark a task done or skipped ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The day it was completed, YYYY-MM-DD. Default today |
| hire | string | yes | The hire id, e.g. H-0001, or the name when only one carries it |
| status | string | yes | done, skipped, or todo to put it back to outstanding |
| task | string | yes | The task id, e.g. K03, as shown by onboarding_progress |
No output schema declared.
No examples provided.
onboarding_template_apply Apply a role template to a hire ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hire | string | yes | 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 |
No output schema declared.
No examples provided.
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.
mcpb · onboarding.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9
macOS / Linux
echo "7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9 onboarding.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\onboarding.mcpb).Hash -eq "7c6662d660776632d72efb550e3a0f72b8696adca845645d6f04e4be92d05ec9"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.