4.6.0 → 4.7.0
minor reliz, 2026-yil 12-noyabrBirorta tool ta'rifi o'zgarmadi.
MCP serverlar / @upstash/context7-mcp
Oxirgi 9 ta yangilanishning 1 tasi agent o'qiydigan narsani o'zgartirdi: 0 ta tool tavsifi qayta yozilgan, 4.7.0 gacha.
npm paketi · oxirgi marta 2026-yil 13-noyabr kuni soxta sozlamalar bilan toza mashinada yozib olingan; faqat tools/list yuborilgan. O'zgargan tavsif zaiflik emas. npm sahifasi · Usul va cheklovlar · bu ma'lumot JSON ko'rinishida.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
Birorta tool ta'rifi o'zgarmadi.
query-docs: kiritma sxemasi o'zgardi
Sinalgan relizlar: 4.3.0 (2026-10-09); 4.4.0 (2026-10-13); 4.4.1 (2026-10-13); 4.4.2 (2026-10-15); 4.4.3 (2026-10-19); 4.4.4 (2026-10-19); 4.5.0 (2026-11-03); 4.5.1 (2026-11-06); 4.6.0 (2026-11-09); 4.7.0 (2026-11-12).
Pin — tool nomi, tavsifi va kiritma sxemasining SHA-256 qiymati, verfy.lock uni shunday yozadi. Lock'ingizda xuddi shu pin bo'lsa, agentingiz aynan shu ta'rifni o'qiydi. Verfy 0.16.0 va yangilari server yuborsa, tool sarlavhasi, annotatsiyalari va chiqish sxemasini ham qotiradi, shuning uchun bunday tool'ning lock'ingizdagi pin'i boshqacha bo'ladi.
| Tool | Tavsif | Pin |
|---|---|---|
| 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. | 1a7e831848ea |
| 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. 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. | 188a34ac2acc |
@upstash/context7-mcp bugun sizga beradigan narsani qotiring, lock'ni commit qiling, va tool o'zgarganda pull request oldingi va keyingi matn bilan yiqiladi. MCP sozlamangizdagi paket versiyasini ham qotiring.
$ pip install verfy
$ verfy lock check --update # har bir tool'ni ko'rsatadi, keyin verfy.lock ni yozadi
$ git add verfy.lock# .github/workflows/verfy.yml, actions/checkout dan keyin
- uses: verfy-dev/verfy-action@v1Bu serverni yuritasizmi? O'z relizlaringizda xuddi shu tekshiruvni ishga tushiring va README'ga Locked by Verfy belgisini qo'shing.