io.github.FoundryNet/foundrynet-geo vs Inpoly
io.github.FoundryNet/foundrynet-geo is an MCP server published by FoundryNet. Marketplaces we read that list it: 1 (Official MCP Registry). Inpoly is an MCP server published by inpoly.dadev.nl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  io.github.FoundryNet/foundrynet-geo |  Inpoly |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.2 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.FoundryNet/foundrynet-geo | Inpoly |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (foundrynet-geo-production.up.railway.app/mcp) | Remote server (inpoly.dadev.nl/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) | github.com/foundrynet/foundrynet-geo | github.com/laflau/inpoly |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (3 h ago) | Not responding since 2026-10-23 |
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.FoundryNet/foundrynet-geo
x402-gated geocoding + distance gateway. Tools: geocode, distance.
Inpoly
Resolve coordinates against delivery and coverage polygons (geofences).
How to run each
io.github.FoundryNet/foundrynet-geo As a remote MCP server
claude mcp add --transport http foundrynet-geo https://foundrynet-geo-production.up.railway.app/mcpInpoly As a remote MCP server
claude mcp add --transport http inpoly https://inpoly.dadev.nl/mcp --header "X-Api-Key: <YOUR_X_API_KEY>"Requires: X-Api-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Neither endpoint 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: io.github.FoundryNet/foundrynet-geo · What it can do: Inpoly · 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.