# io.github.theluckystrike/job-card (remote · mcp.zovo.one)

Job cards for trades and field service: hours and materials per job, open to invoiced.

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

## Components

- remote · `mcp.zovo.one`: 78/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-job-card/mcp-job-card.md), [page](https://verifymcp.io/servers/theluckystrike-job-card/mcp-job-card)
- mcpb · `job-card.mcpb`: 44/100, [markdown](https://verifymcp.io/servers/theluckystrike-job-card/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-job-card-m.md), [page](https://verifymcp.io/servers/theluckystrike-job-card/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-job-card-m)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/job-card`
- 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-20.

- **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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 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.

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "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.

## 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-20 (score 78, +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.

### 2026-09-18 (score 77, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 76)

First indexed and scored.

## MCP tools (11)

### `job_card_create` (~197 tokens)

Open a job card

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.

Input parameters:

- `client` (string, required): Who the job is for, e.g. Kowalski bathroom refit, or Acme Ltd
- `currency` (string, required): ISO code the rates and prices are in
- `description` (string, required): 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, required): Where the job is, e.g. 14 Nowa Street, flat 3

### `job_card_log_labor` (~222 tokens)

Log hours on a job card

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.

Input parameters:

- `card` (string, required): The job card id, e.g. JC-2026-0003, or the client name when only one card has it
- `date` (string, required): The day the work was done, YYYY-MM-DD. A future date is refused
- `hours` (number, required): 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, required): The hourly rate in whole cents. 4500 is 45.00 an hour
- `worker` (string, required): Who did the work, e.g. Anna

### `job_card_log_material` (~200 tokens)

Log materials used on a job card

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.

Input parameters:

- `card` (string, required): The job card id, e.g. JC-2026-0003, or the client name when only one card has it
- `date` (string, required): The day it went in, YYYY-MM-DD. A future date is refused
- `item` (string, required): What went into the job, e.g. Copper pipe 15mm, or Consumer unit 10-way
- `note` (string)
- `qty` (number, required): How many, to the thousandth, e.g. 2 or 0.5
- `unit_cost_cents` (integer, required): What one costs in whole cents. 1299 is 12.99

### `job_card_update_status` (~156 tokens)

Move a job card one step

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.

Input parameters:

- `card` (string, required): 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, required): The next step for this card: open, in_progress, done, invoiced, archived. in-progress is accepted too

### `job_card_list` (~94 tokens)

List job cards

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.

Input parameters:

- `client` (string): Only cards whose client contains this text, case-insensitive
- `status` (string): Only cards at this status: open, in_progress, done, invoiced, archived

### `job_card_get` (~89 tokens)

Read one job card with its running totals

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.

Input parameters:

- `card` (string, required): The job card id, e.g. JC-2026-0003, or the client name when only one card has it

### `job_card_print` (~112 tokens)

Render the card for the client to sign

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.

Input parameters:

- `card` (string, required): 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

### `job_card_delete` (~87 tokens)

Delete an empty job card

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.

Input parameters:

- `card` (string, required): The job card id, e.g. JC-2026-0003, or the client name when only one card has it

### `job_card_summary` (~105 tokens)

Summarize a day or a week

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.

Input parameters:

- `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

### `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-job-card/mcp-job-card#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76

## Common questions

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

## Links

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