agent_memory
Cross-agent persistent memory: what one agent learns, any agent can recall. Call to store a discovery, decision, or warning, or to recall prior context before starting work.
LABSCO SUMMARY
Two things in one server: what your dependencies are doing, and what your team already decided.
The dependency half is live rather than remembered — OSV.dev for CVEs, the registries for freshness — which is exactly the data a model's training cut-off makes stale. The decision half is the more unusual part: check_decision_alignment lets an assistant test a suggestion against conventions you have already settled before it proposes switching your ORM for the third time.
What it is
A server that reads your project's manifest and lock files, resolves exact versions, and queries live vulnerability and registry data — alongside a persistent record of your architectural decisions and context.
What you get
- Known CVEs across npm, Rust, Python and Go dependencies, from OSV.dev, with no configuration — vulnerability_scan
- Version freshness, deprecation status and CVE counts as a health picture rather than a list — dependency_health
- A prioritized upgrade plan that separates quick wins from breaking changes, weighted by severity, deprecation and version distance — upgrade_planner
- A pre-task briefing: advisories, active decisions, signals and ecosystem updates relevant to what you are about to do — what_should_i_know
- Hacker News discussion filtered to your own stack — ecosystem_pulse
- What the server knows about you: role, tech stack, interests, learned affinities — get_context
- Architectural decisions recorded, listed, updated and superseded, and any proposal checked against them before it is suggested — decision_memory, check_decision_alignment
- Memory shared across agents, so what one discovers another can recall — agent_memory
Requirements
No account and no API key: install with claude mcp add 4da -- npx @4da/mcp-server, or point any client at the same package; Node 20 or newer, and npx @4da/mcp-server --setup configures every editor it detects. What leaves the machine is package names, versions and generic tech keywords — the same information your package.json already shows — and FOURDA_OFFLINE=true stops all network calls. The one exception to that is opt-in: configuring FOURDA_EMBED_PROVIDER=openai for semantic recall sends stored decision and memory text to OpenAI to be embedded, while the default and a local Ollama provider keep it on your machine.
Setup effort
One command — claude mcp add 4da -- npx @4da/mcp-server
USE CASES
01
Finding out whether anything you depend on is vulnerable
Scan the resolved dependency versions against live advisories, across whichever ecosystems the project uses.
02
Deciding what to upgrade first
Read the health picture, then take the plan that separates patch-level quick wins from the breaking ones.
03
Not re-opening a decision that was already made
Check the proposed library or pattern against the recorded decisions before suggesting a change.
04
Getting an agent up to speed before a non-trivial task
Take the briefing first — advisories, active decisions and what changed in the ecosystem you work in.
05
Carrying a discovery from one agent to the next
Store what was learned or warned about, and recall it before starting related work.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_decision_alignment
Check whether a technology or pattern aligns with the developer's recorded decisions. Call BEFORE suggesting a major tech change, new library, or architecture shift.
decision_memory
Record, list, update, or supersede the developer's architectural and tech decisions. Call when the user makes, changes, or asks about a settled decision or convention.
dependency_health
Dependency version freshness, deprecation, and CVE counts across npm/Rust/Python/Go. Call when the user asks whether their dependencies are outdated, stale, or need updating.
ecosystem_pulse
Live Hacker News discussions filtered to the user's tech stack. Call when the user asks what is new or trending in their ecosystem.
get_context
What 4DA knows about the user: role, tech stack, interests, and learned affinities. Call FIRST when you need to know what the user works on before answering or recommending.
upgrade_planner
Prioritized upgrade plan (CVE severity, deprecation, version distance), quick wins vs breaking changes. Call when the user asks what to upgrade, or after dependency_health surfaces problems.
vulnerability_scan
Scan dependencies for known CVEs via OSV.dev across npm/Rust/Python/Go, zero config. Call when the user asks about security, vulnerabilities, or CVEs, or before you recommend a dependency.
what_should_i_know
Pre-task briefing: advisories, active decisions, signals, and ecosystem updates for a task. Call BEFORE starting any non-trivial task to get caught up first.
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected; the project documents 14.
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
Claude Code
TERMINAL
claude mcp add 4da -- npx @4da/mcp-serverMCP Clients
Cursor, Windsurf, Claude Desktop
JSON
{
"mcpServers": {
"4da": {
"command": "npx",
"args": [
"@4da/mcp-server"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"4da": {
"type": "stdio",
"command": "npx",
"args": [
"@4da/mcp-server"
]
}
}
}Any installed editor — auto setup
ANY INSTALLED EDITOR — AUTO SETUP · TERMINAL
npx @4da/mcp-server --setup
