MCP.Market

Purchaseiq MCP server

online · 100% uptime
by purchaseiq.io·io.purchaseiq/mcp·v0.1.0
No reviews yet

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

B76/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B76/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Purchaseiq yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Purchaseiq tools (1, 1 write)

write = sends, deletes, buys or posts
  • analyze_purchasewrite actionFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 916ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenancelast push 55 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 76/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Purchaseiq compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
76/100
higher than 48% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
100%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
467 ms
faster than 32% of 30,031 servers

What its tools let an agent do: 1 change

Install Purchaseiq in Claude Code, Cursor or VS Code

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

What the publisher says

From the Purchaseiq repository's README, as published. We do not edit it. Read it on GitHub

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 clinemcpsettings.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 / claudedesktopconfig.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:

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 to the same endpoint — no daily limit. Get a key at purchaseiq.io/mcp.

Links

  • Docs: https://purchaseiq.io/mcp
  • Website: https://purchaseiq.io
  • Contact: contact@purchaseiq.io

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.

Nothing above is checked by us. What we check is on the safety report.

Purchaseiq: common questions

Is Purchaseiq MCP server safe?
Mostly: it is graded B (76/100). Read the Purchaseiq safety report
How do I install Purchaseiq?
It runs remotely at purchaseiq.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Purchaseiq need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Purchaseiq maintained?
The last commit was 93 days ago (2026-08-03). The latest release is v0.1.0.
Is Purchaseiq up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Purchaseiq compare with other MCP servers?
safety score 76/100 (higher than 48% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.