com.myoddly/oddly-corpus

Est-ce que com.myoddly/oddly-corpus est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.myoddly/oddly-corpus » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 6 outils

• benchmark_categories≈ 124 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "benchmark_categories", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• benchmark_lookup≈ 304 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • market · string · optionnel
    Optional ISO 3166-1 alpha-2 market filter, e.g. 'NZ', 'US'. Omit for the all-markets aggregate.
  • metric · string · optionnel
    Optional metric filter, e.g. 'price.romper'. Omit to get every servable metric for the category.
  • category · string · requis
    Category path, e.g. 'commerce/baby/clothing'. Use benchmark_categories to list valid paths.

  Exemple d'appel

  {"name": "benchmark_lookup", "arguments": {"category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• record_answer≈ 268 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • attribute · string · requis
    The attribute to answer, exactly as record_subject_history lists it.
  • subject_key · string · requis
    The subject key exactly as the record prints it on /record/subject?key=..., e.g. 'benchmark-cell:commerce/baby/clothing|SG|*|local|*|*'.

  Exemple d'appel

  {"name": "record_answer", "arguments": {"attribute": "texte", "subject_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• record_subject_history≈ 240 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • subject_key · string · requis
    The subject key exactly as the record prints it on /record/subject?key=..., e.g. 'benchmark-cell:commerce/baby/clothing|SG|*|local|*|*'.

  Exemple d'appel

  {"name": "record_subject_history", "arguments": {"subject_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• record_verify_receipt≈ 224 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • receipt_hash · string · requis
    The 64-character hex receipt hash, as printed on a receipt or returned by the other record tools.

  Exemple d'appel

  {"name": "record_verify_receipt", "arguments": {"receipt_hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• store_audit≈ 194 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    The storefront domain or URL to audit, e.g. 'example.com'.

  Exemple d'appel

  {"name": "store_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://myoddly.com/api/public/mcp