Authorization required for paid tools and saved results. The generated No Auth Quick Start covers discovery only. Use the authenticated example below.

Procurement reports hosted by AIProcurement.club

Connect to https://mcp.aiprocurement.club/mcp for 27 procurement specialists, six fixed workflows and two saved-result recovery tools. Specialists cover contracts, RFP evidence, negotiation, supplier risk, spend, finance and procurement categories.

Access and payment

This is a direct connection to AIProcurement.club. The MCPize catalog listing has no subscription charge; underlying service execution is paid directly to AIProcurement.club, from $10 per job, subject to provider availability. Use your own buyer-scoped AIProcurement API key in the AUTHORIZATION header as Bearer YOUR_KEY. Each workflow stage requires its own valid prepaid service invoice. Check the current catalogue and checkout before execution.

Calling a tool

Provide the required evidence inputs, explicitly set consentExternalProcessing to true, and keep one stable idempotencyKey for the same logical operation. Supply the applicable paymentInvoiceId. Retrying the same operation must reuse its original key.

Successful calls return a structured report, evidence findings, next actions and a saved artifact with a SHA-256 digest. Use procurement_run__get for saved status and procurement_artifact__get to recover the report using the same organization.

Evidence and review

Reports are generated and require human review. A matching source quotation establishes occurrence in the supplied material, not independent verification of a claim. The tools do not contact suppliers, transfer money or purchase invoices.

Authenticated Node.js connection

The autogenerated Quick Start says No Auth because discovery is public. Paid calls and saved-result reads require your own AIProcurement key. Use this authenticated example instead. Never share a merchant-wide key with a marketplace.

Create a private client folder with this package.json, run npm install, then save the example as client.mjs:

{"private":true,"type":"module","dependencies":{"@modelcontextprotocol/sdk":"1.32.1"},"overrides":{"@hono/node-server":"2.1.3"}}

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const key = process.env.AIPROCUREMENT_API_KEY;
if (!key) throw new Error("Set your own scoped AIPROCUREMENT_API_KEY");
const client = new Client({ name: "procurement-buyer", version: "1.0.0" });
try {
  await client.connect(new StreamableHTTPClientTransport(
    new URL("https://mcp.aiprocurement.club/mcp"),
    { requestInit: { headers: { Authorization: "Bearer " + key } } }
  ));
  console.log((await client.listTools()).tools.map(tool => tool.name));
  const runId = process.env.AIPROCUREMENT_RUN_ID;
  if (runId) {
    console.log(await client.callTool({
      name: "procurement_run__get", arguments: { runId }
    }));
  }
} finally { await client.close(); }

Set the API-key environment variable locally without committing it, then run node client.mjs. Listing tools creates no paid job. For a paid invocation, inspect the selected tool inputSchema and supply its evidence, external-processing consent, stable idempotency key and applicable prepaid invoice. Saved-result reads need agent:read; execution also needs agent:invoke. An unknown run or another organization cannot be read.

The official SDK was checked against all 27 successful specialist runs. Paid checkout, settlement and positive multi-stage workflow execution still require a funded pilot.