Context7
NPM · @UPSTASH/CONTEXT7-MCP · 3 COMPONENTS · SCANNED SEP 20
Up-to-date code docs for any prompt
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 25 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1000 tokens (~500/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management15
- Stability check failed: the tool surface changed between 1.0.31 and 4.1.1: 1 tool removals, 1 breaking changes, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Context7 MCP server?
Context7 runs locally as an npm package, launched with npx -y @upstash/context7-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @upstash/context7-mcp
claude mcp add upstash-context7 -- npx -y @upstash/context7-mcp
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp"
]
}
}
} {
"servers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp"
]
}
}
} codex mcp add upstash-context7 -- npx -y @upstash/context7-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"upstash-context7": {
"type": "local",
"command": [
"npx",
"-y",
"@upstash/context7-mcp"
],
"enabled": true
}
}
} openclaw mcp add upstash-context7 --command npx --arg -y --arg @upstash/context7-mcp
mcp_servers:
upstash-context7:
command: "npx"
args: ["-y", "@upstash/context7-mcp"] {
"McpServers": {
"upstash-context7": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@upstash/context7-mcp"
]
}
}
} assistant mcp add upstash-context7 -t stdio -c npx -a -y @upstash/context7-mcp
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.
- 17 Sept 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 25 to 5.
- 15 Sept 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.90 ▲ functional
- 14 Sept 26 −11
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: 0.89 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 4.1.0 → 4.1.1 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.
- 12 Sept 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.89 ▲ functional
- 11 Sept 26 −25
- Malware scan: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Package version: 4.0.7 → 4.1.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@upstash/context7-mcp@4.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 25 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
query-docs Query Documentation ~328
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Do not call this tool more than 3 times per question.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryId | string | yes | Exact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user qu… |
| query | string | yes | What to look up in the library's documentation, scoped to a single concept. Be specific and include relevant details, but keep each query to one topic — if the user's question spans multiple distinct… |
No output schema declared.
No examples provided.
resolve-library-id Resolve Context7 Library ID ~543
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Each result includes: - Library ID: Context7-compatible identifier (format: /org/project) - Name: Library or package name - Description: Short summary - Code Snippets: Number of available code examples - Source Reputation: Authority indicator (High, Medium, Low, or Unknown) - Benchmark Score: Quality indicator (100 is the highest score) - Versions: List of versions if available. Use one of those versions if the user provides a version in their query. The format of the version is /org/project/version. For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result yo…
| Name | Type | Req | Description |
|---|---|---|---|
| libraryName | string | yes | Library name to search for and retrieve a Context7-compatible library ID. Use the official library name with proper punctuation — e.g., 'Next.js' instead of 'nextjs', 'Customer.io' instead of 'custom… |
| query | string | yes | What to look up in the library's documentation. This is used to rank library results by relevance to what the user is trying to accomplish. The query is sent to the Context7 API for processing. Do no… |
No output schema declared.
No examples provided.
What is the Context7 MCP server?
Context7 is an MCP server listed in the public MCP registry as io.github.upstash/context7. Up-to-date code docs for any prompt. This page covers its npm package (@upstash/context7-mcp).
Is the Context7 MCP server safe to use?
Context7 scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Context7 MCP server expose?
Context7 exposes 2 tools: resolve-library-id, query-docs. Their descriptions and schemas cost roughly 871 tokens of context every time the server is loaded.
Is the Context7 MCP server still maintained?
Context7 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Context7 MCP server under?
Context7 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.