36 MCP tools for codebase-aware developer intelligence. Privacy-first, zero config.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
4DA reads the internet for developers β privately, locally. Your codebase decides what's relevant.
It scans your codebase β Cargo.toml, package.json, go.mod, Git history β and scores every article, advisory, and release from 20+ sources against what you actually build. An item needs 2+ independent signals to survive. Everything else is rejected.
Benchmarked across 9 developer personas against a 245-item labeled corpus β 1,997 scored evaluations: 93% of content is rejected, and 98.9% of labeled noise is correctly rejected. Those are measured numbers, and you can reproduce them in one command. Your real rejection rate β computed from your own data, not ours β is shown in the Signal tab.
Saves and dismissals build a preference profile you can inspect, pin, or forget β and teach the Brief what to stop showing you. Relevance scoring itself stays grounded in your actual stack. And when the engine improves, it re-judges everything it already holds: yesterday's noise becomes tomorrow's signal.
Already using Claude Code, Cursor, or Windsurf? One command:
This scans your project, detects your stack, and gives your AI assistant live vulnerability scanning, dependency health, upgrade planning, and ecosystem intelligence. No API keys. No accounts. Works standalone β no desktop app required. Full MCP documentation.
5 independent signal axes. An item must pass 2 or more to surface. Single-axis matches are hard-capped at 28% β no matter how strong one signal is, it cannot pass alone.
| Axis | What it measures |
|---|---|
| Context | Semantic similarity to your active codebase |
| Interest | Alignment with your declared topics |
| ACE | Real-time signals from your Git commits and file edits |
| Dependency | Direct matches against your installed packages |
| Learned | Reserved β held out of scoring until it can be validated against your explicit feedback |
What passes the gate goes through 12 quality multipliers: content depth, novelty detection, competing tech penalties, title-body coherence, and intent scoring from recent work. Every constant is calibrated across 9 simulated developer personas with 245 labeled test items.
After keyword scoring, an LLM layer verifies the top items against your full developer context β stack, dependencies, recent commits, anti-technologies, and engagement history. Strict 1-5 rubric:
This is where the gold surfaces β articles the keyword pipeline misses because there's no keyword overlap, but the LLM understands the conceptual relevance to your specific project.
You own the compute. Use Ollama for free local inference (fully private), or bring your own Anthropic/OpenAI key. 4DA never pays for your compute, never stores your keys remotely, never makes API calls you didn't configure.
Content creators who learn the scoring algorithm still can't game it:
No algorithm can be gamed when the scoring signal comes from your local filesystem. Your Cargo.lock doesn't lie.
4DA is local-first and direct-to-provider. There is no 4DA-operated server, no analytics, and no user account system. Your indexed content, scores, and intelligence live in a SQLite database on your machine.
The only outbound traffic:
| Category | Where | Why |
|---|---|---|
| Source adapters | HN, GitHub, Reddit, arXiv, etc. | Fetching public content you configured |
| LLM providers | Anthropic / OpenAI / localhost Ollama | Only if YOU set up BYOK keys |
| License validation | Keygen | Only if you activated a paid license |
| Updater | GitHub Releases | Signed via minisign, once per session |
| Crash reports | None | 4DA sends no crash reports. Export a scrubbed diagnostic bundle locally, on demand. |
That's the whole list. There is no 4DA telemetry endpoint because there is no 4DA cloud.
Don't take our word for it:
| Network Transparency | Every outbound connection, with source code references |
| Trust Architecture | Why local-first means you don't need to trust us |
| Privacy (Plain Language) | One-page, no-legalese privacy summary |
| Security Audit Guide | Map of trust-critical code paths for auditors |
| Build from Source | Compile it yourself and verify the binary |
Pre-built binaries β no Rust toolchain required.
| Platform | Download | Auto-updates |
|---|---|---|
| Windows | .exe installer | Yes |
| macOS | .dmg (Apple Silicon & Intel) | Yes |
| Linux | .AppImage / .deb | Yes |
Every release publishes SHASUMS256.txt and per-file .sha256 sidecars. Verification instructions.
Windows users: SmartScreen will prompt on first launch (new application, building reputation). Click More info β Run anyway. Full details.
Or install the MCP server for Claude Code / Cursor / Windsurf:
Prerequisites: Rust (1.93.1 via rust-toolchain.toml), Node.js 20, pnpm 9.15. Platform-specific: Windows needs VS Build Tools 2022 with C++ workload. Full build guide.
First-run setup (API keys, context dirs, sources): Getting Started.
4DA runs on modest hardware. Private semantic search is built in β no GPU, no API key, and no first-run download required.
| Baseline (free) | + Cloud AI (BYOK) | + Local AI (offline) | |
|---|---|---|---|
| RAM | 4 GB | 4 GB | 16 GB (8B model); 32 GB for 12β14B |
| CPU | any 64-bit | any 64-bit | 6β8 cores |
| GPU | not needed | not needed | optional (recommended for speed) |
| Disk | ~500 MB | ~500 MB | + 5β9 GB per model |
| Network | install only | install + your AI provider | install + one model download (or none with Ollama) |
| Layer | Technology |
|---|---|
| App Shell | Tauri 2.0 (Rust backend + WebView) |
| Frontend | React 19 + TypeScript + Tailwind CSS v4 |
| Database | SQLite 3.45+ with sqlite-vec (vector search) |
| Scoring | Custom pipeline β build-time Rust codegen |
| Embeddings | OpenAI text-embedding-3-small / Ollama |
| LLM | Anthropic Claude / OpenAI / Ollama (BYOK) |
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/4da-mcp-server-2)<a href="https://allmcps.com/mcp/4da-mcp-server-2"><img src="https://allmcps.com/api/badge/4da-mcp-server-2?style=directory" alt="4da MCP Server on AllMCPs" /></a>