eCommerce
dataenrich.dev
Tracks coffee roaster stores and product catalogs, including pricing, availability, bag sizes, and change events.
ENDPOINT 1
https://api.dataenrich.dev/mcp
MCP server metadata
- Name
- coffee-roaster-data
Specialty coffee roaster prices, stock, price per 100g, change events and store profiles. Preview results are capped; use the x402 REST API for full data.
Known tools 4
search_productsSearch coffee products (one record per product+bag size) by store domain, availability and text query.
Inferred read-onlyget_changesChange events (new_product, price_change, on_sale, restock, sold_out, removed) since an ISO timestamp.
Inferred read-onlylist_storesList tracked roaster stores with currency, product count and in-stock share.
Inferred read-onlystore_profileStore profile for a roaster domain: catalog size, price bands, price/100g quartiles, bag sizes, launch cadence.
Inferred read-onlyCONNECT 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.coffee-roaster-data]
url = "https://api.dataenrich.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"coffee-roaster-data": {
"type": "http",
"url": "https://api.dataenrich.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: coffee-roaster-data
Remote MCP URL: https://api.dataenrich.dev/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": {
"coffee-roaster-data": {
"url": "https://api.dataenrich.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"coffee-roaster-data": {
"type": "http",
"url": "https://api.dataenrich.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "coffee-roaster-data",
"transport": "streamable-http",
"url": "https://api.dataenrich.dev/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.