McpStamp Purchase Requisitions
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS
Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off.
Available components
Last scanned (4 hours ago)
Scores higher than 85% 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 Usability84
- 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
- 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. 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 18 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.
- 4 Nov 26 +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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 +56
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- First check of Authorization: partial security
- First check of Judged manipulation: pass security
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 14 Oct 26 25
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 5 Nov 2026 · Probed https://mcp.zovo.one/mcp/purchase-requisition
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/purchase-requisition"
Bearer realm="mcp.zovo.one", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition"| 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/purchase-requisition |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one/mcp/purchase-requisition |
| 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/purchase-requisition | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/purchase-requisition | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/purchase-requisition |
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.
purchase-requisition_create Create a purchase-requisition ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What the purchase-requisition is, e.g. Pre-delivery vehicle check or Site handover |
No output schema declared.
No examples provided.
purchase-requisition_delete Delete a purchase-requisition ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. There is no undo and nothing is copied anywhere first |
| purchaseRequisition | string | yes | The purchase-requisition id, e.g. CL-0001, or its name when only one carries it |
No output schema declared.
No examples provided.
purchase-requisition_item_add Add a step to a purchase-requisition ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The step, as the person doing it will read it, e.g. Tyre pressures checked and recorded |
No output schema declared.
No examples provided.
purchase-requisition_item_remove Remove a step from a purchase-requisition ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| item | string | yes | The step id, e.g. I03, as shown by purchase-requisition_show |
| purchaseRequisition | string | yes | The purchase-requisition id, e.g. CL-0001, or its name when only one carries it |
No output schema declared.
No examples provided.
purchase-requisition_list List purchase-requisitions ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
purchase-requisition_show Show one purchase-requisition ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_text | boolean | – | Return a blank printable copy as plain text as well as the structured view. Default false |
| purchaseRequisition | string | yes | The purchase-requisition id, e.g. CL-0001, or its name when only one carries it |
No output schema declared.
No examples provided.
run_check Answer a step in a run ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
| state | string | yes | pass, fail, na for did not apply, or pending to put the step back to unanswered |
No output schema declared.
No examples provided.
run_delete Delete a run ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. There is no undo and nothing is copied anywhere first |
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_list List runs ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
run_report Produce the run report ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_show Show one run ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_sign_off Sign off a run ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | 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 | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_start Start a run of a purchase-requisition ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The day the run happened, YYYY-MM-DD. Default today |
| note | string | – | – |
| purchaseRequisition | string | yes | 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 | yes | What this run is against, e.g. Van BX21 KLM, February service |
No output schema declared.
No examples provided.
run_status Reopen or abandon a run ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
| status | string | yes | open puts a complete run back into edit; abandoned closes it without a signature |
No output schema declared.
No examples provided.
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-onboarding-purchase-requisition-i 'https://mcp.zovo.one/mcp/purchase-requisition'
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.