Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Forthcast Inventory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
Demand forecasts, reorder points, order quantities and inventory health for Shopify stores.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http forthcast-inventory-mcp https://app.forthcast.io/mcp
# 2 — ask your agent for something these tools do
# get_inventory_overview, get_reorder_recommendations, find_inventory_items and 8 more
Forthcast Inventory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FOAll 1 server
forthcast1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http forthcast-inventory-mcp https://app.forthcast.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this when the merchant asks for a broad inventory health check, an executive summary, their urgent/excess/no-demand counts, inventory valuation, or current PO workload. Requires a connected Forthcast store; the assistant will prompt to sign in.
No parameter schema on file.
Use this when the merchant asks what to reorder, how much to buy, or which critical/warning items need action. Quantities reuse Forthcast's live lead-time, MOQ, case-pack, open-PO, location, and supplier minimum-order-value logic; this tool does not create a PO. Requires a connected Forthcast store; the assistant will prompt to sign in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| priority | string | no | Return order-now items, plan-ahead items, or both. |
| supplier | no | Optional case-insensitive supplier name filter. | |
| limit | integer | no | Maximum recommendations to return. |
Use this when the merchant wants a bounded list of their items filtered by urgency, assigned supplier, or Shopify vendor, such as all excess items or a supplier's critical SKUs. Requires a connected Forthcast store; the assistant will prompt to sign in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urgency | no | Optional Forthcast urgency bucket. | |
| supplier | no | Optional case-insensitive assigned supplier name. | |
| vendor | no | Optional case-insensitive Shopify vendor or brand. | |
| limit | integer | no | Maximum items to return. |
Use this when the merchant names an exact SKU and needs its live stock, forecast demand, days of supply, reorder point, suggested quantity, supplier, or open-PO coverage. Requires a connected Forthcast store; the assistant will prompt to sign in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sku | string | yes | Exact merchant SKU code. |
Use this when the merchant asks what is ordered, drafted, open, partially received, received, cancelled, overdue, expected, or associated with a named supplier. Results are grouped by PO; this tool does not approve, receive, cancel, or otherwise modify an order. Requires a connected Forthcast store; the assistant will prompt to sign in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | no | Optional exact purchase-order status. | |
| supplier | no | Optional case-insensitive supplier name filter. | |
| limit | integer | no | Maximum grouped purchase orders to return. |
Use this when the merchant asks how suppliers are performing or wants rolling 24-month on-time rate, fill rate, actual versus promised lead time, spend, or invoice price accuracy, plus current open and overdue purchase-order counts. Requires a connected Forthcast store; the assistant will prompt to sign in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier | no | Optional case-insensitive supplier name filter. | |
| limit | integer | no | Maximum suppliers to return. |
Use this when someone asks how much safety stock to hold or at what stock level to reorder a product. Give a daily demand history (best) or an average daily demand with its variability, plus the supplier lead time and a service level. Returns safety stock, lead-time demand and the reorder point with Forthcast's formula and assumptions. Works without a connected store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_time_days | integer | yes | Supplier lead time in days. |
| service_level | number | no | Target in-stock probability, 0.50 to 0.99 (95 also accepted). |
| daily_demand | no | Daily units sold, oldest first, 14 to 365 values. | |
| average_daily_demand | no | Average units sold per day, if no daily history. | |
| demand_std_daily | no | Standard deviation of daily demand; assumed sqrt(average) when omitted. |
Use this when someone asks how many units to order, given demand, lead time, stock on hand and on order, and supplier rules such as MOQ, case pack or a minimum order value. Sizes the line the way Forthcast sizes a purchase-order line and lists every rule that changed the quantity. Works without a connected store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lead_time_days | integer | yes | Supplier lead time in days. |
| on_hand | number | yes | Units available now. |
| on_order | number | no | Units already on open purchase orders. |
| service_level | number | no | Target in-stock probability, 0.50 to 0.99. |
| daily_demand | no | Daily units sold, oldest first, 14 to 365 values. | |
| average_daily_demand | no | Average units sold per day, if no daily history. | |
| demand_std_daily | no | Standard deviation of daily demand, if known. | |
| unit_cost | no | Purchase cost per unit. | |
| moq | no | Supplier minimum order quantity for this item. | |
| case_pack | no | Units per case; quantity is rounded up to whole cases. | |
| min_order_value | no | Supplier minimum order value in currency; needs unit_cost. | |
| cover_days_target | no | Optional explicit days of cover to buy instead of the default weeks-of-supply target. |
Use this when someone pastes past sales numbers and asks what to expect next month, next quarter or next season. Takes 3 to 365 monthly, weekly or daily totals (oldest first) and returns the next periods with an 80 percent range, the model used (Holt-Winters seasonal, damped trend, Croston for intermittent demand, or moving average) and why. Works without a connected store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sales | array | yes | Past sales totals per period, oldest first. |
| period | string | no | Granularity of the sales list. |
| horizon | integer | no | Periods to forecast: up to 12 monthly, 26 weekly, 90 daily. |
Use this when someone shares a list or CSV of products with stock and sales rates and asks which need reordering, which are overstocked, or how healthy the inventory is. Up to 500 rows. Applies Forthcast's urgency bands (Order now, Plan ahead, On track, Excess, No demand), reorder points, suggested quantities and inventory value. Works without a connected store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | Products to score. |
| default_lead_time_days | integer | no | Lead time for rows that give none. |
| service_level | number | no | Target in-stock probability, 0.50 to 0.99. |
Use this when someone asks what an inventory planning term means or how Forthcast calculates it: safety stock, reorder point, days of cover, urgency bands, service level, ABC class, EOQ, order quantity, fill rate, on-time rate, lead time, intermittent demand. Works without a connected store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | string | yes | Metric name, for example 'reorder point' or 'days of cover'. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Forthcast Inventory or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 3 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest3e52c6015802afa4ec2ef683a6082cad4de7f0807368858840db0e86c3f94109
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_inventory_overview | no tags | |
| get_reorder_recommendations | no tags | |
| find_inventory_items | no tags | |
| get_inventory_item | no tags | |
| list_purchase_orders | no tags | |
| get_supplier_performance | no tags | |
| calculate_reorder_point | no tags | |
| calculate_order_quantity | no tags | |
| forecast_demand_series | no tags | |
| score_inventory_health | no tags | |
| explain_inventory_metric | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3e52c6015802afa4
Scanned2026-11-03
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Forthcast Inventory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.