oddly is answering right now. Last checked 10 min ago. It exposes 6 tools.
The world, on the record. AI infrastructure built on the observed web.
Uptime history
35 days of history · worst day 98%
35 days agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
610 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 3
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 October 2026. No other catalogue keeps this.
8 Oct
3 tools appeared
record_answer, record_subject_history, record_verify_receipt
Nothing serious here today
Today is the operative word: we check oddly every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
run in your terminal
claude mcp add oddly-corpus --transport http https://myoddly.com/api/public/mcpSettings → Connectors → Add custom connector, then paste this address
https://myoddly.com/api/public/mcp~/.codex/config.toml
[mcp_servers.oddly-corpus]
url = "https://myoddly.com/api/public/mcp".cursor/mcp.json
{
"mcpServers": {
"oddly-corpus": {
"url": "https://myoddly.com/api/public/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"oddly-corpus": {
"type": "http",
"url": "https://myoddly.com/api/public/mcp"
}
}
}Available tools 6
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
record
record_answer
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.
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 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.
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, 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).
benchmark
benchmark_categories
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.
benchmark_lookup
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.
store
store_audit
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://myoddly.com/api/public/mcp | streamable-http | answering | 482 ms | 10 min ago |
Alternatives to oddly
same job, measured the same wayRoxyon
by bea-technology
Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.
Outcrawl
by outcrawlai
Web infrastructure for AI agents: scrape, crawl and search the web, run browsers and agents.
E
Evidra
by vitas
Evidra — Flight recorder for AI infrastructure agents
Volanea
by pankaj-bit361
Email infrastructure on Volanea: build templates, segments and workflows, send and check email.
Self Healing Infrastructure MCP
by csoai-org
Self Healing Infrastructure MCP Server by MEOK AI Labs
Oracle Cloud
by expertvagabond
Oracle Cloud Infrastructure MCP server
Flows
by rbnd-studio
Build product adoption your way - Product adoption infrastructure no-code or all-code.
E
Email
by primitive
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
oddly — questions
Answers built from our own checks of this server.
What can oddly do?
It exposes 6 tools, read directly from the server on our last check. Among them: benchmark_categories, benchmark_lookup, record_answer, record_subject_history, record_verify_receipt, store_audit. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is oddly mostly used for?
Its tools cluster around record and benchmark. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is oddly working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 610 ms. The bar chart above shows every period we have measured.
How do I connect oddly?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does oddly need an API key?
No. oddly completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is oddly?
It answers our handshake in 610 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.