Categories › Web & Browser › Web search engines & search APIs
The world, on the record. AI infrastructure built on the observed web.
Remote server: your requests and data go to myoddly.com. Claude Code: claude mcp add --transport http oddly https://myoddly.com/api/public/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
record_subject_history — One subject's change history and current state from oddly's record, with both clocks on every row: observed_at (when the source says it was record_verify_receipt — Recompute and check one receipt end to end: the row's receipt hash recomputed from its own sealed document, the link to the row before it, trecord_answer — Answer one question from oddly's record: the newest observed value of one attribute of one subject, with its figure, both clocks, its sourcebenchmark_categories — List the product categories the oddly corpus currently covers, with how many observations and metrics back each one. Call this FIRST to discbenchmark_lookup — Observed price and assortment benchmarks for a product category: the median and the p25-p75 band across real public storefront listings, witstore_audit — Run oddly's free storefront audit against a public ecommerce domain and return the findings: detected platform, the checks that failed, and Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.