Audit MCP Server

Audit MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Can an AI shopping agent find, understand and BUY on a store? Deterministic e-commerce audit /100.

What you get

Call check_merchant_readiness before attempting a purchase on any store — a "capped" store blocks agents at the door and the attempt will fail.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Audit is connected, these are the calls the assistant has available:

• REST — GET https://www.agentready.market/api/v1/scan?url= →
• Discovery — /.well-known/agent-card.json (A2A) ·

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the audit mcp server does with a few real requests.

Choosing this one

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Audit's toolset — REST, Discovery — is a fair guide to whether it matches your workflow. It is maintained by agentready-market; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Audit's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.