io.github.theluckystrike/purchase-requisition
io.github.theluckystrike/purchase-requisition
Is the io.github.theluckystrike/purchase-requisition MCP server down? Yes. It has given no valid answer since 2026-11-01: install failed.
Reusable purchase-requisitions and dated runs of them: pass, fail, not applicable, and a sign-off.
install failed down since 2026-11-01 · probed 2026-11-15 · unchanged since 2026-11-08
the bundle does not match the SHA-256 in the registry entry
- Bundle
- https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/purchase-requisition.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/theluckystrike/mcp-servers
- Website
- https://mcp.zovo.one/s/purchase-requisition
- Registry
- active, updated 2026-10-14 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- io.github.theluckystrike/pomodoro · alive
- io.github.theluckystrike/price-list · install failed
- io.github.theluckystrike/price-tracker · alive
- io.github.theluckystrike/purchase-order · install failed
- io.github.theluckystrike/qr-code · install failed
- io.github.theluckystrike/quotes · install failed
- io.github.theluckystrike/rate-card · install failed
- io.github.theluckystrike/receipts · alive
Servers that mention requisition.
- Supplier Operations — Requisition Audit — Kestrel Procurement Co. (98e58b8b) com.a2awire/benchmark-requisition-audit-2026-09-11-98e58b8b · alive
- PurchasePlus com.purchaseplus/mcp · needs auth
- McpStamp Purchase Requisitions io.github.theluckystrike/onboarding-purchase-requisition-inspection-runs · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-01, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.