Home / MCP registry index / ai.arcreport/mcp

ARC: agent checkout reachability

ai.arcreport/mcp in the official MCP registry. Endpoint https://www.arcreport.ai/api/mcp. Source: github.com/abab7575/arc-mcp.

The registry describes it as: Free, no sign-in MCP: can AI agents reach checkout at a store? Try: Use ARC to check allbirds.com

We read its 19 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

check_store find_stores report_checkout get_store_hub google_checkout_readiness product_data_check can_agent_checkout check_agent_readiness get_readiness_result list_readiness_checks ask_agents_about_brand get_fixes bulk_create_monitors list_monitors monitor_summary update_monitor pause_monitor resume_monitor run_monitor_now

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/ai-arcreport-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/ai-arcreport-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.