timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Single-binary local RAG MCP server in Rust. MiniLM compiled in, hybrid search, zero deps.
教 AI 做这类工作的 Skill,可与本项一起使用
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 7/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 14/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
Claude 暂时无法连接 quillrag
开发者尚未在 MCP 注册表中填写安装方式
ChatGPT 暂时无法连接 quillrag
开发者尚未在 MCP 注册表中填写安装方式
Claude Code 暂时无法连接 quillrag
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 quillrag
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 quillrag
开发者尚未在 MCP 注册表中填写安装方式
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Ayush-yadav11 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/ayush-yadav11-quillrag)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.1.3)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 quillrag | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
One file. Zero dependencies. Ready before your editor finishes loading.
A local RAG engine in a single static binary — MiniLM embeddings compiled inside, hybrid dense + BM25 retrieval, MCP-native. No Node, no Python, no model download on first query.
| ~20 ms to ready | MCP handshake completes before the model even loads |
| Zero runtime deps | no Node, no Python, no pip/npm, no model downloads — ever |
| Hybrid retrieval | dense cosine ⊕ BM25 fused with Reciprocal Rank Fusion |
| Private by construction | no network code path after installation |
| One file, three OSes | ~105 MB (the model lives inside), CI-built for linux/macOS/Windows |
# 1. grab a prebuilt binary (or cargo install --path .)
gh release download --repo Ayush-yadav11/quillrag -p '*linux*' tar xzf quillrag-x86_64-linux.tar.gz && chmod +x quillrag
./quillrag index ~/notes # incremental walk
./quillrag search "how does backpropagation work"
Or wire it straight into Claude Desktop / Cursor and let the AI search your notes mid-conversation — config below.
$ ./quillrag serve --data-dir ~/.local/share/quillrag
2026-08-26 INFO quillrag 0.1.2 ready in 41ms <- handshake-ready before the model loads
| Stage | Cost |
|---|---|
| Binary start + MCP initialize | ~20 ms (measured: store open + tool registration only) |
First rag_search / rag_index call | +~300 ms one-time (mmap safetensors, build BERT graph) |
| Subsequent searches | ~25 ms per query (2-core CPU, small corpus) |
| Re-indexing unchanged corpus | near-zero (FNV content hash skip) |
The embedding model is *lazy*: the MCP handshake and rag_status never touch it, so editors see an instant server.
Download a prebuilt archive from the latest release — Windows x86_64, macOS Apple Silicon, and Linux x86_64 are all built by CI on every version tag:
# linux/macOS example: fetch + extract the latest release
gh release download --repo Ayush-yadav11/quillrag -p '*linux*' | tar xz chmod +x quillrag && ./quillrag --version
Linux requirement: v0.1.6 binaries are built on Ubuntu 24.04 runners and
link glibc 2.39 (
pidfd_spawnp/pidfd_getpid). On older distros (glibc
< 2.39, e.g. Ubuntu 22.04), build from source with your local toolchain
instead:
cargo install --path ..
Or build from source:
cargo install --path .
Cross-compile targets used by CI: x86_64-unknown-linux-gnu, aarch64-apple-darwin, x86_64-pc-windows-msvc.
Claude Desktop / Cursor / any MCP client:
{
"mcpServers": { "quillrag": { "command": "/usr/local/bin/quillrag", "args": ["serve"], "env": { "QUILLRAG_DATA": "~/.local/share/quillrag" } } } }
Or just run ./quillrag serve and point any stdio client at it.
| Tool | What it does |
|---|---|
rag_index | Incrementally index a directory/file. Skips unchanged files, re-embeds only diffs. Pruning is scoped to the directory you pass: docs indexed from other roots are untouched. Symlinked files/dirs are followed. |
rag_search | Hybrid retrieval: dense MiniLM cosine + BM25 keyword, fused with Reciprocal Rank Fusion. Returns ranked chunks with source paths. |
rag_status | Document/chunk counts, bytes indexed, file-type breakdown. |
rag_clear | Wipe everything. |
CLI equivalents (same engine):
quillrag index ~/notes # incremental walk
quillrag search "auth flow" -k 5 # one-shot search quillrag status # stats quillrag clear # wipe
sentence-transformers/all-MiniLM-L6-v2 — masked mean pooling + L2 norm, numerically matching sentence-transformers on CPU. Weights are include_bytes!-ed into the binary and mmap'd from a materialized cache on first load.Σ 1/(60+rank)) — no score-scale tuning, robust to heterogeneous rankings.md markdown txt rst json yaml yml toml csv tsv html htm xml log rs py js jsx ts tsx go c h cpp hpp java rb sh bash zsh sql proto graphql dockerfile makefile ini cfg conf env — extend with -e ext1,ext2 / "extensions": [...].
Ignored dirs: every dot-directory (.git .obsidian .vscode …) plus node_modules target dist build venv __pycache__ vendor.
Applications embedding the engine (default-features = false) can index more through IndexHooks extractors:
| Feature | Adds |
|---|---|
pdf | PdfExtractor: text-layer PDFs, one section per page; hits carry page. |
ocr | Ocr, ImageExtractor (png/jpg/webp/bmp/gif) and OCR of scanned PDF pages via PdfExtractor::with_ocr. Bundles the ocrs models (~12 MB, CC BY-SA 4.0, see assets/ocr/NOTICE.md); English / basic Latin text only. |
Files that are readable but contain no text are recorded as empty documents, so unchanged ones are not re-OCR'd on every pass (IndexOptions::retry_empty re-checks them).
quillrag index ~/notes # incremental walk of one root
quillrag index ~/notes --no-prune # add/update without deleting anything quillrag index ~/notes --force # re-embed this root, preserve other roots
~/work-docs survive a later quillrag index ~/personal-notes against the same data dir. Only files that lived under the directory being walked and have since disappeared get pruned. Existing files excluded by extensions or size stay indexed. --no-prune disables deletion, including through MCP's no_prune. --force re-embeds only the selected sources. Use clear explicitly to wipe a store. An empty successful scan warns and may prune that root's last file.Older batched indexing could associate document paths with the wrong chunks. The fix cannot reconstruct those associations from the stored index alone. Build a fresh data directory from your source files, verify search results, then switch your client to it. Keep the old directory until verification passes. This also removes legacy relative-path keys, which the new indexer preserves rather than guessing their original working directory. New keys are absolute. Paths containing .. resolve through the filesystem; use a stable spelling for symlink-based roots. Re-indexing refreshes the BM25 sidecar as well.
Everything runs locally: embeddings, storage, search. Nothing leaves the machine — there is no network code path at all after installation.
Binary ≈ 105 MB (the model lives inside). RAM ≈ 120 MB resident while idle, spiking to ~250 MB during batch embedding.
quillrag stores everything in a single redb file and runs dense retrieval as an exact, single-threaded linear scan over all vectors — no ANN index yet. That makes the relevant limit *query latency*, not storage. Storage scales to millions of chunks; retrieval speed is O(N) per query.
| Corpus | Vectors | Approx. RAM (f32) | Steady-state query |
|---|---|---|---|
| 1K chunks | 1K | ~1.5 MB | ~25 ms (measured) |
| 10K chunks | 10K | ~15 MB | ~250 ms (extrapolated) |
| 100K chunks | 100K | ~154 MB | ~2–5 s (extrapolated) |
| 1M chunks | 1M | ~1.5 GB | 20–60 s (extrapolated — not viable without ANN) |
Verified on a corpus of 1K chunks (5/5 tests including real JSON-RPC-over-stdio e2e); figures above 1K are extrapolated from the O(N) dense-scan cost, not measured. A synthetic scale probe (src/bin/quillbench.rs) exists to measure the curve on your own hardware — run cargo build --release && ./target/release/quillbench.
What this means in practice:
How it compares to common alternatives on the *relevance* axis:
all-MiniLM-L6-v2 ceiling as quillrag's dense path, but quillrag adds BM25 + RRF fusion, which wins on keyword-heavy queries (error codes, IDs, exact tokens). quillrag has no reranker or metadata filtering, which llama-index offers on top.quillrag is deliberately minimal today. The big unlock is an approximate nearest-neighbor index:
Track the ANN work here: issue #1 — "ANN index for <1M chunks."
Is it really one file? Yes. The MiniLM weights + tokenizer are compiled in via include_bytes!. No npm install, no Python, no model download on first query. The binary is ~105 MB because the model lives inside it.
Why is startup so fast? The embedding model is *lazy*. The MCP handshake and rag_status never touch it — editors see a ready server in ~20 ms. The model only loads on the first rag_search / rag_index (~300 ms one-time).
What's the largest corpus it handles? Verified at 1K chunks (~25 ms/query). The architecture scales to millions of stored chunks; interactive retrieval holds up to low-tens-of-thousands today, and an ANN index (Roadmap) extends that to 1M+.
How is this different from llama-index? Similar hybrid r