eCommerce
buyrecord.app
An MCP server for e-commerce product and merchant research, enabling product searches, outcome comparisons, merchant reputation checks, and purchase outcome submissions.
ENDPOINT 1
https://api.buyrecord.app/mcp
MCP server metadata
- Name
- BuyRecord
Known tools 5
search_productsProducts matching a name, GTIN or SKU: verified outcome summary, plus price, availability, rating and return policy as published on the merchant's site (labelled not verified).
Inferred read-onlyget_product_outcomesScore, sample size, outcome breakdown and top return reasons for one product.
Inferred read-onlyget_merchant_profileReturn rate, complaint rate and delivery issue rate across a merchant's products.
Inferred read-onlysubmit_outcomeRecord a purchase outcome for a product (product_id or product_url).
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.buyrecord]
url = "https://api.buyrecord.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"buyrecord": {
"type": "http",
"url": "https://api.buyrecord.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: buyrecord
Remote MCP URL: https://api.buyrecord.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"buyrecord": {
"url": "https://api.buyrecord.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"buyrecord": {
"type": "http",
"url": "https://api.buyrecord.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "buyrecord",
"transport": "streamable-http",
"url": "https://api.buyrecord.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.