# `io.github.upstash/context7` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/io.github.upstash/context7
- JSON: https://anlyon.dev/api/v1/servers/io.github.upstash/context7
- Version: 4.4.4 (active)
- Publisher: io.github.upstash (GitHub account)
- Runs: remote (streamable-http), local (mcpb,npm)
- Sign-in to list tools: none
- Repository: https://github.com/upstash/context7
- Metadata from the official MCP Registry, synced 2026-10-21T18:51:09.687Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Context7
Up-to-date docs for AI agents
```

Scanned 2026-10-21T16:27:16.799Z over streamable-http.

**2 tools: 2 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 0 | ask |
| Only reads | read | 2 | allow |

## Findings

- **info** The word "credentials" in `resolve-library-id` ([credentials-mention](https://anlyon.dev/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.query.description mentions "credentials".

inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."
```

- **info** Long descriptions in `resolve-library-id` ([long-description](https://anlyon.dev/methodology#long-description))

```untrusted-server-text
The description is 2,006 characters long, over the 2,000 this check looks for.

description ends: "...on. If you cannot find what you need after 3 calls, use the best result you have."
```

- **info** The word "credentials" in `query-docs` ([credentials-mention](https://anlyon.dev/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.query.description mentions "credentials".

inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."
```


## Only reads (2)

Looks things up and changes nothing. Claude Code: allow.

### `query-docs`

- The name "query-docs" says "query": a word for reading.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
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.
```

### `resolve-library-id`

- The name "resolve-library-id" says "resolve": a word for reading.
- Findings: info credentials-mention, info long-description

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `context7`:

```json
{
  "permissions": {
    "allow": [
      "mcp__context7__resolve-library-id",
      "mcp__context7__query-docs"
    ],
    "ask": [],
    "deny": []
  }
}
```