# Fix list: Pinecone API + MCP From Anchor Terminal's listing at https://www.anchorterminal.com/tools/pinecone, the October 2026 research run, assessed 1 October 2026. Grade BB, 76.4 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 Pinecone API + MCP: 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, 40 out of 100, up to 7.5 more on the total Why it scored 40: No x402, MPP or L402 (0). Per-unit prices for storage, read and write units, egress, import and backup are public per the 30 September check, and the rate-limit page lists the monthly caps per plan (20). Starter is free with no card (20). A person signs up in the browser to get a key. Service accounts need an existing organisation (0). 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. Reliability, 75 out of 100, up to 5 more on the total Why it scored 75: Atlassian Statuspage at status.pinecone.io with per-cloud, per-region components and an RSS history back to 2 January 2026 (20). Nine incidents since 9 July, most of them regional 5xx errors on serverless reads or writes. Four ran over an hour, 11 hours 7 minutes of read-path 5xx in AWS us-west-2 on 17 September, 4 hours 36 minutes of control-plane 5xx on 1 September, 4 hours 47 minutes in Azure eastus2 on 9 July and 4 hours 54 minutes of freshness lag in us-east-1 on 13 July. Each hit some indexes in one region rather than the whole service, so 5 rather than 0 (5). Limits published with numbers, 100 requests a second per namespace and 2,000 read units a second per index, plus monthly caps per plan (15). 429 TOO_MANY_REQUESTS with exponential backoff guidance, though no `Retry-After`. Upserts overwrite by ID, so a retried write is safe (15). 99.95% uptime SLA on Enterprise (10). GA (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. ## 3. Security & auth, 79 out of 100, up to 3.7 more on the total Why it scored 79: API keys are per project with roles, and the Admin API uses OAuth service accounts with client credentials (30). Key roles allow read-only access and deletion protection guards indexes, but the MCP server has no read-only mode (18). Stored records come back as written and we found no prompt-injection guidance (5). Audit logs are listed on the security page (12). SOC 2 Type II, ISO 27001 and HIPAA with a BAA, a trust centre at security.pinecone.io and a SECURITY.md in the MCP repo. No security.txt per the 30 September check and no bug bounty found (14). 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. Transparency & trust, 75 out of 100, up to 2.2 more on the total Made of editorial 63, provenance 86. Why it scored 75: Closed service with published terms. The MCP server and clients are Apache-2.0 (18). The privacy policy dates from 8 May 2024, gives no retention period beyond "as long as necessary", mentions a DPA for enterprise customers without a link, and has no subprocessor link (15). Quarterly API versions, each supported for at least 12 months with at least nine months to migrate. Calls without a version header fall to the oldest supported version (20). Regions per cloud are listed, but we found no subprocessor list in the policy (10). 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): - Domain age: pinecone.io, registered 2016-10-20 (9 years) (11 of 15) - security.txt: not found (0 of 10) ## 5. Agent ergonomics, 93 out of 100, up to 1.1 more on the total Why it scored 93: 9 MCP tools, but every database tool also carries two optional analytics fields, `llm_provider` and `llm_model`, each with about 500 characters of description, which adds context cost for no task benefit (20). `topK`, metadata filters, field selection, rerank `topN` and pagination tokens on list calls (20). Documented error codes, and MCP errors are written for the model, such as "Do not retry. Ask the user to create an API key" (18). Every tool sets readOnlyHint, and upsert sets destructiveHint and idempotentHint (20). Few required fields and official clients for Python, TypeScript, Java, Go and .NET (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. ## 6. Maintenance & community, 87 out of 100, up to 1.1 more on the total Why it scored 87: Python client v10.0.0 on 3 September 2026 (30). API 2026-07 went GA on 2 September, the MCP server v0.3.0 shipped on 7 August and the Python client v10.0.0 on 3 September (20). Dated release notes and support plans for a closed service, plus GitHub repos for the MCP server and clients (12). Official clients current with the 2026-07 API (15). CI on the MCP server and the Python client (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. ## 7. Schema & documentation, 94 out of 100, up to 1 more on the total Why it scored 94: OpenAPI files per API version in pinecone-io/pinecone-api, twelve for 2026-07 covering control, data, inference, admin, Assistant and Nexus, plus a proto file (25). llms.txt and Markdown docs (10). MCP descriptions say what each tool does, when to call `describe-index` first, and when a tool fails, for example search "only works with integrated-inference indexes", and they carry a freshness warning (18). Zod schemas with enums for cloud and rerank model and validated record fields, but `filter` is a free-form object (13). An error-handling guide and examples throughout the docs (13). Dated API versions released quarterly and a dated changelog (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. ## Deductions Each comes off the total. A fixed and documented problem counts for less at the next check. - Since MCP server v0.3.0 (7 August 2026), every database tool asks the calling model to report its provider and model name "to track usage analytics", and tells it not to ask the user. The values go to Pinecone with the API calls. The tool schema states the purpose, but the README and docs don't mention it (https://github.com/pinecone-io/pinecone-mcp/blob/main/src/tools/database/common/register-tool.ts). ## 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. - Whether failed or rate-limited requests consume read or write units - Whether Pinecone publishes a subprocessor list, since the privacy policy links none - unchecked: the per-unit prices on the pricing page, which the page text we read didn't include, so they stand per the 30 September check ## Weaknesses - Nine regional incidents between 9 July and 28 September 2026, four lasting more than an hour - Every MCP database tool asks the model for its provider and model name for analytics, which the README doesn't mention - The Developer MCP server only works with integrated-embedding indexes and has no read-only mode - Closed source, with BYOC on Enterprise as the only self-managed option - Read units, write units, storage and egress are each metered, and Starter stops serving reads at its caps ## 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. - Send `X-Pinecone-Api-Version: 2026-07` on every call. Without it you get the oldest supported version - Queries go to the index host from `describe_index`, not to api.pinecone.io - Wait a few seconds and retry when fresh upserts don't show up in search - Back off exponentially on 429. There's no `Retry-After` header - Starter blocks reads once egress or read units run out for the month, so a failing agent may just be out of quota ## What the review panel asked for - document the analytics fields (2 reviews) - Retry-After on 429 - MCP support for your own vectors - Make analytics fields opt-in - Document the fields in the README - Add Retry-After - Say if failures bill - remove self-report fields - read-only MCP mode - changelog entries for MCP - State failed-call billing ## 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.