McpStamp Purchase Requisitions MCP server
io.github.theluckystrike/onboarding-purchase-requisition-inspection-runstheluckystrikestreamable-httpv0.23.0Scanned
Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off.
16 tools: 3 can delete or cancel things, 4 do something that can't be undone, 8 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things and 4 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the McpStamp Purchase Requisitions MCP server can do
The McpStamp Purchase Requisitions MCP server is published by the GitHub account theluckystrike. It has 16 tools. It can delete or cancel things (3 tools: purchase-requisition_item_remove, purchase-requisition_delete and run_delete), do things that cannot be undone, such as sending, paying or publishing (purchase-requisition_create, purchase-requisition_item_add, purchase-requisition_show and purchase-requisition_list) and create or change data (8 tools: run_start, run_check, run_show, run_list and 4 more). 1 tool only reads.
1 tool brings in text other people can write (license_status).
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.23.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 3Claude Code: deny
purchase-requisition_deleteDelete a purchase-requisition and its steps for good.No findings
Why it is in this group
- The name "purchase-requisition_delete" says "purchase": a word that usually means money moves, which cannot be taken back.
- The description's first verb is "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
purchase-requisition_item_removeRemove one step from a purchase-requisition by its I01-style id and bump the purchase-requisition version.No findings
Why it is in this group
- The name "purchase-requisition_item_remove" says "purchase": a word that usually means money moves, which cannot be taken back.
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
run_deleteDelete a run for good, with every answer on it.No findings
Why it is in this group
- The name "run_delete" says "run": a word for a change.
- The description's first verb is "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 4Claude Code: ask
purchase-requisition_createCreate a reusable purchase-requisition and return its CL-NNNN id: a name, a category and an optional description.No findings
Why it is in this group
- The name "purchase-requisition_create" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
purchase-requisition_item_addAdd one step to a purchase-requisition and return its I01-style id: text, an optional section heading, and required flag.No findings
Why it is in this group
- The name "purchase-requisition_item_add" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
purchase-requisition_listEvery purchase-requisition with its category, version, step count and how many runs came from it.No findings
Why it is in this group
- The name "purchase-requisition_list" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
purchase-requisition_showOne purchase-requisition with its steps in order, grouped by section, plus how many are required and how many runs have been started from it.No findings
Why it is in this group
- The name "purchase-requisition_show" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 8Claude Code: ask
license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
run_checkMark one step pass, fail or na, with who did it and when.No findings
Why it is in this group
- The name "run_check" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
run_listRuns newest first, with their purchaseRequisition, progress and sign-off state.1 finding
Why it is in this group
- The name "run_list" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_list" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
run_reportThe 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.1 finding
Why it is in this group
- The name "run_report" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_report" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
run_showThe 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 sig…1 finding
Why it is in this group
- The name "run_show" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_show" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_show" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
run_sign_offSign off a completed run with a name and a date, which freezes it.No findings
Why it is in this group
- The name "run_sign_off" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
run_startStart a dated run of a purchase-requisition and return its RUN-YYYY-NNNN id.No findings
Why it is in this group
- The name "run_start" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
run_statusMove a run back to open so a step can be answered again, or abandon it when the job did not happen.1 finding
Why it is in this group
- The name "run_status" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_status" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
license_statusReport 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.Reads text others writeNo findings
Why it is in this group
- The name "license_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:24 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition
- Authorization servers
- https://mcp.zovo.one
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (3 destructive, 4 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.zovo.one/mcp/purchase-requisition: tools/list returned 16 tools to an anonymous client, including purchase-requisition_item_remove (destructive), purchase-requisition_delete (destructive), run_delete (destructive), purchase-requisition_create (irreversible), purchase-requisition_item_add (irreversible) and 10 more
Posture changes
- Nov 17, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition
- Nov 10, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition to https://mcp.zovo.one/.well-known/oauth-protected-resource
Findings
Matches of fixed checks, with the text they matched.
- Warnrun_show
The server marks "run_show" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_show" says "run": a word for a change.
- Warnrun_list
The server marks "run_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_list" says "run": a word for a change.
- Warnrun_status
The server marks "run_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_status" says "run": a word for a change.
- Warnrun_report
The server marks "run_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_report" says "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition -> https://mcp.zovo.one/.well-known/oauth-protected-resource.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/purchase-requisition to https://mcp.zovo.one/.well-known/oauth-protected-resource
Install
Pinned to version 0.23.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http onboarding-purchase-requisition-inspection-runs https://mcp.zovo.one/mcp/purchase-requisitionclaude mcp add --transport http onboarding-purchase-requisition-inspection-runs https://mcp.zovo.one/mcp/purchase-requisitionRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__onboarding-purchase-requisition-inspection-runs__license_status"
],
"ask": [
"mcp__onboarding-purchase-requisition-inspection-runs__purchase-requisition_create",
"mcp__onboarding-purchase-requisition-inspection-runs__purchase-requisition_item_add",
"mcp__onboarding-purchase-requisition-inspection-runs__purchase-requisition_show",
"mcp__onboarding-purchase-requisition-inspection-runs__purchase-requisition_list",
"mcp__onboarding-purchase-requisition-inspection-runs__run_start",
"mcp__onboarding-purchase-requisition-inspection-runs__run_check",
"mcp__onboarding-purchase-requisition-inspection-runs__run_show",
"mcp__onboarding-purchase-requisition-inspection-runs__run_list",
"mcp__onboarding-purchase-requisition-inspection-runs__run_sign_off",
"mcp__onboarding-purchase-requisition-inspection-runs__run_status",
"mcp__onboarding-purchase-requisition-inspection-runs__run_report",
"mcp__onboarding-purchase-requisition-inspection-runs__license_activate"
],
"deny": [
"mcp__onboarding-purchase-requisition-inspection-runs__purchase-requisition_item_remove",
"mcp__onboarding-purchase-requisition-inspection-runs__purchase-requisition_delete",
"mcp__onboarding-purchase-requisition-inspection-runs__run_delete"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as onboarding-purchase-requisition-inspection-runs. Review it before you use it.
Capability tags behind 1 rule
- mcp__onboarding-purchase-requisition-inspection-runs__license_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/onboarding-purchase-requisition-inspection-runs/verify?hash=dcf90d3dc64f645a81d209a511992a4503ebe50dd10d2bce2db02c2f5380f916" | jq -e '.changed == false'Pinned hash dcf90d3dc64f, from Nov 15, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/onboarding-purchase-requisition-inspection-runs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/onboarding-purchase-requisition-inspection-runs)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.
McpStamp Purchase Requisitions MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the McpStamp Purchase Requisitions MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 15 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the McpStamp Purchase Requisitions MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: purchase-requisition_item_remove, purchase-requisition_delete and run_delete.
Can the McpStamp Purchase Requisitions MCP server do things that cannot be undone?
- Yes. 4 tools can send, pay, publish or merge: purchase-requisition_create, purchase-requisition_item_add, purchase-requisition_show and purchase-requisition_list.
What tools does the McpStamp Purchase Requisitions MCP server have?
- 16 tools: 3 destructive, 4 irreversible, 8 write, 1 read. purchase-requisition_item_remove, purchase-requisition_delete, run_delete, purchase-requisition_create, purchase-requisition_item_add, purchase-requisition_show, purchase-requisition_list, run_start and 8 more.
Does the McpStamp Purchase Requisitions MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the McpStamp Purchase Requisitions MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the McpStamp Purchase Requisitions MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.