io.purchaseiq/mcp

Official registry AI and agents

Pre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http io-purchaseiq-mcp 'https://purchaseiq.io/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "io-purchaseiq-mcp": {
            "type": "http",
            "url": "https://purchaseiq.io/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. PurchaseIQ MCP Server
  2. Endpoint
  3. Connect
  4. The tool: analyze_purchase
  5. Limits & API keys
  6. Links
  7. Disclaimer
  8. License

PurchaseIQ MCP Server

Pre-purchase trust intelligence for AI agents. One tool call before checkout: product recalls (46,000+ records across US/EU/CA/FR), seller credibility, scam and phishing signals, and an AI trust verdict, aggregated from 15+ verified sources.

This repository hosts the MCP Registry manifest for the hosted PurchaseIQ server. The server itself is remote — there is nothing to install or run.

Endpoint

https://purchaseiq.io/api/mcp

Transport: Streamable HTTP (stateless JSON-RPC over POST). Registry name: io.purchaseiq/mcp.

Connect

Claude Code

claude mcp add --transport http purchaseiq https://purchaseiq.io/api/mcp

Cline (VS Code) — add to cline_mcp_settings.json (Cline panel → MCP Servers → Configure MCP Servers). The "type" field is required: without it Cline defaults to the legacy SSE transport, and this server is POST-only streamable HTTP, so the connection fails with a 405.

{
  "mcpServers": {
    "purchaseiq": {
      "type": "streamableHttp",
      "url": "https://purchaseiq.io/api/mcp"
    }
  }
}

Then reload the window (Command Palette → Developer: Reload Window). Step-by-step agent instructions: llms-install.md.

Cursor, Claude Desktop & other MCP clients — add to your MCP config (mcp.json / claude_desktop_config.json):

{
  "mcpServers": {
    "purchaseiq": {
      "url": "https://purchaseiq.io/api/mcp"
    }
  }
}

Claude.ai — Settings → Connectors → Add custom connector → paste the endpoint URL.

ChatGPT — Settings → Connectors → Create (developer mode) → paste the endpoint URL.

The tool: analyze_purchase

Pass whatever the agent has — all inputs optional, at least one required:

InputDescription
urlProduct or store URL
companySeller or company name
productProduct name or description
barcodeEAN, GTIN, or UPC barcode
countryISO country code (default: US)

Response is a compact agent verdict:

{
  "verdict": "caution",
  "score": 55,
  "topFlags": [
    "Domain registered 3 months ago",
    "No company registration found",
    "SSL valid, TLS 1.3"
  ],
  "reason": "Very new domain with no verifiable company behind it."
}

verdict is proceed, caution, or avoid. score is 0–100. topFlags lists up to three highest-priority signals, dangers first.

Limits & API keys

  • Free tier: 10 trust checks (tools/call) per day per IP. Protocol handshakes (initialize, tools/list) are always free.
  • API key: send Authorization: Bearer <key> to the same endpoint — no daily limit. Get a key at purchaseiq.io/mcp.

Disclaimer

PurchaseIQ provides automated, informational risk signals derived from public data sources. Output is not financial, legal, or purchasing advice, and a "proceed" verdict is not an endorsement or guarantee. Verify independently before acting. Full terms: https://purchaseiq.io/terms

License

Documentation in this repository is MIT licensed — see LICENSE.

Frequently asked questions

What is io.purchaseiq/mcp?

Pre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict.

How do I install io.purchaseiq/mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http io-purchaseiq-mcp 'https://purchaseiq.io/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.purchaseiq/mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.purchaseiq/mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.purchaseiq/mcp?

It is published by mrgoodie. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.