_ registry / mcp streamable-http · checked 1m ago

oddly

https://myoddly.com

Registry code: 76cbc02c5f5ee639

api record

oddly is the world, on the record. The record_* tools read the record: a subject's history with both clocks (when the source says it was true and when oddly looked), one question answered with its receipt, and any receipt verified end to end. The benchmark_* and store_audit tools read the observed commerce corpus: real listing prices and assortment shape crawled from public storefronts, aggregated by category and market. Every figure is a MARKET REFERENCE with its sample size and scope attached, never a target, a forecast, or advice. Quote the scope with the number. The corpus holds observed…

endpoint
https://myoddly.com/api/public/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is oddly live?
Yes — it answered the hub's last check (checked 1m ago). It answered 100% of checks over the last 30 days.
Is oddly free to use?
Yes — the hub reached it with no key and no payment.
What tools does oddly have?
6 tools: record_answer, benchmark_lookup, record_verify_receipt, record_subject_history, store_audit, benchmark_categories.
Is oddly safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
581ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 143 checks · signed record
  • degraded → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • benchmark_categories open 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • record_answer unknown 7h ago

    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 not observed) is never metered.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subject_key",
        "attribute"
      ],
      "properties": {
        "attribute": {
          "type": "string",
          "description": "The attribute to answer, exactly as record_subject_history lists it."
        },
        "subject_key": {
          "type": "string",
          "description": "The subject key exactly as the record prints it on /record/subject?key=..., e.g. 'benchmark-cell:commerce/baby/clothing|SG|*|local|*|*'."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • benchmark_lookup unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "market": {
          "type": "string",
          "description": "Optional ISO 3166-1 alpha-2 market filter, e.g. 'NZ', 'US'. Omit for the all-markets aggregate."
        },
        "metric": {
          "type": "string",
          "description": "Optional metric filter, e.g. 'price.romper'. Omit to get every servable metric for the category."
        },
        "category": {
          "type": "string",
          "description": "Category path, e.g. 'commerce/baby/clothing'. Use benchmark_categories to list valid paths."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • record_verify_receipt unknown 7h ago

    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 never_metered list).

    mcp-tool

    {
      "type": "object",
      "required": [
        "receipt_hash"
      ],
      "properties": {
        "receipt_hash": {
          "type": "string",
          "description": "The 64-character hex receipt hash, as printed on a receipt or returned by the other record tools."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • record_subject_history unknown 14h ago

    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 the record has never observed, which is never metered.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subject_key"
      ],
      "properties": {
        "subject_key": {
          "type": "string",
          "description": "The subject key exactly as the record prints it on /record/subject?key=..., e.g. 'benchmark-cell:commerce/baby/clothing|SG|*|local|*|*'."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • store_audit unknown 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The storefront domain or URL to audit, e.g. 'example.com'."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 76cbc02c5f5ee639.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/76cbc02c5f5ee639/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/76cbc02c5f5ee639/badge.svg)](https://brick.blue/agent/76cbc02c5f5ee639?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.