Use with AI assistants

Use LocationLists from ChatGPT or Claude, no setup needed

Ask for the list you need in plain English. Your assistant opens a LocationLists link, shows you the count, sample rows and the price, and you buy only what you approve. Pay by card, no account needed.

The link is https://locationlists.com/find?q= followed by the question in plain words. Nothing to install, nothing to sign up for.

Optional: connect for repeat use or wallet payments

claude mcp add --transport http locationlists https://locationlists.com/mcp

For developers

Optional: let your agent pay from a wallet

Without a connector, every question below is one link: https://locationlists.com/find?dataset=dental-practice-list&city=Austin&state=TX (relating two lists: https://locationlists.com/find?dataset=closed-bank-branches-us&state=OH&relate=nearest&k=1&b.dataset=bank-branches-us&b.state=OH).

2798 datasets. 17.7 million US and Canadian business locations — manufacturer dealer networks, state-licensed trade contractors, retail and restaurant chains, healthcare practices, and firms drawn from federal credential registries. Every one is compiled from the official locator, license register or government file that publishes it, and refreshed on a schedule. Your agent can query any of them and pay per row in USDC — no card, no account, no human at the keyboard.

Connect your client

Without a connector, the same count, preview and price come from a link: https://locationlists.com/find?dataset=dental-practice-list&city=Austin&state=TX (relating two lists: https://locationlists.com/find?dataset=closed-bank-branches-us&state=OH&relate=nearest&k=1&b.dataset=bank-branches-us&b.state=OH).

The server lives at https://locationlists.com/mcp — Streamable HTTP, no key, no signup.

claude mcp add --transport http locationlists https://locationlists.com/mcp

{"mcpServers":{"locationlists":{"url":"https://locationlists.com/mcp"}}}

{"servers":{"locationlists":{"type":"http","url":"https://locationlists.com/mcp"}}}

https://locationlists.com/mcp

POST https://locationlists.com/api/x402/query
Content-Type: application/json

{"dataset":"dental-practice-list","state":"TX","city":"Austin","limit":10}

How the payment works

Without a connector, the link's answer has a card Buy link instead: https://locationlists.com/find?dataset=dental-practice-list&city=Austin&state=TX (relating two lists: https://locationlists.com/find?dataset=closed-bank-branches-us&state=OH&relate=nearest&k=1&b.dataset=bank-branches-us&b.state=OH).

Any MCP client

Without a connector, each free tool's answer is a link: https://locationlists.com/find?dataset=dental-practice-list&city=Austin&state=TX (relating two lists: https://locationlists.com/find?dataset=closed-bank-branches-us&state=OH&relate=nearest&k=1&b.dataset=bank-branches-us&b.state=OH).

The server is plain MCP over HTTP. Point any client at it and read the 402:

POST https://locationlists.com/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call",
 "params":{"name":"query_locations",
           "arguments":{"dataset":"generac-dealers","state":"CO","limit":20}}}

The free tools — search_datasets, relate_locations, count_by_area, cotenancy, get_dataset, count_locations, get_sample, request_list, send_feedback, email_quote, get_quote, create_checkout, check_order, create_query_checkout — need no payment at all, so an agent can decide whether a dataset is worth buying before it spends anything. Start with count_locations: it says how many rows match a filter and exactly what fetching them would cost. Paid: query_locations, buy_dataset.

When this beats gathering it yourself

An agent with a browser can read a brand’s dealer locator, and for who is near me it should. A locator returns what is close to one point, capped per search. Three kinds of question that breaks:

• Coverage and gaps. “Where is coverage thin” depends on the complete set. A partial sweep does not just take longer — it returns a wrong answer, because every location you missed looks like a gap that isn’t there.
• National scale. One brand can be thousands of locations across every state. That is hundreds of capped queries, or one call here.
• Comparing brands. No single locator can show you two networks at once. These datasets share one schema.

For anything smaller than that, honestly, read the locator. We would rather you bought the right thing than the expensive thing.

Buying the whole file

Without a connector, a link's answer shows when the whole file is cheaper: https://locationlists.com/find?dataset=dental-practice-list&city=Austin&state=TX (relating two lists: https://locationlists.com/find?dataset=closed-bank-branches-us&state=OH&relate=nearest&k=1&b.dataset=bank-branches-us&b.state=OH).

Metered queries are for slices. If you want an entire dataset, that is a one-time purchase from $9 to $199 by record count, delivered as a CSV — and per row it is far cheaper than querying. Datasets under 5,000 records are only sold whole; the query tool will tell your agent so and hand back the link.