@4da/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOURDA_DB_PATH | No | Path to 4DA's SQLite database | |
| FOURDA_OFFLINE | No | Disable all network calls | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vulnerability_scanA | 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. |
| dependency_healthA | 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. |
| upgrade_plannerA | 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. |
| what_should_i_knowA | 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. |
| ecosystem_pulseA | 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_contextA | 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. |
| decision_memoryA | 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. |
| check_decision_alignmentA | 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. |
| agent_memoryA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vulnerability_scan schema | Full JSON Schema for the vulnerability_scan tool |
| dependency_health schema | Full JSON Schema for the dependency_health tool |
| upgrade_planner schema | Full JSON Schema for the upgrade_planner tool |
| what_should_i_know schema | Full JSON Schema for the what_should_i_know tool |
| ecosystem_pulse schema | Full JSON Schema for the ecosystem_pulse tool |
| get_context schema | Full JSON Schema for the get_context tool |
| get_relevant_content schema | Full JSON Schema for the get_relevant_content tool |
| get_actionable_signals schema | Full JSON Schema for the get_actionable_signals tool |
| knowledge_gaps schema | Full JSON Schema for the knowledge_gaps tool |
| record_feedback schema | Full JSON Schema for the record_feedback tool |
| decision_memory schema | Full JSON Schema for the decision_memory tool |
| check_decision_alignment schema | Full JSON Schema for the check_decision_alignment tool |
| agent_memory schema | Full JSON Schema for the agent_memory tool |
| developer_dna schema | Full JSON Schema for the developer_dna tool |
| Skill manifest | Registry of 4DA skills for Claude Code agent dispatch |
| Tool categories | Tool groupings by category with tag metadata |
TDQS
Scored across 9 tools
Some tools are clearly distinct (vulnerability_scan vs dependency_health vs upgrade_planner), but get_context, what_should_i_know, and agent_memory all deal with context/memory and could cause misselection. check_decision_alignment overlaps with decision_memory's 'check' functionality.
Tool names follow a consistent snake_case pattern, mixing noun_verb and verb_noun forms (vulnerability_scan, dependency_health, upgrade_planner) with a few verb-first names (get_context, check_decision_alignment). The style is consistent, but verb placement varies slightly.
9 tools is appropriate for a developer-assistant server covering security, dependency, and memory features. Each tool seems purposeful and the count is within the ideal 3-15 range.
The security/dependency workflow is well covered (scan, health, plan), and memory tools cover both recording and recalling. Missing actions like clearing memory or comparing dependency versions are minor gaps that agents could work around.