Is the Arcreport MCP server down?

mcp-registry/ai.arcreport/mcp · v2.1.0

down
Last checked 2026-10-24 16:42 UTC · handshake 59ms

As of 2026-10-24 16:42 UTC, the Arcreport MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 49.9 hours.

uptime (30d checks)
98.8%
checks observed
1,879
outages (90d)
2
tools
19

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

Point your MCP client at this streamable-http endpoint: https://www.arcreport.ai/api/mcp

Agent-readiness: D (69/100)

D (69/100): 1 error(s), 3 warning(s) across 19 tool(s); ~3,273 tokens of tool definitions.
Scores higher than 4% of 15,665 MCP servers Glimind has audited.
Its tool list costs an agent ~3,273 tokens per session — more than 55% of servers.
70 → 79 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions79
Safety hints19
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (6)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

5 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_store_hub, product_data_check, update_monitor

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: bulk_create_monitors, run_monitor_now, update_monitor

Reachable 98.8% of the time over the last 30 days; median recovery 2994 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

13 of 19 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: ask_agents_about_brand, bulk_create_monitors, check_agent_readiness, get_fixes, get_readiness_result and 8 more

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.arcreport%2Fmcp/fixes

bulk_create_monitors 1 change
{
  "name": "bulk_create_monitors",
  "description": "[Requires sign-in] Set up scheduled monitoring for one or more store URLs (the 'set up monitoring' flow). Validates each URL and rejects invalid/private/internal ones. GUIDED FLOW: first ask the user for the URLs (paste a list or a CSV), then the frequency (daily/weekly/monthly, default weekly). Every plan runs the core panel of personal shopping agents — no picking needed. Call once without confirmed=true to preview the exact setup and scan-credit estimate, read that summary to the user, and on",
  "inputSchema": {
    "type": "object",
    "required": [
      "urls"
    ],
    "properties": {
      "urls": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Store/product URLs to monitor (a list or pasted CSV lines)."
      },
      "depth": {
        "enum": [
          "cart",
          "checkout"
        ],
        "type": "string",
        "description": "How far each scan goes. Default: cart."
      },
      "confirmed": {
        "type": "boolean",
        "description": "Must be true only after the user has confirmed the summarized setup. If missing or false, ARC returns a preview and creates nothing."
      },
      "frequency": {
        "enum": [
          "daily",
          "weekly",
          "monthly"
        ],
        "type": "string",
        "description": "How often to re-test. Default: weekly."
      }
    }
  },
  "annotations": {
    "requiresSignIn": true,
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
check_agent_readiness 1 change
{
  "name": "check_agent_readiness",
  "description": "[Requires sign-in] Check whether personal AI agents can reach a product URL, understand it, and reach checkout. Runs ARC's readiness check: crawler access, whether an agent can answer a shopper's questions from the page, and personal shopping agents trying to add to cart or reach checkout. Returns a check id — poll get_readiness_result (about 30–60 seconds). This does not ask what agents think of the brand; use ask_agents_about_brand for that.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The product or store URL to test, e.g. https://store.com/products/best-seller"
      },
      "task": {
        "type": "string",
        "description": "Optional goal, e.g. 'add to cart' (default) or 'reach checkout'."
      }
    }
  },
  "annotations": {
    "requiresSignIn": true,
    "readOnlyHint": true
  }
}
get_fixes 1 change
{
  "name": "get_fixes",
  "description": "[Requires sign-in] Concrete next steps to get recommended by personal agents and to become reachable, understandable, and buyable. Pass a readiness check id and/or the brand, category, store URL, and competitors that were recommended instead. Uses the check's evidence when an id is given. Does not start a new check.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "brand": {
        "type": "string",
        "description": "Brand name, if you want recommendation steps."
      },
      "scan_id": {
        "type": "string",
        "description": "Optional readiness check id from check_agent_readiness."
      },
      "category": {
        "type": "string",
        "description": "Product category, e.g. running shoes."
      },
      "mentioned": {
        "type": "boolean",
        "description": "Whether any benchmark persona mentioned the brand."
      },
      "store_url": {
        "type": "string",
        "description": "Store URL."
      },
      "recommended": {
        "type": "boolean",
        "description": "Whether any benchmark persona recommended the brand for the category."
      },
      "competitors_recommended": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Competitors personal agents recommended instead."
      }
    }
  },
  "annotations": {
    "requiresSignIn": true,
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.arcreport/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.arcreport/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.arcreport%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fai.arcreport%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.arcreport%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.arcreport%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.arcreport%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.arcreport%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0e69fe5595257943…, first seen 2026-10-17, included at leaf 18049 of 62,680. Version history · verify what your client received.

Working alternatives

Tools (19)

Compare: most reliable ml servers · most reliable devops servers · most reliable web servers · most reliable search servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Arcreport MCP server down right now?

As of 2026-10-24 16:42 UTC, the Arcreport MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 49.9 hours.

How many tools does Arcreport MCP server provide?

Arcreport MCP server advertises 19 tools, including ask_agents_about_brand, bulk_create_monitors, can_agent_checkout, check_agent_readiness, check_store.

How do I install Arcreport MCP server?

Point your MCP client at this streamable-http endpoint: https://www.arcreport.ai/api/mcp

Is the Arcreport MCP server safe to connect to an AI agent?

Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Arcreport MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve