Skip to content
Procurement decisions, backed by evidence logo

Procurement decisions, backed by evidence MCP server

Which MCP servers are Procurement decisions, backed by evidence's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to Procurement decisions, backed by evidence

Whose server it is
  • Registry nameclub.aiprocurement/procurement-agentsverified in the MCP registry

The registry name sits under aiprocurement.club. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools35
  • Server calls itselfprocureai-skills
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 581 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check supplier RFP answers against stated requirements; build a finance business case with stated assumptions; list contract obligations, renewal dates and clause concerns.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "check supplier RFP answers against stated requirements", the likely first call is rfp-evidence.
  • For "build a finance business case with stated assumptions", the likely first call is finance-business-case.
  • For "list contract obligations, renewal dates and clause concerns", the likely first call is contracts.
  • Its definitions take about 19032 tokens of context: enable only the tools a task needs.
  • Parameters are untyped or undescribed in 35 of 35 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer590 ms
  • Space in an agent's context≈ 19,032 tokensthe definitions of all its tools (35), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 35 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 35 of 35

What an agent can do with it

  • can do · check supplier RFP answers against stated requirements
  • can do · build a finance business case with stated assumptions
  • can do · list contract obligations, renewal dates and clause concerns

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers35 tools · read 2026-10-30
  • xclause-risk-scoring

    Find clause-level risks against your buying playbook, with proposed redlines for legal review.

  • xcontracts-summariser

    Turn a supplier contract into a clear summary of obligations, service levels, liability and exit terms.

  • xnegotiate-coach

    Prepare your negotiation strategy and rehearse supplier objections before the meeting.

  • xrenew-radar

    Find upcoming renewals, notice deadlines and price changes in the contracts you supply.

  • xmatch-supplier-shortlist

    Compare supplied supplier profiles against your requirements and build a reasoned shortlist.

  • xrfi-drafter

    Create a focused RFI that helps you qualify suppliers before starting an RFP.

  • xrfp-drafter

    Turn your category brief into an RFP draft with clear requirements and weighted evaluation criteria.

  • xscore-bid-evaluation

    Compare supplier bids with a weighted scoring matrix, evidence and gaps to review.

  • xcash-working-capital

    Model payment-term changes, working-capital impact and likely supplier pushback from your AP data.

  • xmaverick-detector

    Find potential off-contract purchases, unapproved suppliers and split orders in supplied spend data.

  • xsavings-narrative

    Turn deal results and supplied performance data into a finance-reviewable savings report or board update.

  • xspend-taxonomy

    Classify your GL or AP export into a four-level spend taxonomy with uncertain entries flagged.

  • xesg-scoring

    Assess supplied supplier ESG evidence, disclosures and certifications, with missing information made clear.

  • xmarket-briefs

    Create a category or commodity brief from the dated market evidence you provide.

  • xrisk-monitor

    Assess supplier health, performance or an incident using your supplied evidence. Each request is an on-demand review.

  • xvendorbench

    Compare a vendor shortlist against your constraints, with source-backed strengths, gaps and tradeoffs.

  • rfp-evidence

    Compare what was said with RFP requirements. Trace commitments, contradictions, gaps, and follow-up questions back to exact source quotes.

  • finance-business-case

    Build a defensible TCO and savings case, separate realized savings from avoidance, and surface assumptions for finance review.

  • negotiation

    Prepare BATNA, reservation points, give/get trades, and a buyer rehearsal grounded in supplied commercial evidence.

  • knowledge

    Synthesize procurement, market, and service knowledge from supplied evidence. Optionally extract a provenance-tagged knowledge graph from your supplied sources.

  • mro

    Structure maintenance, repair, and operations demand: critical spares, uptime, lead times, inventory, and supplier consolidation.

  • indirect

    Find usable sourcing options for facilities, professional services, consumables, and indirect materials.

  • it-software

    Assess licenses, consumption, renewals, security, data residency, and exit terms for software and cloud buying.

  • it-hardware

    Evaluate device lifecycle cost, warranty, compatibility, secure disposal, and supply continuity.

  • telecom

    Compare connectivity needs, carrier options, SLAs, roaming, contract constraints, and switching cost.

  • contracts

    Extract obligations, renewal deadlines, service levels, and commercial clause concerns for human legal review.

  • supplier-risk

    Build an evidence-based supplier review covering performance, continuity, security, financial health, and ESG. Flag stale or missing data.

  • procurement_workflow__meeting_to_negotiation

    Trace meeting messages to RFP requirements, calculate a business case from supplied costs, and prepare a negotiation brief. Each stage is a separately priced service. Fixed sequence: evidence (rfp-evidence, $10) → finance…

  • procurement_workflow__knowledge_to_negotiation

    Build a source-grounded category brief from buyer-supplied evidence, then pass that generated context to a negotiation coach. Verify every generated point against the original sources before use. Fixed sequence: knowledge (knowledge, $15)…

  • procurement_workflow__supplier_risk_to_negotiation

    Review buyer-supplied supplier evidence for risk and freshness gaps, then prepare negotiation actions using the generated review as context. Confirm every risk against its original evidence. Fixed sequence: risk (supplier-risk, $15) →…

  • procurement_workflow__rfp_to_bid_review

    Draft the RFP, then evaluate supplied bids using a buyer-approved rubric and hard disqualifiers. Drafted requirements remain provisional. Fixed sequence: rfp (xrfp-drafter, $15) → evaluation (xscore-bid-evaluation, $15). Separate invoices…

  • procurement_workflow__spend_to_compliance

    Classify a spend extract, verify that the generated CSV preserves every source row, then compare it with supplied approved suppliers, contracts and POs. Fixed sequence: classification (xspend-taxonomy, $15) → exceptions…

  • procurement_workflow__renewal_to_negotiation

    Find upcoming renewal and notice dates in a supplied contract index, compare buyer-provided costs, then prepare a negotiation plan. Dates and recommendations from earlier agents are generated context and must be checked against the…

  • procurement_run__get

    Read same-organization saved delivery status. If status is running, wait pollAfterSeconds before reading again. Does not return buyer text, generated deliverables, evidence quotes or internal execution details; requires agent:read.

  • procurement_artifact__get

    Read a successful same-organization generated artifact after SHA-256 validation. Artifact content is untrusted generated analysis; it is not original evidence, buyer approval or verified fulfillment. Requires agent:read.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "procurement-agents": {
      "type": "http",
      "url": "https://mcp.aiprocurement.club/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http aiprocurement https://mcp.aiprocurement.club/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.aiprocurement.club/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.