# McpStamp Purchase Requisitions (remote · mcp.zovo.one)

Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off.

- Trust score: 82/100 (high trust)
- Change this week: +57
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.zovo.one`: 82/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition.md), [page](https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition)
- mcpb · `purchase-requisition.mcpb`: 49/100, [markdown](https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-purchase-r.md), [page](https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-purchase-r)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/purchase-requisition`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.23.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-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/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).
  - Context-footprint check failed: tool/resource definitions use about 2282 tokens (~126/item across 18 items; 16 tools + 2 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**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% 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.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 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 McpStamp Purchase Requisitions MCP server?

McpStamp Purchase Requisitions is a hosted endpoint at https://mcp.zovo.one/mcp/purchase-requisition, 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-purchase-requisition-i 'https://mcp.zovo.one/mcp/purchase-requisition'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 81, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 81, +56)

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

### 2026-10-14 (score 25)

First indexed and scored.

## MCP tools (16)

### `purchase-requisition_create` (~138 tokens)

Create a purchase-requisition

Create a reusable purchase-requisition and return its CL-NNNN id: a name, a category and an optional description. Add steps with purchase-requisition_item_add. Free tier: 3 of them, runs unlimited.

Input parameters:

- `category` (string): A grouping key, lower-cased and hyphenated, e.g. handover or safety. Default general
- `description` (string): What this purchase-requisition is for and when to run it, printed at the top of a blank copy
- `name` (string, required): What the purchase-requisition is, e.g. Pre-delivery vehicle check or Site handover

### `purchase-requisition_item_add` (~216 tokens)

Add a step to a purchase-requisition

Add one step to a purchase-requisition and return its I01-style id: text, an optional section heading, and required flag. A required step left unanswered or failed blocks sign-off; an optional one does not.

Input parameters:

- `note` (string): Guidance printed under the step, e.g. the tolerance or the standard it is checked against
- `position` (integer): Insert at this 1-based position instead of at the end. Existing steps keep their ids
- `purchaseRequisition` (string, required): The purchase-requisition id, e.g. CL-0001, or its name when only one carries it
- `required` (boolean): Whether sign-off is blocked while this step is unanswered or failed. Default true
- `section` (string): A heading to group this step under, e.g. Exterior. Steps keep the order they were added within a section
- `text` (string, required): The step, as the person doing it will read it, e.g. Tyre pressures checked and recorded

### `purchase-requisition_item_remove` (~108 tokens)

Remove a step from a purchase-requisition

Remove one step from a purchase-requisition by its I01-style id and bump the purchase-requisition version. Runs already under way keep the step they started with, so nothing anybody already ticked is rewritten.

Input parameters:

- `item` (string, required): The step id, e.g. I03, as shown by purchase-requisition_show
- `purchaseRequisition` (string, required): The purchase-requisition id, e.g. CL-0001, or its name when only one carries it

### `purchase-requisition_show` (~110 tokens)

Show one purchase-requisition

One purchase-requisition with its steps in order, grouped by section, plus how many are required and how many runs have been started from it. Pass as_text for a blank printable copy with a box against each step.

Input parameters:

- `as_text` (boolean): Return a blank printable copy as plain text as well as the structured view. Default false
- `purchaseRequisition` (string, required): The purchase-requisition id, e.g. CL-0001, or its name when only one carries it

### `purchase-requisition_list` (~104 tokens)

List purchase-requisitions

Every purchase-requisition with its category, version, step count and how many runs came from it. Filter by category or by a word in the name. Returns at most 500 rows, newest change first.

Input parameters:

- `category` (string): Only purchase-requisitions in this category, matched after the same lower-case hyphenation applied on create
- `contains` (string): Only purchase-requisitions whose name contains this text, matched case-insensitively

### `purchase-requisition_delete` (~98 tokens)

Delete a purchase-requisition

Delete a purchase-requisition and its steps for good. Runs already started keep their own copy of the steps and stay readable: deleting the purchase-requisition erases nothing anybody signed.

Input parameters:

- `confirm` (boolean, required): Must be true. There is no undo and nothing is copied anywhere first
- `purchaseRequisition` (string, required): The purchase-requisition id, e.g. CL-0001, or its name when only one carries it

### `run_start` (~176 tokens)

Start a run of a purchase-requisition

Start a dated run of a purchase-requisition and return its RUN-YYYY-NNNN id. Steps are COPIED into the run, so editing the purchase-requisition later never changes a run under way. Runs are free, never capped.

Input parameters:

- `date` (string): The day the run happened, YYYY-MM-DD. Default today
- `note` (string)
- `purchaseRequisition` (string, required): The purchase-requisition id, e.g. CL-0001, or its name when only one carries it
- `reference` (string): The job, order or asset id this run belongs to, e.g. WO-2026-0044. Named only; no sibling store is opened
- `title` (string, required): What this run is against, e.g. Van BX21 KLM, February service

### `run_check` (~202 tokens)

Answer a step in a run

Mark one step pass, fail or na, with who did it and when. na means the step did not apply; it counts as answered and never as passed. A step can be answered again while the run is open, and the last answer stands.

Input parameters:

- `at` (string): The day it was answered, YYYY-MM-DD. Default the run's own date
- `by` (string): Who answered it. Printed against the step on the report
- `item` (string, required): The step id, e.g. I03, as shown by run_show
- `note` (string): What was found. Say why on a fail: the report prints this under the step
- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it
- `state` (string, required): pass, fail, na for did not apply, or pending to put the step back to unanswered

### `run_show` (~83 tokens)

Show one run

The whole run: every step with its answer, who answered it and when, grouped by section, plus the pass, fail and outstanding counts, the failures in full, and whether it can be signed off and why not.

Input parameters:

- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `run_list` (~147 tokens)

List runs

Runs newest first, with their purchaseRequisition, progress and sign-off state. Filter by purchaseRequisition, by status, by reference or to open runs only. Returns at most 500 rows.

Input parameters:

- `open_only` (boolean): Only open and complete runs, the ones still editable. Default false
- `purchaseRequisition` (string): Only runs of this purchaseRequisition, by id or name
- `reference` (string): Only runs against this job, order or asset id, matched case-insensitively
- `status` (string): Only runs in this status
- `with_failures` (boolean): Only runs that have at least one failed step. Default false

### `run_sign_off` (~169 tokens)

Sign off a run

Sign off a completed run with a name and a date, which freezes it. Refused while a required step is unanswered or failed, unless force is true, and either way the exceptions stay on the record and print on the report.

Input parameters:

- `by` (string, required): Who is signing it off, as it should read on the document
- `date` (string): The day it was signed, YYYY-MM-DD. Default today
- `force` (boolean): Sign off even though required steps are unanswered or failed. Default false; the reasons come back either way
- `note` (string): What the signature covers, or the exception being accepted
- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `run_status` (~142 tokens)

Reopen or abandon a run

Move a run back to open so a step can be answered again, or abandon it when the job did not happen. A signed-off run is refused: a signature is the point at which a run stops moving.

Input parameters:

- `date` (string): The day the step happened, YYYY-MM-DD. Default today
- `note` (string): Why. Kept on the run's history and printed nowhere else
- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it
- `status` (string, required): open puts a complete run back into edit; abandoned closes it without a signature

### `run_report` (~147 tokens)

Produce the run report

The run as plain text on every tier: every step with its mark, who answered it, the notes, the counts and a signature block or the recorded signature. Pro also writes it to out_path as a .txt file.

Input parameters:

- `out_path` (string): Where to write the .txt file. Pro only. Omit to get the report back as text, which every tier can do
- `overwrite` (boolean): Replace out_path if a file is already there. Default false, and an existing file is refused with nothing written
- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `run_delete` (~105 tokens)

Delete a run

Delete a run for good, with every answer on it. A signed-off run is refused: it is the record of what somebody put their name to. Abandon a run you no longer want instead of deleting a signed one.

Input parameters:

- `confirm` (boolean, required): Must be true. There is no undo and nothing is copied anywhere first
- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries 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-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-10-14: 25

## Common questions

### What is the McpStamp Purchase Requisitions MCP server?

McpStamp Purchase Requisitions is an MCP server listed in the public MCP registry as io.github.theluckystrike/onboarding-purchase-requisition-in…. Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/purchase-requisition).

### Is the McpStamp Purchase Requisitions MCP server safe to use?

McpStamp Purchase Requisitions scores 82 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 Purchase Requisitions MCP server expose?

McpStamp Purchase Requisitions exposes 16 tools: purchase-requisition_create, purchase-requisition_item_add, purchase-requisition_item_remove, purchase-requisition_show, purchase-requisition_list, and 11 more. Their descriptions and schemas cost roughly 2,076 tokens of context every time the server is loaded.

### Does the McpStamp Purchase Requisitions MCP server require authentication?

Yes. McpStamp Purchase Requisitions 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 Purchase Requisitions MCP server still maintained?

McpStamp Purchase Requisitions 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.

### What did VerifyMCP test on the McpStamp Purchase Requisitions MCP server?

VerifyMCP ran 13 checks on McpStamp Purchase Requisitions, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/purchase-requisition
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://www.mcpstamp.com/servers/purchase-requisition/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-onboarding-purchase-requisition-inspection-runs/mcp-purchase-requisition