Skip to content

Grok GAIP Procurement Evidence Agent gaip_verify_supplier_claims

How to: Grok GAIP Procurement Evidence Agent gaip_verify_supplier_claims

client:Grok transport:streamable-http tool:gaip_verify_supplier_claims

Add GAIP Procurement Evidence Agent to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "gaip-procurement-verify": {
      "type": "http",
      "url": "https://www.gaipagents.com/mcp/agents/procurement-verify"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something gaip_verify_supplier_claims does. Grok lists the server's tools on connect and calls gaip_verify_supplier_claims itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that GAIP Procurement Evidence Agent's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 4 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.