Skip to content

oddly MCP server

com.myoddly/oddly-corpusmyoddly.comstreamable-httpv1.1.0Scanned

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

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the oddly MCP server can do

The oddly MCP server is published by myoddly.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: record_subject_history, record_verify_receipt, record_answer and store_audit), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (store_audit); 1 tool can send data out of your system (store_audit).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • record_answerAnswer 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: One question answered from the record
    • readOnlyHint: true
    • openWorldHint: false
  • record_subject_historyOne 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)…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: A subject's history on the record
    • readOnlyHint: true
    • openWorldHint: false
  • record_verify_receiptRecompute 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Verify a receipt against the record
    • readOnlyHint: true
    • openWorldHint: false
  • store_auditRun 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 ob…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "store_audit" says "store": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "store_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "store_audit" says "store": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Audit a public storefront
    • readOnlyHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • benchmark_categoriesList the product categories the oddly corpus currently covers, with how many observations and metrics back each one.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote 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.

    Annotations the server declares

    • title: List covered categories
    • readOnlyHint: true
    • openWorldHint: false
  • benchmark_lookupObserved 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…No findings

    Why it is in this group

    • The name "benchmark_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Look up observed category benchmarks
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://myoddly.com/api/public/mcp: tools/list returned 6 tools to an anonymous client, including record_subject_history (write), record_verify_receipt (write), record_answer (write), store_audit (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "store_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "store_audit" says "store": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http oddly-corpus https://myoddly.com/api/public/mcp
claude mcp add --transport http oddly-corpus https://myoddly.com/api/public/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__oddly-corpus__benchmark_categories",
      "mcp__oddly-corpus__benchmark_lookup"
    ],
    "ask": [
      "mcp__oddly-corpus__record_subject_history",
      "mcp__oddly-corpus__record_verify_receipt",
      "mcp__oddly-corpus__record_answer",
      "mcp__oddly-corpus__store_audit"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as oddly-corpus. Review it before you use it.

Capability tags behind 1 rule
  • mcp__oddly-corpus__store_audit untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.myoddly/oddly-corpus/verify?hash=44e0597355f329695572bb8d624a0271fc76cbeb9e61a085a108585251e0772d" | jq -e '.changed == false'

Pinned hash 44e0597355f3, from Nov 13, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.myoddly/oddly-corpus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.myoddly/oddly-corpus
[![Anlyon Radar](https://radar.anlyon.com/badge/com.myoddly/oddly-corpus.svg)](https://radar.anlyon.com/servers/com.myoddly/oddly-corpus)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

oddly MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the oddly MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the oddly MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the oddly MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the oddly MCP server have?

6 tools: 4 write, 2 read. record_subject_history, record_verify_receipt, record_answer, store_audit, benchmark_categories and benchmark_lookup.

Does the oddly MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the oddly MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): store_audit.

Has the oddly MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.