io.github.algolayertechnologies/mapsi-mcp vs Mapsource OpenStreetMap & Geospatial APIs
io.github.algolayertechnologies/mapsi-mcp is an MCP server published by algolayertechnologies. Marketplaces we read that list it: 1 (Official MCP Registry). Mapsource OpenStreetMap & Geospatial APIs is an MCP server published by robit-man. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Downloads/month (npm): 100 Downloads/week (npm): 18 Not marked · First seen |
Listed Version: 0.3.1 No figure published 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 | io.github.algolayertechnologies/mapsi-mcp | Mapsource OpenStreetMap & Geospatial APIs |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mapsi-mcp) | Remote server (api.mapsource.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/algolayer/mapsi-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 16 h ago |
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
io.github.algolayertechnologies/mapsi-mcp
Geocoding, routing, isochrone, H3, elevation and 13 more geospatial tools via OpenStreetMap.
Mapsource OpenStreetMap & Geospatial APIs
OpenStreetMap queries, maps/styles, search, routing, terrain, analysis, pipelines, and rendering.
How to run each
io.github.algolayertechnologies/mapsi-mcp As a local MCP server: npm package
claude mcp add --env "MAPSI_API_KEY=<YOUR_MAPSI_API_KEY>" --transport stdio mapsi-mcp -- npx -y mapsi-mcpRequires: MAPSI_API_KEY (secret)
Mapsource OpenStreetMap & Geospatial APIs As a remote MCP server
claude mcp add --transport http mapsource https://api.mapsource.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Mapsource OpenStreetMap & Geospatial APIs has a remote endpoint we 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
The marketplaces of Mapsource OpenStreetMap & Geospatial APIs publish no settings it asks for, so we do not compare settings.
What it can do: io.github.algolayertechnologies/mapsi-mcp · What it can do: Mapsource OpenStreetMap & Geospatial APIs · 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.