Bragproof

← Reports

@pinecone-database/mcp

Starts with no setup0.4.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: nothing

12tools listed
0hosts contacted
0files written
0.3 sto start
96dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @pinecone-database/mcp@0.4.0

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.

list-indexesNo usable answer tool reported an error: PINECONE_API_KEY environment variable is not set, so Pinecone database tools cannot run. Do not retry. Ask the user to create an API key

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

search-docs query
Search the official Pinecone documentation for relevant
information. Use this before writing Pinecone code or explaining Pinecone
behavior, rather than relying on assumptions.
list-indexes llm_provider, llm_model
List all Pinecone indexes in the project, including each
index's configuration and readiness status. Use this to discover valid index
names before calling other tools.
describe-index name, llm_provider, llm_model
Describe the configuration of a Pinecone index, including
its embedding model and the "fieldMap" that names the record field holding the
text to embed. Call this before upsert-records to learn the required field
name. Check "status.ready" in the response to confirm the index can accept
upserts and queries.
describe-index-stats name, llm_provider, llm_model
Describe the statistics of a Pinecone index, including
record counts per namespace. Use this to discover which namespaces exist in an
index. Newly upserted records can take a few seconds
to be indexed and become visible to search results and index stats; if recent
data is missing, wait briefly and retry.
create-document-index name, fields, cloud, region, llm_provider, llm_model
Create a Pinecone document index: an index defined by a
schema of searchable "string" fields. Each field can declare "fullTextSearch"
(indexed for keyword search with BM25), "embed" (Pinecone embeds the text with a
hosted dense model for semantic search), "sparseEmbed" (a hosted sparse model),
or a combination. A good default is one field with both, for example
{"chunk_text": {"fullTextSearch": {"language": "en"}, "embed": {}}}, which
supports search by meaning and by exact terms on the same text. Fields you only
need to filter on are not declared here; send them as document metadata.
Use upsert-documents and search-document-index with the new index. This call blocks
until the index is ready. If an index with the same name already exists, it is
returned unchanged instead of erroring.
7 more tools
upsert-documents name, namespace, documents, llm_provider, llm_model
Insert or update documents in a Pinecone document index
(one created with create-document-index). Each document needs an "_id" and
plain text in every field the index declares with "embed"; Pinecone embeds that
text on write, so never send vectors. Call describe-index first to see the
schema. Fields not in the schema are stored as metadata you can filter on.
Documents with an existing "_id" are replaced. Newly upserted records can take a few seconds
to be indexed and become visible to search results and index stats; if recent
data is missing, wait briefly and retry.
search-document-index name, namespace, scoreBy, topK, filter, includeFields, llm_provider, llm_model
Search a Pinecone document index (one created with
create-document-index). Call describe-index first to see which fields declare
"embed", "sparseEmbed", or "fullTextSearch". Rank with one or more "scoreBy"
clauses:
- "embed": search by meaning on a field with "embed". Pass the query as plain
text; Pinecone embeds it with the field's model.
- "sparse_embed": search a field with "sparseEmbed" the same way.
- "text": keyword (BM25) search on one or more full-text fields. Good for exact
terms like IDs, error codes, and names.
- "query_string": Lucene-style query syntax. Don't pass "fields" (the API
rejects it); target fields with qualifiers inside the query, for example
'chunk_text:"exact phrase"', or omit qualifiers to search every full-text field.
An "embed" or "sparse_embed" clause must be the only clause; "text" and
"query_string" clauses can be combined. To rank by meaning and by exact terms,
run two separate searches: their scores are on different scales, so don't
compare them across searches. Returns matches with "_id", "_score", and the
fields named in "includeFields". Newly upserted records can take a few seconds
to be indexed and become visible to search results and index stats; if recent
data is missing, wait briefly and retry.
create-index-for-model name, cloud, region, embed, llm_provider, llm_model
Create a Pinecone index with integrated inference, which
automatically embeds the text field named in "fieldMap". Supports AWS, GCP, and
Azure cloud providers. This call blocks until the index is ready to accept
upserts and queries, so no readiness polling is needed afterwards. If an index
with the same name already exists, it is returned unchanged instead of
erroring. For a new index, prefer create-document-index, which supports
full-text search and integrated embedding on the same field.
upsert-records name, namespace, records, llm_provider, llm_model
Insert or update records in an integrated Pinecone index.
For a document index, use upsert-documents instead.
Text in the field named by the index's "fieldMap" is embedded automatically —
call describe-index first to confirm that field name. Records with an existing
"id" are overwritten. Newly upserted records can take a few seconds
to be indexed and become visible to search results and index stats; if recent
data is missing, wait briefly and retry.
search-records name, namespace, query, rerank, llm_provider, llm_model
Search an index for records that are semantically similar
to the query text. Only works with integrated-inference indexes (e.g. created
with create-index-for-model), which embed the query automatically; it fails on
standard indexes and document indexes (use search-document-index for those) — use
describe-index to check the index type. Returns hits
with "_id", "_score", and the record's stored "fields". Newly upserted records can take a few seconds
to be indexed and become visible to search results and index stats; if recent
data is missing, wait briefly and retry.
rerank-documents model, query, documents, options, llm_provider, llm_model
Rerank a set of provided documents by relevance to a
query. Use this for documents that did not come from a Pinecone search (e.g.
externally sourced text). To rerank the results of a single-index search,
prefer the "rerank" parameter of search-records instead of calling this tool
separately.
cascading-search indexes, query, rerank, llm_provider, llm_model
Search across multiple indexes for records that are
similar to the query text, then deduplicate and rerank the combined results.
Reranking is required for this tool. Only works with integrated-inference
indexes. To search a single index, use search-records instead.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=22.0.0
Sourcegithub.com/pinecone-io/pinecone-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-JewEAQw+C3vys9hWT4vMePzeP5AA8QZeHMmS4JPtYIuHZtdQRmx0o4DZZCcdXluT8dNEXM3oh1tB473vJgUA8A==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@pinecone-database/mcp.svg)](https://bragproof.smaverk.com/r/%40pinecone-database/mcp)

New version out? Ask for a fresh report.