McpStamp Onboarding
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
New-hire onboarding plans from role templates: tasks with due dates, progress, overdue items.
Available components
Last scanned (2 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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 1171 tokens (~106/item across 11 items; 9 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 11 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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Server version: 0.22.0 → 0.22.6 functional
- 15 Oct 26 +68
- Authorization: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.80 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
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 · Probed https://mcp.zovo.one/mcp/onboarding
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 39e1adfa4eb6500e0e3d48868766e3e9 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/onboarding"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/onboarding"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/onboarding |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/onboarding |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/onboarding | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/onboarding | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/onboarding |
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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-onboarding 'https://mcp.zovo.one/mcp/onboarding'
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 hosted endpoint (https://mcp.zovo.one/mcp/onboarding).
Is the McpStamp Onboarding MCP server safe to use?
McpStamp Onboarding scores 95 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 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 989 tokens of context every time the server is loaded.
Does the McpStamp Onboarding MCP server require authentication?
Yes. McpStamp 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 McpStamp Onboarding MCP server still maintained?
McpStamp Onboarding is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.