Ottom
MCP server · ottom.io · found in a public list · checked since 2026-11-13
Live, handshake completed · latest check
https://ottom.io/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-13 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
check_store_readinessget_benchmarklist_checks
- Tools
- 3
- This list since
- 2026-11-13
- First listed to us
- 2026-11-13
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- Credentials needed, by its MCP Registry entry (a secret header)
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
Calls it declares
check_store_readiness url* → url host publishedResult publishedResultNote lightCheckget_benchmark category* → name category url summary methodologylist_checks → lightCheck fullScan
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Links
What it states about itself, from its registry entry or package:
- Website: ottom.io/developers/mcp
Pages we read:
- llms.txt: ottom.io/llms.txt, read
Its own links, from its llms.txt, under its own headings and names. These are its words, not ours:
Product (41)
- Ottom: Can AI agents actually buy from your store?
- Our agent: user agent, egress addresses and opt-out
- Pricing: plans for testing your store with AI agents
- Agency partner program: sell AI agent readiness
- Privacy Policy
- markdown
- Terms of Service
- markdown
- Legal documents: terms, privacy and subprocessors
- Acceptable Use Policy
- markdown
- Partner Terms
- markdown
- Subprocessors
- markdown
- Data Processing Agreement
- markdown
- About Ottom: who runs it and how its agents behave
- Trust centre: how Ottom protects your data
- Reporting a security problem
- Status: live service checks and incident history
- What an agent readiness report looks like
- How it works: an AI agent tries to buy from your store
- Why it matters when AI agents cannot buy from your store
- Ottom compared with monitoring and AI visibility tools
- Checkly alternative: test checkout with AI agents
- markdown
- Datadog Synthetics alternative for AI shopping agents
- markdown
- Profound alternative: test whether AI agents can buy
- markdown
- Peec AI alternative: test whether AI agents can buy
- markdown
- AthenaHQ alternative: test whether AI agents can buy
- markdown
- Synthetic monitoring for ecommerce: test the purchase
- markdown
- Checkout monitoring: know when checkout stops working
- markdown
- Uptime vs synthetic monitoring for online stores
- markdown
Docs (36)
- Docs: plans, scan cadence and enterprise contracts
- markdown
- Plans and what each one includes
- markdown
- Enterprise contracts
- markdown
- Limits, and what happens when a store reaches one
- markdown
- How an Ottom score is calculated
- markdown
- Alerts, and when each one is sent
- markdown
- Workspaces, roles and adding a store
- markdown
- Proving a store is yours with a DNS record
- markdown
- Connecting a store from its own platform
- markdown
- Letting our agent through your CDN
- markdown
- Allowing our agent through Cloudflare
- markdown
- Allowing our agent through Fastly
- markdown
- Allowing our agent through Akamai
- markdown
- Allowing our agent through AWS WAF and CloudFront
- markdown
- Allowing our agent through Azure Front Door
- markdown
- Allowing our agent through Google Cloud Armor
- markdown
- Allowing our agent through the Vercel Firewall
- markdown
- Release gates: failing a build when AI agents stall
- markdown
Learn (47)
- Learn: agentic commerce guides for store owners
- Agentic commerce: how AI agents find, compare and buy
- Agentic commerce statistics 2026: market size, adoption
- markdown
- AI commerce ROI calculator
- Agent view: see your product page the way an AI agent does
- Help: reading your report, billing and allowlisting
- Developer docs: findings, fixes, CI and enterprise
- HTTP API reference
- markdown
- Ottom MCP server: check a store from any AI assistant
- markdown
- Ottom developer changelog: API, MCP server and docs
- markdown
- Agent readiness score vs purchase attempt
- Stall library: every way an AI agent fails on a store
- Agentic commerce glossary
- Free agent readiness tools
- AI robots.txt checker: which agents can shop your store
- llms.txt validator: check your store’s llms.txt file
- Product data checker: schema.org fields AI agents read
- Sitemap and product feed checker for AI agents
- UCP checker: validate your /.well-known/ucp manifest
- llms.txt generator
- AI agents, by what you sell
- AI agents and apparel stores
- markdown
- AI agents and beauty stores
- markdown
- AI agents and electronics stores
- markdown
- AI agents and food and drink stores
- markdown
- AI agents and health and wellness stores
- markdown
- AI agents and home and furniture stores
- markdown
- AI agents and jewellery and accessories stores
- markdown
- AI agents and outdoor and sports stores
- markdown
- The agentic readiness checklist
- Agentic readiness checklist: the discover stage
- markdown
- Agentic readiness checklist: the evaluate stage
- markdown
- Agentic readiness checklist: the compare stage
Links only (links/3): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Commerce, travel and logistics / Products and shopping (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-11-14. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 460 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_08bb175cbbe09112