Mapbox APIs + MCP vs NextBillion.ai

Mapbox APIs + MCP 82

Atlassian Statuspage at status.mapbox.com with an uptime view (20). The history page renders client-side and robots.txt disallows the incidents API, so on 1 November we read the history RSS feed and the incident pages. Two incidents on Navigation (API) fall in the 90 days from 3 August. On 19 October, 19:18 to 19:41 UTC, the Directions and Map Matching APIs in US-East had "elevated latency and missing route data for a significant portion of regional traffic" (23 minutes). On 20 October, 14:45 to 15:47 UTC, "brief, recurring periods of elevated latency and missing route results" in US-East (62 minutes of intermittent disruption). Neither was a core API down, or wide errors, for an hour or more, so minor only (20, was 30 with nothing after 29 June). Rate limits with numbers, 1,000 geocoding requests a minute by default, and X-Rate-Limit-Interval, -Limit and -Reset headers on responses, re-read on 1 November (15). A 429 on overrun with a reset timestamp to wait for, but no Retry-After and no backoff guidance (10). A published Service Level Agreement (last updated 15 April 2024) at mapbox.com/legal/sla gives customers with an executed order 99.9 per cent monthly availability per API, with service credits of 10 and 25 per cent. The 1 October to 17 October checks looked only at the pricing page and the API docs (10, was 0). The REST APIs are GA, but the MCP server is at 0.16 and its place_details_tool calls the Places API Details endpoint, which Mapbox still labels Public Preview with a contract subject to change (7). 20+20+15+10+10+7 = 82.

NextBillion.ai 45

Hosted lines, for the REST APIs at api.nextbillion.io and the hosted MCP server. A status page at status.nextbillion.io, 'NextBillion.AI API Status', renders only in a browser, and its Statuspage-style JSON paths return 404, so we couldn't see its components (10) or read any history. That's our limit, not a finding, and the rubric gives 5 (5). The API reference states 2,400 queries a minute, or 40 a second, for continuous requests (15). Each endpoint's error table lists 429 as 'QPM or API request count quota reached', with no Retry-After or backoff guidance (5). No SLA found; the terms say access isn't warranted to be uninterrupted (0). The REST APIs are GA. The MCP server is at version 0.5.3 (10). 10+5+15+5+0+10 = 45.

Mapbox APIs + MCP 84

Closed service with published terms and product terms, plus an MIT-licensed MCP server (20). A DPA, a privacy FAQ that says IP addresses are kept 30 days, and geocoding storage rules that are plain about what can be cached. The terms also let Mapbox build de-identified aggregated data from customer usage (24). An API policy of at least 90 days' emailed notice before an endpoint is deprecated, with dated removals in the changelog, though that changelog stopped in 2021 (18). 22 subprocessors with locations, 14 third-party and 8 affiliates, still last updated 4 June 2026 on 1 November (20).

NextBillion.ai 58

Editorial half only. Closed service under terms that name NextBillion.ai Pte. Ltd. and Singapore law, and an Apache-2.0 MCP server (18). The privacy policy keeps personal data while a legitimate business need exists, with no periods given. The MCP README says only tool arguments are sent to the API and nothing is retained between requests (14). No deprecation policy or dated notices found. The terms promise 10 days' notice of material changes to the terms (3). Data is mainly processed in Singapore, with transfers abroad under standard clauses. No sub-processor list found (8). 18+14+3+8 = 43.

Mapbox APIs + MCP 71

Public and secret tokens with scopes, URL restrictions, one-hour temporary tokens and documented rotation, which earns 30. Less 10 because the REST APIs take the token as the access_token query parameter, and that's the documented way in. The hosted MCP signs in with OAuth instead. Accounts on the card-free trial get a single token they can't rotate or delete until a payment method is added (20). Public-scope tokens can't change the account, and every MCP tool is read-only (18). Responses are structured place data, partly third-party POI names and attributes, and we found no prompt-injection guidance (7). The local MCP emits OpenTelemetry traces per tool call tagged with the client name. We didn't check per-token usage reporting in the account (8). SOC 2 Type II and SOC 3, a HackerOne bug bounty and a disclosure programme, re-read on 1 November. MCP 0.13.0 on 30 July 2026 fixed a query-parameter injection through directions_tool's exclude field, and 0.15.0 on 8 October shipped the fix for reads of cached tool results by anyone who knew a resource URI and could forge the owner's username claim, with a narrowed map CSP. 0.16.0 on 15 October replaced those cached refs for directions and isochrones with refs that re-run the request under the reader's token, and fetches place photos server-side only from public https hosts. All were stated in the public changelog. On 21 October the URL check for custom marker images and place photos was fixed to strip every trailing dot (localhost.. had passed), released in the v0.17.0-dev pre-releases of 30 October and not yet in a stable release. The photo fetch also resolves the host and refuses private addresses, and marker URLs are fetched by Mapbox's Static Images API, so we read it as hardening and don't deduct. No security.txt, still 404 on 1 November (18).

