Context7 MCP server
io.github.upstash/context7upstashstreamable-httpv4.7.3Scanned
Up-to-date docs for AI agents
2 tools: 2 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Context7 MCP server can do
The Context7 MCP server is published by the GitHub account upstash. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool reads private data (query-docs); 2 tools bring in text other people can write (resolve-library-id and query-docs).
The fixed checks matched 3 findings (credentials-mention and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 4.7.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Only reads 2Show 2 read-only tools
query-docsRetrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.Reads private dataReads text others write1 finding
Why it is in this group
- The name "query-docs" says "query": a word for reading.
What it can reach
- private-dataThe name "query-docs" says "query" and "doc": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.query.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."
Description, as the server wrote it 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. If you know the programming language the user is working in, pass it as `language` so the results match their setup.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
resolve-library-idResolves a package/product name to a Context7-compatible library ID and returns matching libraries.Reads text others write2 findings
Why it is in this group
- The name "resolve-library-id" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.query.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."
- Info
The description is 2,006 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...on. If you cannot find what you need after 3 calls, use the best result you have."
Description, as the server wrote it 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 you have.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.context7.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://clerk.context7.com, https://context7.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Findings
Matches of fixed checks, with the text they matched.
The input schema at properties.query.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."
The description is 2,006 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...on. If you cannot find what you need after 3 calls, use the best result you have."
- Infoquery-docs
The input schema at properties.query.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 4.7.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http context7 https://mcp.context7.com/mcpclaude mcp add --transport http context7 https://mcp.context7.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__context7__resolve-library-id",
"mcp__context7__query-docs"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as context7. Review it before you use it.
Capability tags behind 2 rules
- mcp__context7__resolve-library-id untrusted-input
- mcp__context7__query-docs private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.upstash/context7/verify?hash=36dee0f3fbf80c4ed815e2b82cdfeb444188e7e941177d3124e31a3e0d6d91d6" | jq -e '.changed == false'Pinned hash 36dee0f3fbf8, from Nov 17, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.upstash/context7/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.upstash/context7)Source: MCP Registry · repository. Synced Nov 17, 2026, 14:18 UTC.
Context7 MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Context7 MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 3 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Context7 MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Context7 MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Context7 MCP server have?
- 2 tools: 2 read. resolve-library-id and query-docs.
Does the Context7 MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Context7 MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Context7 MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.