Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Track this specific mcp_server implementation and its adoption, setup drift, privilege model, and source activity.
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Access Turbopuffer vector and database APIs from MCP
What we know
Official Stainless-generated Turbopuffer MCP using sandboxed code-mode tools for SDK operations; local package and hosted proxy options.
Maintenance / activity evidence
- 145491 npm downloads during 2026-09-08 through 2026-10-07 for @turbopuffer/turbopuffer-mcp
Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- API operations can read/write namespace data Reported action classes: API operations can read/write namespace data. Complete write authority is not verified.
- Turbopuffer API key
- Sensitive access: Vector records, API credentials, User data
- Sandbox blocks code access to web/filesystem, not authorized remote API writes
- Remote vector index may be changed or deleted with authorized API credentials; runtime sandboxing does not make remote writes impossible.
- Turbopuffer API key authorizes access to configured namespaces and potentially write/delete data; scope keys and protect secrets. Generated Stainless client.
- Unknown vulnerabilities, deployment environment and client privileges not exhaustively reviewed.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
· 145.5k package downloads / 30 days
Downloads observed Oct 9, 2026.
Exact npm package @turbopuffer/turbopuffer-mcp; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.
All limitations / Review context
What changed in documented permissions, distribution and MCP integration of Turbopuffer MCP before the next review?
No substantiated blocker to accurately qualified PUBLIC RADAR TRACKING observed in the scoped cited documentation; material caveats are required on the public page.
- Sandbox blocks code access to web/filesystem, not authorized remote API writes
- Remote vector index may be changed or deleted with authorized API credentials; runtime sandboxing does not make remote writes impossible.
- Turbopuffer API key authorizes access to configured namespaces and potentially write/delete data; scope keys and protect secrets. Generated Stainless client.
- API operations can read/write namespace data
- Turbopuffer API key
- Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
- Reviewed write actions: API operations can read/write namespace data
- Sensitive access: Vector records, API credentials, User data
- Complete write authority is not verified.
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- Unknown vulnerabilities, deployment environment and client privileges not exhaustively reviewed.
- Exact dated attributable activity evidence
- production authorization and network isolation depend on deployment
- Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
- Needs Turbopuffer API key and region
- Code-mode operations can mutate remote records
- Remote service access needs intentional scoping
- No independent release lifecycle audit; do not claim precise activity date.
Original activity observations
- 145491 npm downloads during 2026-09-08 through 2026-10-07 for @turbopuffer/turbopuffer-mcp
Technical identity
npm/@turbopuffer/turbopuffer-mcp- Exact implementation source
- https://www.npmjs.com/package/@turbopuffer%2Fturbopuffer-mcp ↗
- Reviewed resource type
- MCP Server
- Package identity
- npm:@turbopuffer/turbopuffer-mcp
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry ↗
@turbopuffer/turbopuffer-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Setup · Watchlist
Install & Agents
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsBoth local stdio and separately hosted endpoint; set API key.
publisher documented install or connect · Publisher instructions
npx -y @turbopuffer/turbopuffer-mcp@latestConfigure / authenticate
MCP100 setup guideRequires TURBOPUFFER_API_KEY; publisher also shows distinct hosted/remote MCP with API-key request header. Avoid database insertion/deletion as smoke test.
Environment variables referenced by this route (respect the alternatives above): TURBOPUFFER_API_KEY
Check connection
Suggested checkUser-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guideGeneric client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.
What it does
Official Stainless-generated Turbopuffer MCP using sandboxed code-mode tools for SDK operations; local package and hosted proxy options.
- Capability
- Data & Databases
- Resource type
- MCP Server
- Best fit
- Access Turbopuffer vector and database APIs from MCP
Representative uses
- Search API docs
- Run SDK API queries
- Read and modify Turbopuffer namespace data
Limitations
- Needs Turbopuffer API key and region
- Code-mode operations can mutate remote records
- Remote service access needs intentional scoping
- Sandbox blocks code access to web/filesystem, not authorized remote API writes
- No independent release lifecycle audit; do not claim precise activity date.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Turbopuffer API key
- Permissions
- API operations can read/write namespace data
- Data handling
- Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
- Cost
- unknown
- Risk and cautions
- Sandbox blocks code access to web/filesystem, not authorized remote API writes
Access scope and cautions
- Write actions
- Not verified API operations can read/write namespace data
- Sensitive access
- Vector records API credentials User data
- Risk level
- high
- Security notes
- Remote vector index may be changed or deleted with authorized API credentials; runtime sandboxing does not make remote writes impossible. Turbopuffer API key authorizes access to configured namespaces and potentially write/delete data; scope keys and protect secrets. Generated Stainless client.
The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.
FAQ
Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.