
Agentic Research
io.github.TheAiSingularityPublished by GitHub account TheAiSingularityv0.1.3Updated Oct 24, 2026
Local research agent that verifies its own answers. Runs on Gemma 3 4B + Ollama, $0/query.
The publisher's own server: agentic.no
Overview
Local-first research agent that runs a multi-stage search, retrieval and verification pipeline and returns cited, self-checked answers to an assistant.
- What you can do
- Run a full research query on a question, optionally with a domain preset and a memory mode, returning a structured answer with verified and unverified claims, sources and a trace
- Reset the stored research memory and check how many memory entries exist
- Search the web through a self-hosted SearXNG instance, fetch and clean pages, and rerank results
- Augment web results with a local document corpus indexed from PDFs, Markdown, text or HTML
- Apply domain presets such as general, medical, papers, financial, stock trading or personal documents
- When to use it
- Useful when an assistant needs sourced, citation-backed answers to research questions and the user wants the work done locally or on a chosen OpenAI-compatible endpoint rather than a hosted research service. Also fits question answering over a private document collection.
- Requirements
- Runs as a local Python package (agentic-research-engine) started with the agentic-research-mcp command. Needs an OpenAI-compatible model endpoint: either a local Ollama install with pulled models, or a cloud endpoint with OPENAI_API_KEY. A SearXNG instance is expected for web search (SEARXNG_URL, default local port 8888). Optional settings include OPENAI_BASE_URL, MODEL_PLANNER, MODEL_SYNTHESIZER, EMBED_MODEL, LOCAL_CORPUS_PATH, ENABLE_FETCH and ENABLE_RERANK.
Installation
In SourceWeft
- Open Agentic Research in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
agentic-research-engine-oss
[License] [PyPI] [Version] [Default] [Tests] [Interfaces] [MCP]
The best $0 research agent that runs on a laptop. Open-source end-to-end, reproducible, privacy-preserving. No cloud dependency by default; no telemetry; every LLM call, every source, and every verification decision is visible.
Table of contents
- TL;DR
- Why use this instead of…
- Quickstart — Mac local
- Quickstart — no install (Google Colab)
- Three ways to drive it
- What ships
- Domain presets
- Bring your own documents
- MCP + Claude plugin
- Plugin / skill loader
- Architecture at a glance
- Repo layout
- Configuration (env vars)
- Testing
- Troubleshooting
- Honest limits
- Status + roadmap
- Contributing
- License
TL;DR
Local-first research agent that verifies its own answers. Runs on
Gemma 3 4B + Ollama (3.3 GB on disk) for $0/query; swaps to any
OpenAI-compatible endpoint with one env var.
Why use this instead of…
Honest read: on complex multi-hop reasoning benchmarks, Gemma 3 4B sits 15–25% below 30 B+ open models. We don't claim to beat GPT-5.4 Pro. We claim to be the best $0, runs-on-your-laptop, fully-open research agent in April 2026.
Quickstart — Mac local
Option A — PyPI (fastest)
Option B — from source
Expected wall-clock on an M-series Mac: ~45 s for a factoid, ~90 s for multi-hop synthesis. Zero dollars per query.
Higher honesty — cloud-model mode
Gemma 3 4B is surprisingly good at structure (plan, route, verify,
compress) but confabulates specific factoids when SearXNG doesn't
surface a source containing the right token. Live SimpleQA-mini run on
2026-04-21 (see engine/benchmarks/RESULTS.md)
showed gemma3:4b emitting "2023" for "year Anthropic published
Contextual Retrieval" (gold: 2024) and "LayoutLMv3" for "which
cross-encoder for reranking" (gold: bge-reranker-v2-m3).
The fix you probably want isn't a smarter synthesizer — it's a
more honest one. A 5-question head-to-head on the same retrieval
output showed gpt-5-nano + gpt-5-mini refuse to confabulate when
evidence was missing ("The provided evidence does not answer this
question"), where gemma3:4b confidently guessed. Per-claim
faithfulness went from 82.9 % → 100 %. Pass rate barely moved (1/5
vs 0/5) because retrieval is the real bottleneck — if SearXNG
didn't return a source with the gold token, neither model can
produce it.
Swap the whole stack to a cloud endpoint:
Cost is dominated by synthesizer tokens (~5–15 k per query). Full
cloud mode with gpt-5-nano + gpt-5-mini runs roughly
$0.02–0.05 per research query and is ~2-3× slower than Gemma
local (measured: 127 s vs 52 s mean wall on the 5-question subset).
Works with any OpenAI-compatible endpoint — Groq, Together, Mistral,
DeepSeek, local vLLM — so you can pick a cheap fast model
(llama-3.3-70b on Groq ≈ $0.003/query) or a frontier one. Per-node
base-URL routing (run gemma3:4b locally for plan/verify AND gpt-5-mini
on cloud for synth in the same query) is tracked for 0.2; today the
pipeline uses one global OPENAI_BASE_URL.
The bigger accuracy lever is retrieval. Point
LOCAL_CORPUS_PATH at an indexed corpus containing your answer and
either model will be correct.
Quickstart — no install (Google Colab)
Five runnable notebooks in tutorials/:
- 01 — Engine API quickstart (mocked, no key) — see how the pipeline works without running inference.
- 02 — Groq cloud inference (free tier) — real LLM, no local GPU.
- 03 — Build your own corpus — upload PDFs, index them, query.
- 04 — MCP server from Python — drive the engine as a tool from another agent.
- 05 — Domain presets showcase — compare presets on the same question.
Each notebook is self-contained, runs end-to-end on Colab free tier, no credit card required.
Three ways to drive it
CLI
TUI (Textual — keyboard-driven, SSH-safe)
Three panes: sources · answer + hallucination flags · trace + memory hits. Press Enter to ask, Ctrl-M to cycle memory mode, Ctrl-L to clear, Ctrl-Q to quit.
Web GUI (FastAPI + HTMX on localhost:8080)
No auth. No cloud. No analytics. Dark theme. Streams tokens in place.
What ships
engine/ — the flagship
8-node LangGraph pipeline with 2026-SOTA composition:
classify → plan → search → retrieve → fetch_url → compress → synthesize → verify
Every stage is env-toggleable for leave-one-out ablation. Techniques
folded in: HyDE, CoVe verification, iterative retrieval, FLARE active
retrieval, question classifier router, step critic (ThinkPRM pattern),
LongLLMLingua-lite compression, cross-encoder rerank
(BAAI/bge-reranker-v2-m3), Anthropic contextual chunking, W6 small-
model hardening (three-case synthesize prompt + per-chunk char cap).
core/rag/ — reusable retrieval primitives (v1 stable)
HybridRetriever (BM25 + dense + RRF) · CrossEncoderReranker ·
contextualize_chunks (Anthropic pattern) · CorpusIndex (bring-
your-own-PDFs). 5 exports, used by the engine and the archived
recipes.
archive/recipes/ — pre-engine reference recipes
research-assistant, trading-copilot, document-qa,
rust-mcp-search-tool. All still work; all tests still pass. The
research-assistant/production/main.py is a thin shim over
engine.core.pipeline so the cookbook framing is preserved.
Domain presets
Six YAML files in engine/domains/:
Write your own in ~10 lines of YAML — see docs/domains.md.
Bring your own documents
Supported formats: PDF (via pypdf), Markdown, plain text, HTML (via
trafilatura). The index persists as a directory with a human-readable
manifest.json + a pickled index.pkl. Rebuild anytime the docs change.
Details: docs/self-learning.md covers the
trajectory + memory model; docs/plugins-skills.md
covers external plugins.
MCP + Claude plugin
engine/mcp/server.py is a Python MCP server exposing:
research(question, domain?, memory?)→ structured{answer, verified_claims, unverified_claims, sources, trace, totals, memory_hits}reset_memory()memory_count()
Bundled Claude plugin at engine/mcp/claude_plugin/ — four skills
(/research, /cite-sources, /verify-claim, /set-domain), ready to
submit to the Anthropic marketplace.
Register in Claude Desktop:
Plugin / skill loader
Install third-party Claude plugins or Hermes (agentskills.io) skills:
Safety: every install runs a forbidden-symbols scan
(eval(, exec(, os.system(, …) — rejects plugins that would
execute arbitrary code. Registry lives at
~/.agentic-research/plugins/, fully inspectable, wipable.
Full docs: docs/plugins-skills.md.
Architecture at a glance
Every stage has an ENABLE_* flag so you can leave-one-out ablate.
Deep spec: docs/architecture.md.
Repo layout
Configuration (env vars)
Full list in engine/core/pipeline.py header. Most-common knobs:
Full list: docs/architecture.md env-vars section.
Testing
All tests are mocked — no network, no API key, no model downloads. Live
integration smokes are separate (make smoke).
CI runs on every push / PR touching engine / core / recipes — see
.github/workflows/engine-tests.yml.
Troubleshooting
Still stuck? Open an issue with the bug_report
template — include ollama list, engine version, and the error.
Honest limits
- Gemma 4B ≠ GPT-5.4 Pro. 15–25 % below 30 B+ open models on hard multi-hop. We position as "best $0 local", not "SOTA."
- Gemma 3 4B confabulates specific factoids when SearXNG doesn't
return a source that contains the right token. Measured on
SimpleQA-mini: 0/20 strict pass rate (see
engine/benchmarks/RESULTS.md—verified_ratio85.5 %, zeromust_not_containhits; the model isn't emitting banned strings, it's picking wrong ones). Mitigations: (a) swap the whole stack to a cloud endpoint (see "Higher factoid accuracy" above —$0.02–0.05/querywithgpt-5-nano+gpt-5-mini), (b) give the engine aLOCAL_CORPUS_PATHso your own docs become retrieval targets, (c) setENABLE_RERANK=1to bias retrieval toward the right sources. - CoVe confirms internal consistency, not ground truth. Every synthesized claim is checked against retrieved evidence; claims don't get verified by the world. If retrieval misses, CoVe will still happily verify a confidently-wrong answer. The engine will never fabricate citations, but it can confidently repeat wrong information that was in its evidence pool.
- No LoRA fine-tuning in v1. Trajectory data is collected; actual model training deferred until GPU access + data volume.
- No hosted SaaS. Local-first is the entire v1 positioning.
- Team / multi-user features. Out of scope for v1.
- General web crawler / own search index. Not shipping. SearXNG stays. A curated research-focused index may land in v2.
- Mobile. Not in scope.
Status + roadmap
- 0.1.3 — public alpha (current). Features listed above; on PyPI +
the official MCP registry + the Anthropic plugin marketplace. See
CHANGELOG.md. - 0.2 — specialist tool wiring (
tools_enabledfield in presets finally activates), first LoRA run if GPU arrives, plugin catalog indocs/. - 0.3 — team-collab features (shared memory, PR-driven domain presets), desktop app packaging via Tauri.
- 0.4+ — open-work tracked in GitHub Issues.
Contributing
Good first issues: CONTRIBUTING.md. RFCs for
anything pipeline-scope. Plugin + domain-preset submissions welcome.
No Co-Authored-By trailers; author-as-written-by.
License
MIT. See LICENSE.
Related (sibling projects)
- HermesClaw — the secure runtime these recipes can run inside
- NVIDIA/OpenShell — kernel-level agent sandbox
- NousResearch/hermes-agent — self-improving agent (whose
agentskills.ioskill format we interoperate with)
MCP registry ownership
This PyPI package is the official source of the MCP server registered at https://registry.modelcontextprotocol.io. The line below is the ownership marker the registry validates — do not remove when editing this README.
mcp-name: io.github.TheAiSingularity/agentic-research
Source: README.md at commit e2ab781
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Agentic integrations
agentic.no
no.agenticOfficial publisher
A remote MCP endpoint that helps an assistant find GPU sellers for AI inference by model, ordered cheapest first, with per-call payment via x402.
Agentic Engineering Periodic System
academy.aseOfficial publisher
Agentic Engineering Periodic System's hosted MCP server, published by ase.academy; no sign-in required; Streamable HTTP; 4 tools.
Agentic RL: Credit Assignment and CLI Agents
space.hf.hoyant-su-agentic-rlOfficial publisher
Lets an assistant filter agentic reinforcement-learning methods by supervision, critic and task setting, and retrieve source links and BibTeX.

Agentic Video
Published by GitHub account tlq5l
Local stdio MCP server that lets a text-and-image assistant inspect video files: contact sheets, transcripts, cuts, loudness and sync checks.

Agentic Os
Published by GitHub account kinnister
Read-only MCP server that exposes the agentic-os governance, SDLC and quality-engineering methodology to an assistant, without executing anything.