# Context7 (remote · mcp.context7.com)

Up-to-date code docs for any prompt

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.context7.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/upstash-context7/mcp.md), [page](https://verifymcp.io/servers/upstash-context7/mcp)
- mcpb · `context7.mcpb`: 46/100, [markdown](https://verifymcp.io/servers/upstash-context7/https-github-com-upstash-context7-releases-download-mcpb-v4-1-1-context7-mcpb.md), [page](https://verifymcp.io/servers/upstash-context7/https-github-com-upstash-context7-releases-download-mcpb-v4-1-1-context7-mcpb)
- npm · `@upstash/context7-mcp`: 71/100, [markdown](https://verifymcp.io/servers/upstash-context7/upstash-context7-mcp.md), [page](https://verifymcp.io/servers/upstash-context7/upstash-context7-mcp)

## Channel facts

- Endpoint: `https://mcp.context7.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `4.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http upstash-context7 'https://mcp.context7.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "upstash-context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "upstash-context7": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.upstash-context7]
url = "https://mcp.context7.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "upstash-context7": {
      "type": "remote",
      "url": "https://mcp.context7.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add upstash-context7 --url 'https://mcp.context7.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  upstash-context7:
    url: "https://mcp.context7.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "upstash-context7": {
      "Transport": "http",
      "Url": "https://mcp.context7.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add upstash-context7 -t streamable-http -u 'https://mcp.context7.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "upstash-context7": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, 0)

- [functional] Server version: 4.1.0 → 4.1.1

### 2026-09-13 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 78, +1)

- [functional] Server version: 4.0.7 → 4.1.0

### 2026-09-09 (score 77, +1)

- [functional] Server version: 4.0.5 → 4.0.7

### 2026-09-07 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `resolve-library-id` (~543 tokens)

Resolve Context7 Library ID

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…

Input parameters:

- `libraryName` (string, required): 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, required): 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…

### `query-docs` (~328 tokens)

Query Documentation

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.

Input parameters:

- `libraryId` (string, required): 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, required): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/upstash-context7/mcp#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 74
- 2026-09-01: 73
- 2026-08-31: 73
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 71

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

### Is the Context7 MCP server safe to use?

Context7 scores 82 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 871 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.context7.com/mcp
- Repository: https://github.com/upstash/context7
- Website: https://context7.com/
- Changelog RSS feed: https://verifymcp.io/servers/upstash-context7/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/upstash-context7/mcp.json
- HTML version of this page: https://verifymcp.io/servers/upstash-context7/mcp