oddly commerce corpus

The world, on the record. AI infrastructure built on the observed web.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
77%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~439Tokens (tool definitions)
~742 BTypical response size
Minimal attention impact (0.34% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "oddly-corpus": {
      "url": "https://myoddly.com/api/public/mcp"
    }
  }
}

Remote endpoints

https://myoddly.com/api/public/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢benchmark_categories

List the product categories the oddly corpus currently covers, with how many observations and metrics back each one. Call this FIRST to discover valid category paths before calling benchmark_lookup, rather than guessing a path.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
⚪benchmark_lookup(category, metric, market)

Observed price and assortment benchmarks for a product category: the median and the p25-p75 band across real public storefront listings, with the sample size, the currency, and the exact scope of each figure. Figures are observed market reference, not targets or advice. Returns an honest empty answer when a category has too little data to serve; it never estimates or fills a gap. This corpus does NOT hold conversion rates, revenue, or AOV, so do not ask it for those.

Input Schema

{
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Category path, e.g. 'commerce/baby/clothing'. Use benchmark_categories to list valid paths."
    },
    "metric": {
      "type": "string",
      "description": "Optional metric filter, e.g. 'price.romper'. Omit to get every servable metric for the category."
    },
    "market": {
      "type": "string",
      "description": "Optional ISO 3166-1 alpha-2 market filter, e.g. 'NZ', 'US'. Omit for the all-markets aggregate."
    }
  },
  "required": [
    "category"
  ],
  "additionalProperties": false
}
⚪store_audit(url)

Run oddly's free storefront audit against a public ecommerce domain and return the findings: detected platform, the checks that failed, and how the store's catalogue compares to observed category norms where the corpus can say. Reads the store's own public pages only, obeys robots.txt, and is rate limited. Use the bare domain (example.com). Never pass an internal host or an IP address.

Input Schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The storefront domain or URL to audit, e.g. 'example.com'."
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools