
Calculate a SKU reorder point, stock coverage and replenishment quantity from your own assumptions.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Calculate a SKU's reorder point, stock coverage and indicative replenishment quantity using daily demand, lead time, safety stock and committed units. The model assumes constant demand and lead time. It does not optimize purchase minimums, case multiples, campaigns, expiry, financing or supplier variability. With zero demand, coverage days are undefined. Confirmed inbound can improve position without preventing a stockout before arrival: check its timing. Input fields: dailyDemand: Your projection, excluding orders already counted as reserved. leadDays: From purchase placement to usable stock. reviewDays: Additional horizon used to calculate the replenishment target. safetyUnits: Your chosen buffer; no statistical service level is inferred. onHandUnits: Include your safety buffer; exclude damaged or unusable goods. reservedUnits: Unshipped commitments. They may exceed physical stock. incomingUnits: Only units usable within the lead time. A delay changes the scenario.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http reposicion-stock https://www.argohub.es/mcp/reposicion-stock
Calculate a SKU's reorder point, stock coverage and indicative replenishment quantity using daily demand, lead time, safety stock and committed units. The model assumes constant demand and lead time. It does not optimize purchase minimums, case multiples, campaigns, expiry, financing or supplier variability. With zero demand, coverage days are undefined. Confirmed inbound can improve position without preventing a stockout before arrival: check its timing. Input fields: dailyDemand: Your projection, excluding orders already counted as reserved. leadDays: From purchase placement to usable stock. reviewDays: Additional horizon used to calculate the replenishment target. safetyUnits: Your chosen buffer; no statistical service level is inferred. onHandUnits: Include your safety buffer; exclude damaged or unusable goods. reservedUnits: Unshipped commitments. They may exceed physical stock. incomingUnits: Only units usable within the lead time. A delay changes the scenario.
| Argument | Type | Description |
|---|---|---|
| leadDays* | integer | |
| reviewDays* | integer | |
| dailyDemand* | number | |
| onHandUnits* | integer | |
| safetyUnits* | integer | |
| incomingUnits* | integer | |
| reservedUnits* | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"dailyDemand",
"leadDays",
"reviewDays",
"safetyUnits",
"onHandUnits",
"reservedUnits",
"incomingUnits"
],
"properties": {
"leadDays": {
"type": "integer",
"maximum": 3650,
"minimum": 0
},
"reviewDays": {
"type": "integer",
"maximum": 3650,
"minimum": 1
},
"dailyDemand": {
"type": "number",
"maximum": 1000000,
"minimum": 0,
"multipleOf": 0.0001
},
"onHandUnits": {
"type": "integer",
"maximum": 1000000,
"minimum": 0
},
"safetyUnits": {
"type": "integer",
"maximum": 1000000,
"minimum": 0
},
"incomingUnits": {
"type": "integer",
"maximum": 1000000,
"minimum": 0
},
"reservedUnits": {
"type": "integer",
"maximum": 1000000,
"minimum": 0
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 12, 2026.