NextBillion.ai 46

The REST APIs take a single key query parameter, so a plain key that travels in URLs, which earns 20 less 10. The MCP server adds OAuth 2.1 with PKCE, seals the key into tokens with AES-256-GCM, accepts a Bearer header and stores nothing server-side, so 5 back (15). Every tool is read-only, and keys can carry an IP allowlist (12). Places results are POI and address text with no prompt-injection guidance (7). Usage alerts at 50, 75 and 90 per cent of credits, per the pricing FAQ. No per-call log found (5). /.well-known/security.txt returns 404, and we found no disclosure policy or bug bounty. The about page says the company follows ISO 27001 standards, without naming a certificate (7). 15+12+7+5+7 = 46.

Mapbox APIs + MCP 40

No x402, MPP or L402 (0). Per-1,000 prices for every API published without login, $0.75 temporary geocoding, $5 permanent, $2 directions, re-read on 1 November (20). The sign-up guide has a 'Start without a credit card' option, a trial with monthly limits such as 10,000 temporary geocodes, 10,000 directions requests and 5,000 map loads, and lower rate limits. Adding a card unlocks the full free allowances, permanent geocoding and raster tiles. Re-read on 1 November (20). Signup is a browser flow with email confirmation, and the hosted MCP needs a browser OAuth step (0).

NextBillion.ai 20

No x402, MPP or L402 (0). Pricing is by quote, with annual licences per order, asset or API call and no published unit price (0). A 7-day free trial with an API key and 'No credit card required' (20). A person signs up through the console or emails support for a key (0). 0+0+20+0 = 20.

Mapbox APIs + MCP 90

MCP server v0.16.0 on 15 October 2026, after v0.15.0 and v0.15.1 on 8 and 9 October (30). Three stable releases in the 90 days from 3 August, v0.15.0, v0.15.1 and v0.16.0, plus the v0.16.1-dev, v0.17.0-dev and v0.17.0-dev.1 pre-releases (20). Commits reference user-reported issues and fixes land within weeks. We couldn't see issue reply times from git (15). Listed in the official MCP registry as io.github.mapbox/mcp-server, active, with 0.16.0 the latest, published 15 October (15). CI builds and runs the test suite on every push and pull request, and since 0.17.0-dev also typechecks the tests (10).

NextBillion.ai 73

MCP server 0.5.3 on 30 October 2026 (30). Eleven tagged MCP releases between 7 October and 30 October, adding hosted mode, truck routing and geometry tools (20). Support by email, a public MCP repository with a changelog, but no public API changelog (8). The MCP server isn't in the official MCP registry, and we didn't check the mobile SDK versions (7). The MCP repository runs CI with unit and end-to-end tests (8). 30+20+8+7+8 = 73.

Mapbox APIs + MCP 85

No public OpenAPI for the REST APIs, but every MCP tool has a typed Zod input and output schema, published as JSON Schema 2020-12 since 0.15.0 (8 October) (20). llms.txt at docs.mapbox.com, re-read on 1 November (10). MCP descriptions say when not to use a tool, for example search_and_geocode_tool sends generic place types to category_search_tool and warns that big-box brand plus address queries are unreliable (17). Zod limits and enums, such as q capped at 200 characters after the team found the API rejects 201 (13). An error table per API with 401, 403, 404, 422 and 429 messages, and curl examples throughout (13). Versioned paths (geocode v6) and a dated MCP CHANGELOG.md, but the top-level API changelog's newest entry is still 5 November 2021, current changes sit in per-service pages, and the MCP guide on docs.mapbox.com still says v0.12.0 on 1 November (12).

NextBillion.ai 73

No OpenAPI document for the REST APIs was found in llms.txt or the docs. The hosted MCP server's 27 tools are defined with Zod schemas, so they carry typed JSON Schema inputs (15 of 25). llms.txt, llms-full.txt and a Markdown file for each docs page (10). Endpoint pages explain each parameter, and MCP tool descriptions say when not to use a tool, such as the geometry tools being straight-line rather than road distance (16). Parameter tables give types, allowed values and defaults, such as types and limit (default 10), though in packs several filters into one string (12). curl examples and a per-endpoint error table with causes (13). The MCP server has a dated changelog. No API changelog or versioned path was found (7). 15+10+16+12+13+7 = 73.