Purchaseiq

io.purchaseiqPublished by purchaseiq.ioOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Hosted PurchaseIQ server that lets an assistant run a pre-purchase trust check on a product, seller or store URL and get a proceed/caution/avoid verdict.

What you can do
  • Assess a product, seller, company or purchase URL for trust and safety
  • Return a verdict (proceed, caution or avoid), a 0-100 trust score, up to three top risk flags and a one-line reason
  • Accept a URL, company name, product name or description, barcode (EAN/GTIN/UPC) and country code, all optional with at least one required
  • Draw on product recall records and scam, phishing and seller-credibility signals from public sources
When to use it
Useful when an assistant is helping someone evaluate an unfamiliar online store, seller or product before checkout and needs a quick risk signal. It is informational only, so it suits a sanity check rather than a final decision.
Requirements
Remote streamable HTTP endpoint; nothing to install or run locally. Clients must use POST-based streamable HTTP (Cline needs the type field set to streamableHttp). No account is needed for the free tier of 10 trust checks per day per IP; an API key sent as an Authorization Bearer header removes the daily limit.
Before you install
The free tier is capped at 10 checks per day per IP, and an API key is a credential to keep private. The inputs (URLs, seller names, product details) are sent to a third-party service. Verdicts are automated and informational, not financial, legal or purchasing advice, and a proceed verdict is not an endorsement, so results should be verified independently.

Installation

In SourceWeft

  1. Open Purchaseiq in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.purchaseiq%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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

bash
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.

json
{  "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):

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:

json
{  "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.

Links

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.

Source: README.md at commit db487d4

Tools

1

analyze_purchase

Assess trust and safety of a product, seller, or purchase URL. Returns a verdict (proceed/caution/avoid), trust score 0-100, top risk flags, and a one-line reason. Informational only, not advice — see purchaseiq.io/terms.

Parametersurlbarcodecompanycountryproduct

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts