issafe.store

Check a store before you buy

Paste any store URL for a risk score, cited evidence, and a clear recommendation — no account required.

How We Check a Store

We combine public data sources with AI analysis to produce a risk assessment you can act on — no account or purchase history needed.

Domain Age & History

We check when the domain was registered and whether ownership changed hands — newly registered or frequently transferred domains are a common scam store signal.

RDAP Registration Data

Public RDAP records reveal the domain's registration date and active status. Very recent registrations are a known warning sign for disposable storefronts.

Review Platform Signals

We aggregate public complaint and review data from Trustpilot, BBB, ScamAdviser, Reddit, and other platforms to surface patterns of non-delivery, fraud, or disputes.

Blocklist & Fraud Databases

We cross-reference the store URL against publicly maintained fraud blocklists, phishing databases, and community scam registries.

SSL & Technical Signals

We verify the SSL certificate's presence, validity, and issuing authority. Self-signed or recently-issued certificates on new domains raise the risk score.

AI-Powered Synthesis

An AI model weighs all collected signals, resolves conflicts between sources, and produces a calibrated risk score, confidence rating, and plain-language recommendation.

Note: We rely only on publicly available signals — no private merchant data, payment records, or order history. This is a best-effort public-signal assessment and should not be your sole basis for any financial decision.

Use IsSafe.store from your AI client

Connect the public MCP endpoint so Cursor, Claude, or other agents can check a store URL and read the compact risk report.

MCP endpoint

https://issafe.store/mcp

Add to Cursor

Or paste one of the configs below.

Cursor

{
  "mcpServers": {
    "issafe-store": {
      "url": "https://issafe.store/mcp"
    }
  }
}

Claude Desktop

{
  "mcpServers": {
    "issafe-store": {
      "command": "npx",
      "args": ["mcp-remote", "https://issafe.store/mcp"]
    }
  }
}

Claude Code

claude mcp add --transport http issafe-store https://issafe.store/mcp

Note: The MCP tools share the same public-signal checks and daily limits as the website. Results are a risk assessment, not a purchase guarantee.

Common Store Safety Questions

A quick check helps reduce uncertainty. Use it alongside your normal payment, refund, and merchant verification habits.

Can IsSafe.store guarantee a store is safe?

No. IsSafe.store is a public-signal risk assessment. It surfaces warning signs and reputation evidence, but cannot guarantee merchant behavior, delivery, refunds, or payment safety.

What signals does the store checker use?

The checker reviews domain registration data, site accessibility, SSL status, policy and contact signals, public reputation results, and known fraud or phishing indicators.

Do I need an account or purchase data?

No. Just paste a store URL — no account needed. We never access private purchase, payment, or order history.

Can an AI client use IsSafe.store?

Yes. Connect the public MCP endpoint at https://issafe.store/mcp from Cursor, Claude Desktop, Claude Code, or any MCP-compatible client. The check_store and get_report tools share the same public-signal checks and daily limits as the website.