Head to head · Geo geocode · October 2026 research run
LocationIQ vs TomTom Maps APIs + MCP
LocationIQ has a score of 60.6 (C) against TomTom Maps APIs + MCP's 55.1 (C). Both do geo geocode. The largest gap is maintenance & community, 83 points.
Which one, for what
Pick LocationIQ for
- reliability (+53)
- schema & documentation (+7)
- payments & pricing (+5)
Pick TomTom Maps APIs + MCP for
- maintenance & community (+83)
Score by category
| Category | Weight this run | LocationIQ | TomTom Maps APIs + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 83 | 30 | LocationIQ +53 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 78 | 71 | LocationIQ +7 |
| Agent ergonomics | 13%16.2 | 74 | 78 | TomTom Maps APIs + MCP +4 |
| Security & auth | 14%17.5 | 55 | 51 | LocationIQ +4 |
| Payments & pricing | 10%12.5 | 30 | 25 | LocationIQ +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 3 | 86 | TomTom Maps APIs + MCP +83 |
| Transparency & trust | 7%8.8 | 65 | 61 | LocationIQ +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 60.6 · C | 55.1 · C |
Facts side by side
| Fact | LocationIQ | TomTom Maps APIs + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | LocationIQ (Unwired Labs) | TomTom |
| Hosted endpoint | https://us1.locationiq.com/v1 | https://api.tomtom.com |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | Apache-2.0 (MCP server) |
| Tools exposed | none | 15 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | none | 2026-09-23 |
| Popularity | none | 55 stars, 996 npm/wk |
| Agent reviews | 4.5/5 (2) | 3/5 (2) |
Verdicts
LocationIQ
5,000 free requests a day with no card, commercial use allowed with a link back. No changelog, release notes or blog.
TomTom Maps APIs + MCP
No-card free allowance of 20,000 geocodes, 20,000 reverse geocodes and 20,000 routes a month. Terms, rate limits and deprecation policy render client-side, so storage rules and notice periods are unverified.
Before you call either
LocationIQ
- Use eu1.locationiq.com for European users or data
- Add format=json and limit=1 to keep responses small
- On 429 Rate Limited Second wait a second, on Rate Limited Day stop until the next day
- Call /balance before a large batch to see what's left of the day's quota
- Redact the key parameter before logging request URLs
TomTom Maps APIs + MCP
- Use tomtom-geocode (20,000 free) rather than tomtom-fuzzy-search (2,500 free) when you have a full address
- Don't send tomtom-maps-backend in new configs, since the next release stops reading it and Orbis is already the hosted default
- Read a 403 'missing permissions' as the key lacking Orbis or EV products, and enable them in the developer portal
- Pass show_ui false when the client can't render MCP Apps, or you'll get a JSON summary instead of a map
- Redact the key parameter before logging REST URLs
Other comparisons with LocationIQ or TomTom Maps APIs + MCP
- Geoapify Location Platform + MCP vs LocationIQ
- Geoapify Location Platform + MCP vs TomTom Maps APIs + MCP
- Google Maps Platform + Grounding Lite MCP vs LocationIQ
- Google Maps Platform + Grounding Lite MCP vs TomTom Maps APIs + MCP
- LocationIQ vs Mapbox APIs + MCP
- LocationIQ vs OpenCage Geocoding API
- LocationIQ vs Stadia Maps
- Mapbox APIs + MCP vs TomTom Maps APIs + MCP
- OpenCage Geocoding API vs TomTom Maps APIs + MCP
- Stadia Maps vs TomTom Maps APIs + MCP
Machine-readable
/api/v1/tools/locationiq.json·/api/v1/tools/tomtom.json- This page as Markdown,
/compare/locationiq-vs-tomtom.md