McpStamp Purchase Requisitions is answering right now. Last checked 6 min ago. It exposes 16 tools. Last commit 6 Nov 2026.
Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off.
Uptime history
6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
16
Tools
read from the server
188 ms
Response time
average over 24h
2
Stars
last commit 6 Nov 2026
What changed 30
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 November 2026. No other catalogue keeps this.
6 Nov
15 tools changed the parameters they ask for30 times that day
license_activate, purchase-requisition_create, purchase-requisition_delete and 12 more
and 15 more, back to 6 November 2026
Nothing serious here today
Today is the operative word: we check McpStamp Purchase Requisitions every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
run in your terminal
claude mcp add onboarding-purchase-requisition-inspection-runs --transport http https://mcp.zovo.one/mcp/purchase-requisitionSettings → Connectors → Add custom connector, then paste this address
https://mcp.zovo.one/mcp/purchase-requisition~/.codex/config.toml
[mcp_servers.onboarding-purchase-requisition-inspection-runs]
url = "https://mcp.zovo.one/mcp/purchase-requisition".cursor/mcp.json
{
"mcpServers": {
"onboarding-purchase-requisition-inspection-runs": {
"url": "https://mcp.zovo.one/mcp/purchase-requisition"
}
}
}.vscode/mcp.json
{
"servers": {
"onboarding-purchase-requisition-inspection-runs": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/purchase-requisition"
}
}
}Available tools 16
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
purchase
purchase-requisition_create
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_delete
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_add
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_remove
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_list
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_show
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
run_check
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_delete
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_list
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.
license
license_activate
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_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.
report
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.
show
run_show
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.
sign
run_sign_off
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.
start
run_start
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.
status
run_status
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zovo.one/mcp/purchase-requisition | streamable-http | answering | 437 ms | 6 min ago |
Alternatives to McpStamp Purchase Requisitions
same job, measured the same wayPurchase Requisition
by theluckystrike
Reusable purchase-requisitions and dated runs of them: pass, fail, not applicable, and a sign-off.
McpStamp Checklists
by theluckystrike
Reusable checklists with dated runs: pass, fail or N/A per step, then a frozen sign-off.
Onboarding Checklist Inspection Runs
by theluckystrike
Onboarding and inspection checklists you reuse: dated runs, who ticked what, and a sign-off.
PLC Cloud Sim — LAD/SCL simulation over MCP
by tia-forge
Cloud PLC simulator: validate and step-run LAD/SCL programs, run scenarios, return PASS/FAIL.
McpStamp Goods Receipt
by theluckystrike
Receive goods against purchase orders: partial, damaged or short units, and each order's status.
Bruno MCP Studio
by ostico
Author, edit and run Bruno collections as files: HTTP, WebSocket, gRPC, per-request pass/fail.
Airtable
by airtable
Official Airtable MCP server — database and operations layer for agents.
McpStamp Contract Clauses
by theluckystrike
Save reusable contract clauses, search them, and assemble a contract as .docx or markdown.
McpStamp Purchase Requisitions — questions
Answers built from our own checks of this server.
What can McpStamp Purchase Requisitions do?
It exposes 16 tools, read directly from the server on our last check. Among them: license_activate, license_status, purchase-requisition_create, purchase-requisition_delete, purchase-requisition_item_add, purchase-requisition_item_remove and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is McpStamp Purchase Requisitions mostly used for?
Its tools cluster around purchase, run and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is McpStamp Purchase Requisitions working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 188 ms. The bar chart above shows every period we have measured.
How do I connect McpStamp Purchase Requisitions?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does McpStamp Purchase Requisitions need an API key?
No. McpStamp Purchase Requisitions completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is McpStamp Purchase Requisitions?
It answers our handshake in 188 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is McpStamp Purchase Requisitions open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 2 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.