@4da/mcp-server

MCPcommunity
v5.0.24DAApache-2.0Updated 22d agonpmGitHub

Dependency intelligence for AI coding agents. Live CVE scanning, dependency health, upgrade planning, ecosystem news, decision memory — zero config, privacy-first. 9 tools standalone, 14 total with desktop app.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
417Downloads/wk
22d agoLast update
Package
Author4DA
LicenseApache-2.0
Version5.0.2
Sourcenpm+mcp-registry
npm@4da/mcp-server
GitHub4DA-Systems/4DA
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface14 tools · none privileged
Security scan✓ Cleanv4.6.6 · 1mo agoHow well does this scan work?
MODERATE@hono/node-server@1.19.17Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) · transitive
EvalsNone
IndexedJul 18, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

14 tools · none privileged
Statically extracted from the published packagev4.6.6 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

agent_memoryNo description published

This tool published no description. Forge does not invent one.

check_decision_alignmentNo description published

This tool published no description. Forge does not invent one.

decision_memoryNo description published

This tool published no description. Forge does not invent one.

dependency_healthNo description published

This tool published no description. Forge does not invent one.

developer_dnaNo description published

This tool published no description. Forge does not invent one.

ecosystem_pulseNo description published

This tool published no description. Forge does not invent one.

get_actionable_signalsNo description published

This tool published no description. Forge does not invent one.

get_contextNo description published

This tool published no description. Forge does not invent one.

get_relevant_contentNo description published

This tool published no description. Forge does not invent one.

knowledge_gapsNo description published

This tool published no description. Forge does not invent one.

record_feedbackNo description published

This tool published no description. Forge does not invent one.

upgrade_plannerNo description published

This tool published no description. Forge does not invent one.

vulnerability_scanNo description published

This tool published no description. Forge does not invent one.

what_should_i_knowNo description published

This tool published no description. Forge does not invent one.

0 of 14 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Dependency intelligence for AI coding agents. Live CVE scanning, dependency health, upgrade planning, ecosystem news, decision memory — zero config, privacy-first. 9 tools standalone, 14 total with desktop app.

Keywords
mcpmcp-servermodel-context-protocolclaudeclaude-codeclaude-desktopcursorwindsurfcopilotvscodeai-toolsai-agentai-codingdeveloper-toolsdeveloper-intelligencedeveloper-productivitydeveloper-contextcodebase-awarenesscodebase-contextcode-contextcode-intelligencecontent-scoringrelevance-scoringprivacy-firstlocal-firstofflinehacker-newsarxivredditgithubknowledge-gapstech-radardecision-memorydependency-trackingsecurity-advisoriesagent-memorysqlite
Alternatives
Comparing tool surfaces…

Tools exposed

14 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in memory & knowledge graphs