# io.github.theluckystrike/onboarding (remote · mcp.zovo.one)

New-hire onboarding: role-based task templates, day-one to day-ninety checklists, completion.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

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

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/onboarding`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/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 1071 tokens (~97/item across 11 items; 9 tools + 2 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: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.theluckystrike/onboarding MCP server?

io.github.theluckystrike/onboarding is a hosted endpoint at https://mcp.zovo.one/mcp/onboarding, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-onboarding 'https://mcp.zovo.one/mcp/onboarding'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-onboarding": {
      "url": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-onboarding": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-onboarding]
url = "https://mcp.zovo.one/mcp/onboarding"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-onboarding": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/onboarding",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-onboarding --url 'https://mcp.zovo.one/mcp/onboarding' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-onboarding:
    url: "https://mcp.zovo.one/mcp/onboarding"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-onboarding": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-onboarding -t streamable-http -u 'https://mcp.zovo.one/mcp/onboarding'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-onboarding": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/onboarding"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-21 (score 79, +54)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-09-20 (score 25)

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` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-onboarding/mcp-onboarding#diagnostics

## Score history

- 2026-09-21: 79
- 2026-09-20: 25

## Common questions

### What is the io.github.theluckystrike/onboarding MCP server?

io.github.theluckystrike/onboarding is an MCP server listed in the public MCP registry as io.github.theluckystrike/onboarding. New-hire onboarding: role-based task templates, day-one to day-ninety checklists, completion. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/onboarding).

### Is the io.github.theluckystrike/onboarding MCP server safe to use?

io.github.theluckystrike/onboarding scores 79 out of 100 on VerifyMCP. 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.theluckystrike/onboarding MCP server expose?

io.github.theluckystrike/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 989 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/onboarding MCP server require authentication?

Yes. io.github.theluckystrike/onboarding asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/onboarding MCP server still maintained?

io.github.theluckystrike/onboarding is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/onboarding
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/onboarding
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/onboarding
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-onboarding/mcp-onboarding.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-onboarding/mcp-onboarding.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-onboarding/mcp-onboarding