Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Generate QA datasets & evaluate RAG systems with failure diagnosis. Any LLM.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
OPENAI_API_KEY, ANTHROPIC_API_KEY标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"ragscore": {
"command": "uvx",
"args": [
"ragscore"
],
"env": {
"OPENAI_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add ragscore --env OPENAI_API_KEY=your-value --env ANTHROPIC_API_KEY=your-value -- uvx ragscore运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"ragscore": {
"command": "uvx",
"args": [
"ragscore"
],
"env": {
"OPENAI_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"ragscore": {
"type": "stdio",
"command": "uvx",
"args": [
"ragscore"
],
"env": {
"OPENAI_API_KEY": "your-value",
"ANTHROPIC_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 HZYAI 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:OPENAI_API_KEY, ANTHROPIC_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.8.6)于6个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Generate QA datasets & evaluate RAG systems in 2 commands
🔒 Privacy-First • ⚡ Lightning Fast • 🤖 Any LLM • 🏠 Local or Cloud • 🌍 Multilingual
English | 中文 | 日本語 | Deutsch
# Step 1: Generate QA pairs from your docs
ragscore generate docs/
ragscore evaluate http://localhost:8000/query
That's it. Get accuracy scores and incorrect QA pairs instantly.
============================================================
✅ EXCELLENT: 85/100 correct (85.0%) Average Score: 4.20/5.0 ============================================================
❌ 15 Incorrect Pairs:
pip install ragscore # Core (works with Ollama)
pip install "ragscore[openai]" # + OpenAI support pip install "ragscore[notebook]" # + Jupyter/Colab support pip install "ragscore[all]" # + All providers
Already installed? Keep up to date — new versions add features like failure diagnosis and retrieved context capture:
`bash
pip install --upgrade ragscore
`
Perfect for Jupyter, Colab, and rapid iteration. Get instant visualizations.
from ragscore import quick_test
result = quick_test( endpoint="http://localhost:8000/query", # Your RAG API docs="docs/", # Your documents n=10, # Number of test questions )
result = quick_test( endpoint="http://localhost:8000/query", docs="docs/", audience="developers", # Who asks the questions? purpose="api-integration", # What's the document for? )
result.plot()
bad_rows = result.df[result.df['score'] < 3] display(bad_rows[['question', 'rag_answer', 'reason']])
Rich Object API:
result.accuracy - Accuracy scoreresult.df - Pandas DataFrame of all resultsresult.plot() - 3-panel visualization (4-panel with detailed=True)result.corrections - List of items to fix# Set API key (or use local Ollama - no key needed!)
export OPENAI_API_KEY="sk-..."
ragscore generate paper.pdf ragscore generate docs/*.pdf --concurrency 10
ragscore generate docs/ --audience developers --purpose faq ragscore generate docs/ --audience customers --purpose "pre-sales" ragscore generate docs/ --audience "compliance auditors" --purpose "security audit"
# Point to your RAG endpoint
ragscore evaluate http://localhost:8000/query
ragscore evaluate http://api/ask --model gpt-4o --output results.json
Go beyond a single score. Add detailed=True to get 5 diagnostic dimensions per answer — in the same single LLM call.
result = quick_test(
endpoint=my_rag, docs="docs/", n=10, detailed=True, # ⭐ Enable multi-metric evaluation )
display(result.df[[ "question", "score", "correctness", "completeness", "relevance", "conciseness", "faithfulness" ]])
result.plot()
================================================== ✅ PASSED: 9/10 correct (90%) Average Score: 4.3/5.0 Threshold: 70% ────────────────────────────────────────────────── Correctness: 4.5/5.0 Completeness: 4.2/5.0 Relevance: 4.8/5.0 Conciseness: 4.1/5.0 Faithfulness: 4.6/5.0 ==================================================
| Metric | What it measures | Scale |
|---|---|---|
| Correctness | Semantic match to golden answer | 5 = fully correct |
| Completeness | Covers all key points | 5 = fully covered |
| Relevance | Addresses the question asked | 5 = perfectly on-topic |
| Conciseness | Focused, no filler | 5 = concise and precise |
| Faithfulness | No fabricated claims | 5 = fully faithful |
CLI:
ragscore evaluate http://localhost:8000/query --detailed
--diagnose)When answers fail, --diagnose tells you why — retriever miss, generator hallucination, incomplete answer, or wrong interpretation:
ragscore evaluate http://localhost:8000/query --diagnose
🔍 Failure Diagnosis:
Retriever Miss: 3 (42.9%) Generator Hallucination: 2 (28.6%) Incomplete Answer: 1 (14.3%) Wrong Interpretation: 1 (14.3%)
Uses the support_span already generated with each QA pair to give the judge grounding context. Combine with --detailed for full diagnostics:
ragscore evaluate http://localhost:8000/query --diagnose --detailed -o results.json
| Category | Meaning |
|---|---|
| Retriever Miss | RAG didn't retrieve the chunk containing the evidence |
| Generator Hallucination | Retrieved correctly but fabricated information |
| Incomplete Answer | Retrieved correctly but answer is partial |
| Wrong Interpretation | Retrieved correctly but misunderstood the content |
📓 Full demo notebook — build a mini RAG and test it with detailed metrics.
🎯 Audience & Purpose demo — generate tailored QA for developers, customers, auditors, and more.
🏠 Ollama local demo — 100% private RAG evaluation with no API keys.
# Use Ollama - no API keys, no cloud, 100% private
ollama pull llama3.1 ragscore generate confidential_docs/*.pdf ragscore evaluate http://localhost:8000/query
Perfect for: Healthcare 🏥 • Legal ⚖️ • Finance 🏦 • Research 🔬
RAGScore generates complex structured QA pairs (question + answer + rationale + support span) in JSON format. This requires models with strong instruction-following and JSON output capabilities.
| Model | Size | Min RAM | QA Quality | Recommended |
|---|---|---|---|---|
llama3.1:70b | 40GB | 48GB VRAM | Excellent | GPU server (A100, L40) |
qwen2.5:32b | 18GB | 24GB VRAM | Excellent | GPU server (A10, L20) |
llama3.1:8b | 4.7GB | 8GB VRAM | Good | Best local choice |
qwen2.5:7b | 4.4GB | 8GB VRAM | Good | Good local alternative |
mistral:7b | 4.1GB | 8GB VRAM | Good | Good local alternative |
llama3.2:3b | 2.0GB | 4GB RAM | Fair | CPU-only / testing |
qwen2.5:1.5b | 1.0GB | 2GB RAM | Poor | Not recommended |
Minimum recommended: 8B+ models. Smaller models (1.5B–3B) produce lower quality support spans and may timeout on longer chunks.
# Recommended: 8B model with concurrency 2 for local machines
ollama pull llama3.1:8b ragscore generate docs/ --provider ollama --model llama3.1:8b
ollama pull qwen2.5:32b ragscore generate docs/ --provider ollama --model qwen2.5:32b --concurrency 5
Expected performance (28 chunks, 5 QA pairs per chunk):
| Hardware | Model | Time | Concurrency |
|---|---|---|---|
| MacBook (CPU) | llama3.2:3b | ~45 min | 2 |
| MacBook (CPU) | llama3.1:8b | ~25 min | 2 |
| A10 (24GB) | llama3.1:8b | ~3–5 min | 5 |
| L20/L40 (48GB) | qwen2.5:32b | ~3–5 min | 5 |
| OpenAI API | gpt-4o-mini | ~2 min | 10 |
RAGScore auto-reduces concurrency to 2 for local Ollama to avoid GPU/CPU contention.
| Provider | Setup | Notes |
|---|---|---|
| Ollama | ollama serve | Local, free, private |
| OpenAI | export OPENAI_API_KEY="sk-..." | Best quality |
| Anthropic | export ANTHROPIC_API_KEY="..." | Long context |
| DashScope | export DASHSCOPE_API_KEY="..." | Qwen models |
| vLLM | export LLM_BASE_URL="..." | Production-grade |
| Any OpenAI-compatible | export LLM_BASE_URL="..." | Groq, Together, etc. |
output/generated_qas.jsonl){
"id": "abc123", "question": "What is RAG?", "answer": "RAG (Retrieval-Augmented Generation) combines...", "rationale": "This is explicitly stated in the introduction...", "support_span": "RAG systems retrieve relevant documents...", "difficulty": "medium", "source_path": "docs/rag_intro.pdf" }
--output results.json){
"summary": { "total": 100, "correct": 85, "incorrect": 15, "accuracy": 0.85, "avg_score": 4.2 }, "incorrect_pairs": [ { "question": "What is RAG?", "golden_answer": "RAG combines retrieval with generation...", "rag_answer": "RAG is a database system.", "score": 2, "reason": "Factually incorrect - RAG is not a database" } ] }
from ragscore import run_pipeline, run_evaluation
run_pipeline(paths=["docs/"], concurrency=10)
run_pipeline( paths=["docs/"], audience="support engineers", purpose="fine-tuning a support chatbot", )
results = run_evaluation( endpoint="http://localhost:8000/query", model="gpt-4o", # LLM for judging ) print(f"Accuracy: {results.accuracy:.1%}")
RAGScore is designed for AI agents and automation:
# Structured CLI with predictable output
ragscore generate docs/ --concurrency 5 ragscore evaluate http://api/query --output results.json
CLI Reference:
| Command | Description |
|---|---|
ragscore generate | Generate QA pairs from documents |
ragscore generate --audience | Tailored QA for specific audience |
ragscore generate --purpose | Focus QA on document purpose |
ragscore evaluate | Evaluate RAG against golden QAs |
ragscore evaluate --detailed | Multi-metric evaluation |
ragscore evaluate --diagnose | Failure root-cause classification |
ragscore --help | Show all commands and options |
ragscore generate --help | Show generate options |
ragscore evaluate --help | Show evaluate options |
Zero config required. Optional environment variables:
export RAGSCORE_CHUNK_SIZE=512 # Chunk size for documents
export RAGSCORE_QUESTIONS_PER_CHUNK=5 # QAs
只显示了开头部分;其余内容请在仓库中阅读