# Fix list: Doppler From Anchor Terminal's listing at https://www.anchorterminal.com/tools/doppler, the October 2026 research run, assessed 1 October 2026. Grade BB, 71.6 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on Doppler: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Payments & pricing, 25 out of 100, up to 9.4 more on the total Why it scored 25: No x402, MPP or L402 (0). Developer is free for 3 users then $8 a user, Team $21 a user a month, Enterprise custom, with no per-call price (10). A free plan and a 14-day Team trial; the pricing page doesn't say whether a card is taken (15 of 20). A person signs up in a browser and creates the token (0). The pricing page says AI agents and non-human identities ride free. The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 2. Agent ergonomics, 59 out of 100, up to 6.7 more on the total Why it scored 59: With no flags the MCP server exposes one tool per API operation, up to 89 in the spec we read; --read-only cuts that to the 36 GET operations and --config to 10 config and secret tools. The API has /secrets/names for names without values and a download endpoint for a whole config in one call (18 of 25). page and per_page on the list endpoints (15 of 20). Errors come back with a messages array and a status code, and the reference documents them only by range (10 of 20). No MCP tool annotations (read-only is a startup flag instead) and no idempotency keys (6 of 20). doppler run needs only a token, and the MCP server infers project and config from a scoped token; we didn't confirm current official SDKs beyond the CLI (10 of 15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 3. Security & auth, 82 out of 100, up to 3.2 more on the total Why it scored 82: Service tokens are bound to one config, read-only by default and can expire with --max-age, and service account identities trade an OIDC token for a short-lived Doppler token on Team and above. The CLI keeps serving its encrypted fallback file after a token is revoked (27 of 30). Read-only tokens, the MCP server's --read-only and --config flags, and startup warnings when a production config or write tools are exposed (17 of 20). Secrets aren't untrusted content; the MCP README tells you to scope tokens and review output, and there's no value masking (10 of 15). Activity logs for 3 days on Developer and 90 on Team, and the security fact sheet says every secret change is logged, but we found no per-read access log (10 of 15). SOC 2 and ISO 27001 claimed on the security page, a trust centre, HackerOne and a published list of customer-affecting vulnerabilities; security.txt is blocked by robots.txt, so we couldn't read it (18 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 4. Schema & documentation, 81 out of 100, up to 3.1 more on the total Why it scored 81: OpenAPI 3.1 at docs.doppler.com/openapi/core.json, 47 paths and 89 operations in the copy we read, with 4xx response schemas and a security scheme (25). llms.txt at docs.doppler.com with about 500 links to Markdown versions of the guides and API reference (10). Operation summaries are one word ("List", "Retrieve", "Download"), and the MCP tools inherit them, so a model learns little about when to use each (10 of 20). Typed parameters from the OpenAPI, carried into the generated MCP schemas (12 of 15). Error responses are defined in the spec, but the reference only describes them by status range (10 of 15). /v3 versioned paths, a monthly changelog (July and August 2026 entries) and semver CLI releases (14 of 15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 5. Maintenance & community, 76 out of 100, up to 2.1 more on the total Why it scored 76: CLI 3.76.6 on 21 September 2026, 10 days before this check (30). Six CLI tags from 3.76.1 (21 July) to 3.76.6, plus changelog entries for July and August 2026 (20). 35 open CLI issues, and most of the ten newest have no reply, including a panic report (#560) and one about secrets delete printing every value (#542) (10 of 25). The CLI and the MCP server (1.0.5 on npm, 4 June 2026) are official; the MCP server isn't in the MCP registry per the 30 September check, and we didn't confirm other SDKs (7 of 15). Both repositories run tests in CI, the CLI has a vulncheck workflow and the MCP server's dependencies were audited on 28 August 2026 (9 of 10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 6. Reliability, 90 out of 100, up to 2 more on the total Why it scored 90: Atlassian Statuspage at www.dopplerstatus.com with an incident history back to 2023 (20). Since 3 July 2026 the only incident is CLI downloads failing on 16 July, with nothing posted against the API or dashboard; the last API outages were on 18 and 20 November 2025 (30). Rate limits published per plan, 240 reads, 120 secret reads and 60 writes a minute on Developer (15). A 429 carries retry-after in seconds plus x-ratelimit-limit, -remaining and -reset headers, but there's no retry guidance for writes (13 of 15). Enterprise lists a 99.95% SLO, an objective rather than an agreement, and no SLA appears for Team (5 of 10). The API is generally available and the MCP server is marked experimental (7 of 10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 7. Transparency & trust, 77 out of 100, up to 2 more on the total Made of editorial 64, provenance 90. Why it scored 77: CLI and MCP server are Apache-2.0, the platform is closed under clear terms (18 of 30). Privacy notice of 17 September 2026 per the 30 September check, a DPA, and a subprocessor list dated 13 July 2026 with 9 entries, consistent with the fact sheet's single GCP us-central1 region; retention periods aren't stated (24 of 30). No deprecation policy or dated deprecation notices found (8 of 20). Subprocessors and data location are disclosed, but the CLI sends anonymous command analytics by default, with an analytics flag to turn it off that the README doesn't mention (14 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - security.txt: could not be fetched (0 of 10) ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - The listing put dynamic secrets on Team; the dynamic secrets docs say Enterprise only, corrected in pricingNotes. - The listing called the MCP server unversioned; npm has 1.0.5 from 4 June 2026, although package.json in the repository still reads 0.0.0. - Whether the Developer plan or the Team trial asks for a card; the pricing page doesn't say, and the listing's no-card tag is unconfirmed. - Whether CLI analytics are documented on the docs site; the README doesn't mention them. - unchecked: security.txt (robots.txt blocks it) and the status page incidents.json (robots.txt blocks it, we read the RSS instead). ## Weaknesses - Dynamic secrets and on-prem are Enterprise only, and Developer has no service accounts - The MCP server is experimental, has no tool annotations or value masking, and exposes up to 89 tools by default - 35 open CLI issues, most of the newest without a reply - The CLI keeps serving its fallback file after a token is revoked, and sends anonymous analytics unless turned off - No SLA, only a 99.95% SLO on Enterprise ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Create a service token scoped to one config and read-only, then start the agent with `doppler run --token $DOPPLER_TOKEN -- ` so values never touch disk - Start the MCP server with --read-only and --config as well as a scoped token; the server can't tell a token's permissions and would otherwise list write tools that fail - Call /v3/configs/config/secrets/names when you only need names, and secrets/download?format=json for every value in one call - On a 429 wait for the retry-after seconds; secret reads have their own limit, 120 a minute on Developer - Run `doppler configure flags disable analytics` on build agents if you don't want CLI command usage reported ## What the review panel asked for - versioned MCP tools - a deprecation policy - read-only as the MCP default - value masking in MCP output ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.