forecast-mcp (RohanSingh02/forecast-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 6 tools. No publisher has claimed this listing.

C
Emerging
74/100

forecast-mcp

Enables demand forecasting and replenishment recommendations using statistical models (Syntetos-Boylan classification, AutoETS, TSB) and provides tools for forecasting, evaluation, and order quantity calculation.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

RohanSingh02

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes6 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

list_skus

List every SKU/series id available in the loaded dataset.

classify_demand_pattern

Classify a SKU's demand pattern (Syntetos-Boylan: smooth / erratic / intermittent / lumpy / cold_start) and the model tier it routes to.

forecast_series

Forecast future demand for a SKU. Automatically classifies the series first and routes to the matching model: mean fallback for cold-start SKUs, TSB for intermittent demand, AutoETS for regular continuous demand.

evaluate_forecast

Backtest a SKU's forecast: hold out the last `test_size` days, forecast them from the remaining history, and score with MASE (scale-free, so it's comparable across SKUs with very different demand volumes).

recommend_replenishment

Recommend a reorder quantity for a SKU: forecasts demand, then applies a reorder-point / safety-stock formula against current on-hand stock.

explain_forecast

Return a plain-language explanation of why a SKU was routed to the model tier it was, for surfacing to a non-technical user.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configFORECAST_MCP_DATAexport =/path/to/demand.csv
configFORECAST_MCP_TRANSPORT
configFORECAST_MCP_HOST
configFORECAST_MCP_PORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

6/6 tools missing one or more hints — list_skus (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); classify_demand_pattern (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); forecast_series (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

4/6 tools referenced in tests (67%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/rohansingh02/forecast-mcp)](https://m8ven.ai/mcp/rohansingh02/forecast-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 53e8a877c7592bf5cd0cbb32a4dd26ddbe4fce45
code hash: be10b2abdb73625f1491a7bf0763495b7bd1bc7d0ff769cad1ff43d060945ec2
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client