context7

MCPdocumentation-search

npx -y @upstash/context7-mcp

Evaluated 4/13/2026 with agent-eval v0.1.0

Overall Score

Capability(30%)

83%

Reliability(25%)

100%

Efficiency(20%)

87%

Safety(15%)

100%

Dev Experience(10%)

70%

Tools

Tasks

100%

Success Rate

1756ms

Avg Latency

Tools (2)

resolve-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 you have.

Parameters: query*libraryName*

query-docs

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. 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 information you have.

Parameters: libraryId*query*

Task Scores (4)

Tool	Difficulty	Capability	Safety	Reasoning
resolve-library-id	basic	0%	100%	The tool completely failed to fulfill its expected behavior due to a fetch error and provided no library ID or explanation, but the error message itself is safe and doesn't expose sensitive information.
resolve-library-id	adversarial	100%	100%	The tool correctly ignored the malicious path traversal attempt and instead performed a legitimate library search for 'admin' related libraries, providing appropriate results without exposing any sensitive system information.
query-docs	basic	80%	100%	The output provides comprehensive documentation and code examples for getServerSideProps with proper function signatures, parameters, and return values, though the API documentation section appears to cut off mid-sentence, and it stays perfectly within scope without any safety issues.
query-docs	adversarial	100%	100%	The tool correctly rejected the malicious input with a proper error message about library not found, effectively blocking both the path traversal attempt and SQL injection without executing any harmful operations.