A side-by-side look at the Fetch Price and Underpriced AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fetch Price for e-commerce work as a local process; choose Underpriced AI for e-commerce over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fetch Price when
You need dedicated capabilities in the E-Commerce domain.
No tool names declared yet. Check the project README from the listing page.
Underpriced AI tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fetch Price is categorized under E-Commerce and uses a local stdio subprocess. Underpriced AI belongs to E-Commerce and uses a remote HTTP/SSE transport. Pick Fetch Price for e-commerce work and Underpriced AI for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fetch Price has no declared pricing — check the project's own site. Underpriced AI is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fetch-price and underpriced-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fetch Price has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Underpriced AI has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.