MCP.Market

P2Predict MCP server

by ahmed-khalil-hafsi·io.github.ahmed-khalil-hafsi/p2predict·v1.1.0·2 stars

Local MCP server for parametric price benchmarking in procurement and engineering.

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed P2Predict yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

P2Predict tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How P2Predict compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 33% of 48,243 servers
GitHub stars
2
more than 75% of 28,706 servers

Install P2Predict in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the P2Predict repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.ahmed-khalil-hafsi/p2predict -->

The right price is already in your data.

P2Predict turns your purchasing history into a price model your team can talk to. Ask what a part should cost, why, and how sure the answer is, in plain language, through the AI agent you already use.

&nbsp; &nbsp; &nbsp;

&nbsp;

Set up in one command:

pip install "p2predict[mcp]"

Built for procurement and engineering teams in automotive, semiconductors, electronics, industrials, pharma, and chemicals.

The problem

Most of what a part costs is decided upstream, in a design review procurement never sees. An engineer tightens a tolerance beyond what the application needs, or locks the part to a single supplier, and the cost rides downstream with no number attached. By the time the BOM reaches procurement, the expensive decisions are frozen and all that is left to negotiate is the rounding.

Then the quote arrives. The supplier knows their cost to the cent; you have last year's PO and a few days to respond. Multiply that across every line you buy and the leaks look the same everywhere: premiums no one benchmarked, specs no one costed, a number you cannot defend when finance asks where the savings went.

The answers are already in your purchase history. Nobody has had the time to dig them out.

What P2Predict does

P2Predict learns from your own purchasing data what drives the price of a part: supplier, material, size, spec, region. Then it gives your team a defensible target for any new or proposed part. Your category managers ask in plain English. The answer comes back grounded in what you have actually paid.

It runs on your machine, on your data, through any AI agent your team already uses. Nothing is uploaded. No vendor catalog, no cloud, no per-seat data-sharing.

What it is, and what it isn't

P2Predict is parametric price prediction. It learns the fundamental pricing structure in your historical buying data and benchmarks any part against it, the ones you are about to buy and the ones you already do. Being precise about that is the whole point, so here is the honest scope.

What it does

  • Learns from the prices you have actually paid and predicts what a similar part should cost.
  • Attributes that predicted price to each spec and to the supplier, so you can see what is moving the number.
  • Puts a calibrated likely-range on every estimate and flags where the data is too thin to trust.
  • Improves as you give it more of your own purchase history.

What it does not do

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

P2Predict: common questions

Is P2Predict MCP server safe?
Mostly: it is graded B (70/100). Read the P2Predict safety report
Does P2Predict need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is P2Predict maintained?
The last commit was 41 days ago (2026-09-25). The latest release is v1.1.0.
How does P2Predict compare with other MCP servers?
safety score 70/100 (higher than 33% of 48,243 servers); github stars 2 (more than 75% of 28,706 servers). Full comparison.