Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/spacehendrix/clauder/pineconegit clone --depth 1 https://github.com/spacehendrix/clauderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/spacehendrix/clauder/pinecone)<a href="https://agentmods.dev/mcp/spacehendrix/clauder/pinecone"><img src="https://agentmods.dev/badge/mcp/spacehendrix/clauder/pinecone.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
Pinecone scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"Pinecone": {
"_website": "https://docs.pinecone.io/guides/operations/mcp-server",
"_description": "search Pinecone documentation, manage indexes, upsert data, and query indexes",
"_requires": [
"$PINECONE_API_KEY_{{PROJECT_NAME}}"
],
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "$PINECONE_API_KEY_{{PROJECT_NAME}}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 17 lines scan A a1cf4590c066
Pinecone is an MCP server published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other mcp servers, from other repositories
elicit
Elicitation MCP server. Runs locally from the @blizzy/mcp-elicit npm package.
figma-desktop
A Model Context Protocol Server that runs as stdio, wrapping a Streamable HTTP server, so any MCP-supporting client can use Streamable HTTP MCP Servers. Runs locally from the @pyroprompts/mcp-stdio-to-streamable-http-adapter npm package. Needs 1 environment variable to run.
chrome-devtools
MCP server "chrome-devtools", hosted remotely at 127.0.0.1, as configured in L-X-T/ng-agentic.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.