
4da Mcp Server
io.github.runyourempirePublished by GitHub account runyourempirev4.6.0Updated Oct 24, 2026
Dependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.
Overview
Local MCP server giving AI agents dependency intelligence: CVE scanning, health checks and upgrade planning for a project's dependencies.
- What you can do
- Scan dependencies for known CVEs
- Run health checks on the dependency set
- Plan upgrades for outdated or vulnerable packages
- Read the host app's database, whose schema is published as a contract file
- When to use it
- Useful when an assistant needs to audit a project's dependencies for vulnerabilities, judge their health, or draft an upgrade plan, and you are willing to run it locally alongside the app whose database it reads.
- Requirements
- Runs as a local stdio process on the desktop, installed via npx from the npm package @4da/mcp-server (Node.js required) or as a Claude Code plugin. No authentication, environment variables or headers are declared. The README says it reads the host app's database.
Installation
In SourceWeft
- Open 4da Mcp Server 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
@4da/mcp-server has moved
The 4DA MCP server now lives in its own repository, with its full history:
https://github.com/4DA-Systems/4da-mcp-server
Install it as before; the package name is unchanged:
As a Claude Code plugin:
This folder stays only so that older links keep resolving. Issues, releases and contributions go to the new repository.
The server reads this app's database. The schema it relies on is published
from here as src-tauri/contract/app-schema.sql,
generated from the migrations; CI checks every app schema change against the
server's queries before it merges.
Source: mcp-4da-server/README.md at commit e06a08a
Tools
0Version history
1- v4.6.0LatestSep 16, 2026
Score
40% 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
Declare a license in the repository or the registry entry.