mcpbeat

Amazon MCP Server

com.seoapi/amazon
not responding

Amazon is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Validate Amazonbot and Amzn-SearchBot IP addresses. Remote MCP validate_ip tool.

Uptime history 42 hours of history · worst hour 25%
42 hours agonow
94.5%
Uptime 24h
86 of 91 checks
1
Tools
read from the server
56 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add amazon --transport http https://amazon.seoapi.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "amazon": {
      "url": "https://amazon.seoapi.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.amazon]
url = "https://amazon.seoapi.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "amazon": {
      "url": "https://amazon.seoapi.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "amazon": {
      "url": "https://amazon.seoapi.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

validate
validate_ip
Check whether an IP address (IPv4 or IPv6) is a genuine Amazonbot IP address, verified against Amazonbot's published IP data on seoapi.com.

Endpoints

URLTransportStateLatencyChecked
https://amazon.seoapi.com/mcp streamable-http answering 58 ms 9 min ago

Amazon — questions

Answers built from our own checks of this server.

What can Amazon do?
It exposes 1 tools, read directly from the server on our last check. Among them: validate_ip. 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 →
Is Amazon working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 86 of 91 checks got a reply (94.5%), average response time 56 ms. The bar chart above shows every period we have measured.
The registry lists Amazon as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Amazon?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Amazon need an API key?
No. Amazon completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Amazon?
It answers our handshake in 56 ms on average, which is faster than 97% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.