English Français العربية

net.mostexpensivewatches/mcp

Official registry Data and databases

Documented luxury-watch auction records: 1,150+ verified results, prices, rankings and datasets

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http net-mostexpensivewatches-mcp 'https://mostexpensivewatches.net/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "net-mostexpensivewatches-mcp": {
            "type": "http",
            "url": "https://mostexpensivewatches.net/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. MostExpensiveWatches — watch auction records API, dataset, MCP server & CLI
  2. For AI agents — MCP server (one line of config)
  3. Datasets (CC-BY 4.0, schema.org Dataset, refreshed automatically)
  4. API (43 endpoints, no key)
  5. CLI (dependency-free Python)
  6. Human surfaces the data powers
  7. License

MostExpensiveWatches — watch auction records API, dataset, MCP server & CLI

Documented ultra-luxury watch auction data ($100k–$31M realized prices, primary-sourced), free to use, built for AI agents, CLIs and apps. No API key required.

Live site: https://mostexpensivewatches.net

For AI agents — MCP server (one line of config)

{"mcpServers": {"mostexpensivewatches": {"url": "https://mostexpensivewatches.net/mcp"}}}

Streamable HTTP, JSON-RPC 2.0. Tools: search_inventory, lookup_reference, search_auction_comps, list_upcoming_auctions, get_market_estimate, get_brand_info, search_answers, get_site_stats. Install docs: https://mostexpensivewatches.net/mcp/install

Datasets (CC-BY 4.0, schema.org Dataset, refreshed automatically)

DatasetLive JSONSnapshot here
Record Ledger — every documented watch auction record (all-time, per brand/material/year, record progressions)/data/records.jsondata/records.json
Auction Records — 1,150+ documented hammer prices with sources/api/auctions-dataset.jsondata/auction-records.json
Grail Index — the $1M+ segment record (182 results, $616M documented)/data/grail-index.jsondata/grail-index.json
Price Index — daily repeat-listing index across merchants/data/watch-price-index.jsondata/price-index.json

Snapshots in this repo are point-in-time copies; the live endpoints recompile daily via an autonomous verification pipeline. Cite as "MostExpensiveWatches Record Ledger".

API (43 endpoints, no key)

curl -s "https://mostexpensivewatches.net/api/listings/search?q=nautilus&limit=3"
curl -s "https://mostexpensivewatches.net/api/auctions?brand=Rolex&limit=5"
curl -s "https://mostexpensivewatches.net/api/answers/patek-5711-market-price.json"

CLI (dependency-free Python)

curl -sO https://mostexpensivewatches.net/cli/mew.py
python3 mew.py search "daytona" --limit 5

Also in this repo: mew.py

Human surfaces the data powers

License

Data: CC-BY 4.0 (attribution: MostExpensiveWatches). Code (mew.py): MIT.

Frequently asked questions

What is net.mostexpensivewatches/mcp?

Documented luxury-watch auction records: 1,150+ verified results, prices, rankings and datasets

How do I install net.mostexpensivewatches/mcp?

It runs as a remote server. In Claude Code: claude mcp add --transport http net-mostexpensivewatches-mcp 'https://mostexpensivewatches.net/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does net.mostexpensivewatches/mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is net.mostexpensivewatches/mcp open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains net.mostexpensivewatches/mcp?

It is published by softdevfz. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.