mcp server
audit
Can an AI shopping agent find, understand and BUY on a store? Deterministic e-commerce audit /100.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Most recent push to the repository was 2026-08-02.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_merchant_readiness(host)- Check whether an AI shopping agent can find, understand and BUY on an e-commerce store: AgentReady's deterministic agent-readiness score /100 for a host, with grade, hard-block status (capped = agents are blocked at the door) and agent-protocol adoption (UCP, A2A, ARD). Scores exist for stores whose merchant ran a scan at agentready.market — this tool never triggers a new audit of a third-party site. Required: host.
get_readiness_report(host)- The latest public agent-readiness report for a scanned store: every check with its status (pass/partial/fail) across access & crawlability, structured data and catalog pillars, plus score, grade and report link. Same visibility as the public web report. Required: host.
list_agent_ready_stores(limit, vertical)- The Agent-Ready Index: e-commerce stores where an AI shopping agent can actually buy (grade B or better), ranked by agent-readiness score /100. Use it to route a purchase toward a store agents are known to succeed on, or to benchmark a store against its peers. Optionally filter by vertical and cap the number of rows.
Last successful function declaration observed on . Source: https://www.agentready.market/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.agentready.market/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-02 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-08-01 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.agentready.market | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | www.agentready.market |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json