Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Context7

REMOTE · MCP.CONTEXT7.COM · 3 COMPONENTS

Up-to-date docs for AI agents

0 this week 85 Trust /100

Last scanned (23 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1092 tokens (~546/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Changelog

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.

  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 4.4.3 → 4.5.0 functional
  • 19 Oct 26 0
    • Server version: 4.4.2 → 4.4.3 functional
  • 15 Oct 26 0
    • Server version: 4.4.1 → 4.4.2 functional
  • 14 Oct 26 0
    • Server version: 4.4.0 → 4.4.1 functional
  • 13 Oct 26 0
    • Server version: 4.3.0 → 4.4.0 functional
    • “query-docs” reworded the description of “libraryId” cosmetic
  • 10 Oct 26 0
    • Tool “query-docs” rewrote its description, which is the text the model reads security
    • Server version: 4.2.0 → 4.3.0 functional
    • “query-docs” added an optional parameter “language” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 4 Nov 2026 · Probed https://mcp.context7.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.context7.com CN=Amazon ECDSA 384 M01,O=Amazon,C=US 21 Sept 2026 6 Apr 2027 ECDSA 384 ECDSA-SHA384 a954e2a4cb0a9820d92fbcdb2dc9f81
SANs: *.context7.com
CN=Amazon ECDSA 384 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 4,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 ECDSA 384 ECDSA-SHA384 77312757ef4c3660f08af2403d3e55435d40b
CN=Amazon Root CA 4,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 ECDSA 384 SHA256-RSA 67f944a7111aac3ea73ba4cac07572696df8b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.context7.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
context7.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.context7.com/mcp Verified 200
http (plaintext) http://mcp.context7.com/mcp HTTPS enforced
MCP tools · 2 exposed · ~946 tokens

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 →

Tool Tokens
query-docs ~403

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.

NameTypeReqDescription
languagestring–Programming language the user is writing code in, such as 'Python', 'TypeScript', 'Go', or 'C#'. Ranks code examples in that language first. Leave it out when the language is unknown or does not appl…
libraryIdstringyesExact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v16.2.9') retrieved from 'resolve-library-id' or directly from user query in the…
querystringyesWhat 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 ~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…

NameTypeReqDescription
libraryNamestringyesLibrary 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…
querystringyesWhat 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.

Install

How do I install the Context7 MCP server?

Context7 is a hosted endpoint at https://mcp.context7.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.context7.com

# add to Claude Code
claude mcp add --transport http upstash-context7 'https://mcp.context7.com/mcp'
Common questions

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 docs for AI agents. This page covers its hosted endpoint (https://mcp.context7.com/mcp).

Is the Context7 MCP server safe to use?

Context7 scores 85 out of 100 on VerifyMCP. 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 946 tokens of context every time the server is loaded.

Does the Context7 MCP server require authentication?

No. We connected to Context7 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Context7 MCP server still maintained?

Context7 is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.