Wheremind vs Geoapify MCP by usefulapi
Wheremind is an MCP server published by wheremind.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Geoapify MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Wheremind |   Geoapify MCP by usefulapi |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.35.3 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Wheremind | Geoapify MCP by usefulapi |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | Remote server (wheremind.ai/mcp) | Remote server (geoapify.usefulapi.io/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days (differs) | 0 | 12 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 5 days ago returned HTTP 200 | Status out of date: last check 2 days ago returned HTTP 401 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Wheremind
Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Geoapify MCP by usefulapi
Geocode, reverse-geocode, autocomplete, route and search places.
How to run each
Wheremind As a remote MCP server
claude mcp add --transport http wheremind https://wheremind.ai/mcpGeoapify MCP by usefulapi As a remote MCP server
claude mcp add --transport http geoapify https://geoapify.usefulapi.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Wheremind · What it can do: Geoapify MCP by usefulapi · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.