MCP Server
The ASINScope MCP server lets an AI assistant look up Amazon products for you. Once it is connected you can ask things like "find the UPCs for these 20 ASINs" or "which ASINs sell this barcode on amazon.de?" and the assistant calls ASINScope itself. There is no code to write.
It uses the Model Context Protocol (MCP), an open standard that Claude, Cursor and many other AI tools support.
https://api.asinscope.com/mcp
You need an API key from the API dashboard. The server uses the same key, the same plan and the same tokens as the REST API: a lookup made through an assistant costs exactly what the same lookup costs over REST.
Connect your assistant
Claude Code
claude mcp add --transport http asinscope https://api.asinscope.com/mcp \
--header "x-api-key: YOUR_API_KEY"
Cursor
Add the server to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:
{
"mcpServers": {
"asinscope": {
"url": "https://api.asinscope.com/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}
Other clients
Any client that supports MCP over Streamable HTTP works. Give it the server URL and send your key in the x-api-key
header.
Some apps only let you enter a server URL, with no place for a header. For those, put the key in the URL:
https://api.asinscope.com/mcp?key=YOUR_API_KEY
A key in a URL is easier to leak (it can end up in logs and screenshots), so use the header wherever the client supports it.
Tools
| Tool | What it does | Cost |
|---|---|---|
lookup_products | Looks up products by ASIN, UPC or EAN on one Amazon marketplace. Returns UPC/EAN codes, MPN, title, brand, category, Best Sellers Rank, lowest new price, package dimensions and images | Tokens, same as GET /products/lookup |
get_token_balance | Shows tokens left today, the daily allowance and the short-term bucket | Free |
lookup_products takes:
asins,upcsoreans: a list of codes. Exactly one of the three, with up to 10 codes per call on Basic and Pro plans.domain(optional): the marketplace. Defaults tocom. Alsoca,de,fr,it,nl,es,in,uk,jp,au,mx,pl.include_description(optional): also return the listing description and bullet points.
The results are the same JSON the REST API returns, including consumedTokens and dailyTokensLeft, so the assistant
can tell you what each request cost.
Things to know
- Barcode lookups can cost more than one token per code. A UPC or EAN costs one token per listing returned, and a barcode can be shared by many listings. Ask the assistant to check the balance first when you hand it a long list.
- Big lists take several calls. The assistant sends up to 10 codes at a time, and each plan has a short-term bucket (see Rate Limits). When the bucket is empty the server says how long to wait, and the assistant can continue after that.
- Limits and errors are the REST API's. A tool call that fails returns the same error body with the same
codeas the REST API, for exampleTOKEN_BUCKET_EMPTYorDAILY_LIMIT_REACHED. - Not found still costs a token. A code that matches nothing on the chosen marketplace is charged like any other.
Example requests
Once connected, you can ask in plain language:
- "Convert these ASINs to UPC and EAN and give me a table: B088H39PXX, B01NAL48FU."
- "Which ASIN has the UPC 793610399007 on amazon.com, and what is its current lowest new price?"
- "How many ASINScope tokens do I have left today?"
- "Here is my supplier's price list. Match each UPC to an Amazon ASIN, and stop if it would cost more than 200 tokens."
Troubleshooting
- "No ASINScope API key was sent": the client connected without a key. Add the
x-api-keyheader to the server configuration, or use the URL form with?key=. INVALID_API_KEY: the key is wrong. Copy it again from the API dashboard.NO_ACTIVE_SUBSCRIPTION: the key has no active API plan. See plans and pricing.- The assistant doesn't see the tools: restart the client after changing its MCP configuration, and check that the
URL ends in
/mcp.
Building your own integration instead? See the AI integration guide and the OpenAPI spec.