Brave Search MCP Server: web results, images, videos, rich results, AI summaries, and more.
oddly commerce corpus is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
The world, on the record. AI infrastructure built on the observed web.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http oddly-commerce-corpus-mcp https://myoddly.com/api/public/mcp
# 2 — ask your agent for something these tools do
# record_subject_history, record_verify_receipt, record_answer and 3 more
oddly commerce corpus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http oddly-commerce-corpus-mcp https://myoddly.com/api/public/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version 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 true) and fetched_at (when oddly looked), and the receipt hash of each row so any value can be checked with record_verify_receipt. Rate: meter data.history, US$0, attribution required (cite oddly and the subject). Returns an honest empty answer for a subject t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject_key | string | yes | The subject key exactly as the record prints it on /record/subject?key=..., e.g. 'benchmark-cell:commerce/baby/clothing|SG|*|local|*|*'. |
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, the day root its day folds into, and that root's anchor state (confirmed with a block height, or pending). Every check is named in the verdict, and a check that could not run says so rather than passing. Rate: never metered (verification is on the price book's
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt_hash | string | yes | The 64-character hex receipt hash, as printed on a receipt or returned by the other record tools. |
Answer one question from oddly's record: the newest observed value of one attribute of one subject, with its figure, both clocks, its source, its receipt and its scope. The figure is what the source published when oddly looked, not an estimate, a forecast or advice. Rate: meter data.answer, US$0.001 per answer, first 100 per month free. An unanswered question (a subject or attribute the record has
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject_key | string | yes | The subject key exactly as the record prints it on /record/subject?key=..., e.g. 'benchmark-cell:commerce/baby/clothing|SG|*|local|*|*'. |
| attribute | string | yes | The attribute to answer, exactly as record_subject_history lists it. |
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.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | Category path, e.g. 'commerce/baby/clothing'. Use benchmark_categories to list valid paths. |
| metric | string | no | Optional metric filter, e.g. 'price.romper'. Omit to get every servable metric for the category. |
| market | string | no | Optional ISO 3166-1 alpha-2 market filter, e.g. 'NZ', 'US'. Omit for the all-markets aggregate. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The storefront domain or URL to audit, e.g. 'example.com'. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install oddly commerce corpus or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish oddly commerce corpus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.