replenishradar
https://server.smithery.ai/pro/replenishradar/mcp# ReplenishRadar MCP Multi-channel inventory forecasting and reorder automation for **Shopify and Amazon sellers**. Connect an AI agent to live inventory data: predict stockouts, surface what to reorder, and manage purchase orders end to end. ## What you can do **Read (works with any read key)** - Stockout risk, inventory positions, and demand forecasts by SKU or location - Suggested and canonical replenishment actions (what to buy or transfer next) - Alerts, sales history, top sellers, slow movers, and lost-sales estimates - Purchase orders, suppliers, sync status, and store/data-health diagnostics **Write (requires a write-scope key + tool group)** - Create, update, approve, send, and cancel purchase orders (always drafted first) - Execute replenishment actions in draft or, when explicitly enabled, autonomous mode - Manage locations and stock, import POs from Stocky / Inventory Planner, and store bounded agent context ## Auth and safety Every call is authenticated with an `rr_sk_` API key and scoped to a single organization. Read tools need only a read key; write tools require explicit write capabilities and the matching tool group, so a leaked key can't control everything. Purchase orders are always created as drafts and require human approval before they're sent to a supplier. ## Get started Generate an API key in **Settings > API Keys** at [app.replenishradar.com](https://app.replenishradar.com), or request a no-signup, read-only sandbox key to try it against demo data first. Full docs: [replenishradar.com/docs/mcp](https://replenishradar.com/docs/mcp).
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 23/25 | Endpoint answers the MCP initialize handshake (6205 ms); very slow response -2. |
| Protocol revision | 10/10 | Speaks the current MCP revision 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 51 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 95% of peers
- This listing 88 · peer median 81
- Latency
- Faster than 28% of peers
- This listing 528 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Live MCP endpoint −2
— Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (6205 ms); very slow response -2.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/pro/replenishradar/mcpcurl -X POST https://server.smithery.ai/pro/replenishradar/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'