McpStamp Purchase Requisitions MCP server

• license_activateFree

  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.

• license_statusFree

  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.

• purchase-requisition_createwrite actionFree

  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.

• purchase-requisition_deletewrite actionFree

  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.

• purchase-requisition_item_addwrite actionFree

  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.

• purchase-requisition_item_removewrite actionFree

  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.

• purchase-requisition_listwrite actionFree

  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.

• purchase-requisition_showwrite actionFree

  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.

• run_checkwrite actionFree

  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.

• run_deletewrite actionFree

  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.

• run_listwrite actionFree

  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.

• run_reportwrite actionFree

  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.

• run_showwrite actionFree

  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.

• run_sign_offwrite actionFree

  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.

• run_startwrite actionFree

  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.

• run_statuswrite actionFree

  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.

• –Code scanpackage could not be scannedn/a
• Live reliabilityremote reachable in 3116ms17/20
• Tool poisoning16 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 14 write-action tools with no auth3/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

77/100

higher than 50% of 48,255 servers

Tools

16

the typical server has 7

Tools that change things

88%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

11 ms

faster than 98% of 30,031 servers

GitHub stars

2

more than 75% of 28,688 servers

McpStamp Purchase Requisitions: common questions

Is McpStamp Purchase Requisitions MCP server safe?

Mostly: it is graded B (77/100). Read the McpStamp Purchase Requisitions safety report

How do I install McpStamp Purchase Requisitions?

It runs remotely at mcp.zovo.one. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does McpStamp Purchase Requisitions need an API key?

Yes. The registry entry asks for MCP_LICENSE_KEY.

Is McpStamp Purchase Requisitions maintained?

The last commit was 2 days ago (2026-11-02). The latest release is v0.23.0.

Is McpStamp Purchase Requisitions up?

100% of our last 7 checks got an answer. We check remote servers about four times a day.

How does McpStamp Purchase Requisitions compare with other MCP servers?

safety score 77/100 (higher than 50% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 88% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.