A side-by-side look at the Google Image Search and Notch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Google Image Search for developer tools work; choose Notch for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | G Google Image Search | N Notch |
|---|---|---|
| Category | Developer Tools | Multimedia Process |
| Quality signal | 37/100 · Fair | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 26 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Google Image Search | View Notch |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Google Image Search yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"notch": {
"url": "https://app.usenotch.ai/mcp/setup"
}
}
}