io.github.theluckystrike/job-card
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Job cards for trades and field service: hours and materials per job, open to invoiced.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1444 tokens (~120/item across 12 items; 11 tools + 1 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "job_card_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
How do I install the io.github.theluckystrike/job-card MCP server?
io.github.theluckystrike/job-card is a hosted endpoint at https://mcp.zovo.one/mcp/job-card, 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-job-card 'https://mcp.zovo.one/mcp/job-card'
{
"mcpServers": {
"theluckystrike-job-card": {
"url": "https://mcp.zovo.one/mcp/job-card"
}
}
} {
"servers": {
"theluckystrike-job-card": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/job-card"
}
}
} [mcp_servers.theluckystrike-job-card] url = "https://mcp.zovo.one/mcp/job-card"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-job-card": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/job-card",
"enabled": true
}
}
} openclaw mcp add theluckystrike-job-card --url 'https://mcp.zovo.one/mcp/job-card' --transport streamable-http
mcp_servers:
theluckystrike-job-card:
url: "https://mcp.zovo.one/mcp/job-card" {
"McpServers": {
"theluckystrike-job-card": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/job-card"
}
}
} assistant mcp add theluckystrike-job-card -t streamable-http -u 'https://mcp.zovo.one/mcp/job-card'
{
"mcpServers": {
"theluckystrike-job-card": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/job-card"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 76
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/job-card
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 | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| 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 Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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/job-card | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/job-card | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/job-card |
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 →
job_card_create Open a job card ~197
Open a job card for a job your crew is taking on and return its JC-YYYY-NNNN number: the client, the site, what the job is, the currency and when it is scheduled. Free tier: 10 active cards; archiving a finished job frees its slot.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Who the job is for, e.g. Kowalski bathroom refit, or Acme Ltd |
| currency | string | yes | ISO code the rates and prices are in |
| description | string | yes | What the job is, e.g. Replace the consumer unit and certify |
| note | string | – | – |
| scheduled_date | string | – | The date the crew is due on site, YYYY-MM-DD. May be in the future; it is a plan, not a log |
| site | string | yes | Where the job is, e.g. 14 Nowa Street, flat 3 |
No output schema declared.
No examples provided.
job_card_delete Delete an empty job card ~87
Delete a job card entered by mistake. One with labor or materials logged is refused, naming what it holds, because deleting it would lose the record of work done: archive it instead. The JC number is never reissued.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | The job card id, e.g. JC-2026-0003, or the client name when only one card has it |
No output schema declared.
No examples provided.
job_card_get Read one job card with its running totals ~89
Read one job card in full by JC number or client: every labor entry and every material used, the hours per worker, and the running totals -- labor, materials and grand total -- as integer cents with formatted amounts. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | The job card id, e.g. JC-2026-0003, or the client name when only one card has it |
No output schema declared.
No examples provided.
job_card_list List job cards ~94
List job cards newest first: client, site, status, hours logged, and the labor, materials and grand totals in cents. Filter by status and by client. Totals are kept per currency, never mixed.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only cards whose client contains this text, case-insensitive |
| status | string | – | Only cards at this status: open, in_progress, done, invoiced, archived |
No output schema declared.
No examples provided.
job_card_log_labor Log hours on a job card ~222
Log hours worked on a job card: who did the work, the day, the hours and the hourly rate in whole cents, with a note on what was done. The line value is hours times rate, rounded half-up to the cent, fixed the moment it is logged.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | The job card id, e.g. JC-2026-0003, or the client name when only one card has it |
| date | string | yes | The day the work was done, YYYY-MM-DD. A future date is refused |
| hours | number | yes | Hours worked, to the hundredth, e.g. 7.5 or 3.25. One entry is one worker's day at most |
| note | string | – | What was done, e.g. First fix, kitchen ring main |
| rate_cents | integer | yes | The hourly rate in whole cents. 4500 is 45.00 an hour |
| worker | string | yes | Who did the work, e.g. Anna |
No output schema declared.
No examples provided.
job_card_log_material Log materials used on a job card ~200
Log materials used on a job card: the item, the day it went in, the quantity and the unit cost in whole cents. The line value is quantity times unit cost, rounded half-up to the cent, fixed the moment it is logged.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | The job card id, e.g. JC-2026-0003, or the client name when only one card has it |
| date | string | yes | The day it went in, YYYY-MM-DD. A future date is refused |
| item | string | yes | What went into the job, e.g. Copper pipe 15mm, or Consumer unit 10-way |
| note | string | – | – |
| qty | number | yes | How many, to the thousandth, e.g. 2 or 0.5 |
| unit_cost_cents | integer | yes | What one costs in whole cents. 1299 is 12.99 |
No output schema declared.
No examples provided.
job_card_print Render the card for the client to sign ~112
Render a job card ready to print and hand to the client: the labor, the materials, the totals and a signature line for client sign-off. Markdown, or self-contained HTML that needs nothing from the network. Writes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | The job card id, e.g. JC-2026-0003, or the client name when only one card has it |
| format | string | – | markdown (default) or html. The HTML carries its own styling and references nothing external |
No output schema declared.
No examples provided.
job_card_summary Summarize a day or a week ~105
Hours and value for a day or a week: the job cards touched, the hours per worker, and the labor, materials and total value, kept per currency. A week runs Monday to Sunday. Touched means a labor or material entry dated inside the window.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | A date inside the window, YYYY-MM-DD. Default today |
| span | string | – | day (default) is the date itself; week is the Monday to Sunday containing it |
No output schema declared.
No examples provided.
job_card_update_status Move a job card one step ~156
Move one job card exactly one step: open, in_progress, done, invoiced, archived, stamping the date and an optional note into its history. A skipped or backwards step is refused and nothing is written. Archiving a finished job frees a free-tier slot.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | The job card id, e.g. JC-2026-0003, or the client name when only one card has it |
| date | string | – | The date to stamp the step with, YYYY-MM-DD. Default today |
| note | string | – | – |
| status | string | yes | The next step for this card: open, in_progress, done, invoiced, archived. in-progress is accepted too |
No output schema declared.
No examples provided.
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.
What is the io.github.theluckystrike/job-card MCP server?
io.github.theluckystrike/job-card is an MCP server listed in the public MCP registry as io.github.theluckystrike/job-card. Job cards for trades and field service: hours and materials per job, open to invoiced. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/job-card).
Is the io.github.theluckystrike/job-card MCP server safe to use?
io.github.theluckystrike/job-card scores 78 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/job-card MCP server expose?
io.github.theluckystrike/job-card exposes 11 tools: job_card_create, job_card_log_labor, job_card_log_material, job_card_update_status, job_card_list, and 6 more. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/job-card MCP server require authentication?
Yes. io.github.theluckystrike/job-card 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/job-card MCP server still maintained?
io.github.theluckystrike/job-card is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.