Bragproof

← Reports

@4da/mcp-server

Starts with no setup6.3.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 2 of 2 tools tried
Contacts while installing and starting: nothing

11tools listed
0hosts contacted
6files written
0.2 sto start
46dependencies

Its tool definitions changed since version 6.2.7. If you approved the earlier ones, read them again.

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y -p @4da/mcp-server@6.3.0 mcp-server

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

2 tools that take no input and look read-only were called once with nothing. 2 returned a result.

dependency_healthReturned a result under 0.1 s · 1,030 characters
get_contextReturned a result under 0.1 s · 170 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

vulnerability_scan project_path, severity_filter, include_dev, force_refresh, package, include_test_fixtures, response_format
Scan this project's lockfiles (npm/pnpm/yarn/bun, Cargo, Python, Go) for OSV.dev vulnerabilities in installed versions, transitives included, with fix versions and where each is pinned; `package` for one dep. Call when asked about security or CVEs. To vet a version first: dependency_check.
dependency_health include_dev, ecosystem_filter, sort_by, limit
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_planner include_dev, max_recommendations, risk_threshold, package, project_path
Prioritized upgrade plan for one project (project_path): the 4DA app's work order when computed (per-line targets, manifest vs lockfile fix), else the smallest version that fixes each vulnerability. Call when the user asks what to upgrade.
upgrade_impact package, to_version, from_version, ecosystem, response_format
What changes between the installed version of ONE dependency and a target: changelog per release, breaking changes, deprecations, security fixes, and this project's files that import it. Call before upgrading or bumping a dependency.
dependency_check items, response_format
Is a dependency version safe to write? Verdict on an exact version, or safe releases in a constraint ("7.x", "~=3.1"); npm, crates.io, PyPI, Go. Call BEFORE writing any version to a manifest: add, pin, upgrade, bump, downgrade.
6 more tools
what_should_i_know task, files, project_path
Pre-task briefing for a task in one project: the dependencies and package families it names, installed versions, confirmed vulnerabilities, releases since, your decisions, a delegation verdict. Call BEFORE a non-trivial task, especially one that changes dependencies.
ecosystem_pulse min_points, limit
Recent Hacker News discussions that name a dependency or framework this project actually uses. Call when the user asks what is new or being discussed in their ecosystem.
get_context include_ace, include_learned
What 4DA knows about the user: role, tech stack, interests, exclusions, and detected project context. Call FIRST when you need to know what the user works on before answering or recommending.
decision_memory action, decision_type, subject, decision, rationale, alternatives_rejected, context_tags, confidence, filter_type, filter_status, limit, technology, pattern, id, new_decision, new_rationale, new_status, new_confidence, old_id, new_id
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_alignment technology, pattern
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_memory action, session_id, agent_type, memory_type, subject, content, context_tags, expires_at, query, filter_agent, limit, tags, since
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.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseApache-2.0
Needsnode >=22.0.0
Sourcegithub.com/4DA-Systems/4da-mcp-server
Install scriptsbetter-sqlite3 declare them. This runner does not run them.
Tarballsha512-5oM0OoFJWlF7XSjgNNdMQnp5zPj5xNCK8fRO163+dObTwk25DNXi9MrkCeRl6GS4dJ37GPUJA7kY2meF0pNdMg==

Versions reported

VersionRunResultTools
6.3.02026-11-16Starts with no setup11
6.2.72026-11-12Starts with no setup11

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@4da/mcp-server.svg)](https://bragproof.smaverk.com/r/%404da/mcp-server)

New version out? Ask for a fresh report.