depsonar
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| depsonar_alertsA | Show pending dependency alerts from the last background scan. This reads the cache file written by the background checker (no live scan, instant response). If no cache exists, suggests running depsonar_scan or setting up the background checker. Examples:
|
| depsonar_checkA | Check a project for outdated dependencies. Supports Node.js, Python, Rust, Go, PHP, Ruby, and Dart/Flutter. Groups results by ecosystem for Node projects. Flags major version updates. Examples:
|
| depsonar_updateA | Update dependencies for a project. Works with any supported language. Three safety levels:
Examples:
|
| depsonar_scanA | Scan all projects in your workspace. Auto-detects language (Node, Python, Rust, Go, PHP, Ruby, Dart) and framework. Can filter by framework or language. Examples:
|
| depsonar_update_allA | Batch update across all projects. Defaults to dry_run=true (safe preview). Can filter by framework or language. Examples:
|
| depsonar_healthA | Score a project from 0-100. Checks outdated deps, security issues, lockfile. Examples:
|
| depsonar_installA | Fresh install. Use clean=true to nuke node_modules/vendor first. Examples:
|
| depsonar_setup_checkerA | Install or remove the background dependency checker. On macOS, uses launchd (native, lightweight). On Linux, uses cron. The checker runs on schedule, scans all projects, writes results to ~/.depsonar-cache.json, then exits. Zero RAM between runs, zero AI tokens, zero cost. Results are shown by depsonar_alerts. Examples:
|
| depsonar_configA | View or update configuration. Saved to ~/.depsonarrc.json. Examples:
|
| depsonar_auditA | Scan projects for known security vulnerabilities (CVEs). Uses npm audit, cargo audit, pip-audit, composer audit, govulncheck. CRITICAL: Run this after any CVE announcement (e.g. Svelte CVE-2026-22775, devalue DoS). Examples:
|
| depsonar_runtimesA | Check installed runtime versions (Node.js, Python, Rust, Go, PHP, Ruby, Dart, Swift). Detects EOL and outdated versions. Also checks project version files (.nvmrc, .python-version, rust-toolchain.toml, engines.node). Examples:
|
| depsonar_toolchainA | Check versions of globally installed tools: npm, pnpm, yarn, bun, composer, cargo, pip, typescript, git, docker, homebrew, vercel-cli, supabase-cli, wrangler. Shows installed vs latest version and update commands. Examples:
|
| depsonar_dockerA | Scan Dockerfile and docker-compose files for outdated or EOL base images. Checks: node, python, ruby, php, golang, rust, nginx, postgres, redis, ubuntu, alpine. Examples:
|
| depsonar_actionsA | Scan GitHub Actions workflow files for outdated or deprecated actions. Knows 30+ popular actions (actions/checkout, docker/build-push-action, cloudflare/wrangler-action, etc.). Examples:
|
| depsonar_envcheckA | Validate project environments: .env/.env.example sync, lockfile freshness, tsconfig best practices, Svelte config (detects deprecated svelte-preprocess with Svelte 5, duplicate adapters, etc.), multiple lockfiles. Examples:
|
| depsonar_infraA | Complete infrastructure health check in one command. Combines: runtime versions, global toolchain, security audit, CVE advisories, Docker images, GitHub Actions, environment configs, secret scanning, license compliance, deprecated packages, and optionally dependency scan. This is the "run everything" command. Use when you want a full picture. Examples:
|
| depsonar_cveA | Check projects against known framework CVEs (Svelte, SvelteKit, devalue, Next.js, Vite, Express, Axios). Goes beyond npm audit by checking a curated database of framework-specific vulnerabilities. CRITICAL after any CVE announcement. Run immediately when new CVEs are published. Examples:
|
| depsonar_deprecatedA | Detect deprecated, unmaintained, or replaced packages. Checks both npm deprecated flags and a curated list of known replacements (moment→dayjs, node-fetch→native fetch, request→undici, etc.). Examples:
|
| depsonar_secretsA | Scan project files for exposed secrets, API keys, tokens, and credentials. Detects: AWS keys, GitHub tokens, Stripe keys, Supabase JWT, OpenAI/Anthropic keys, private keys, database URLs, generic API key patterns. Also checks that .env files are properly gitignored. Examples:
|
| depsonar_licensesA | Check dependency licenses for commercial/SaaS compatibility. Flags: GPL/AGPL (copyleft, requires source disclosure), non-commercial (CC-BY-NC), unknown licenses. Important for SaaS products to avoid legal issues. Examples:
|
| depsonar_live_cveA | Real-time vulnerability scan using the osv.dev API. Checks every installed package against the global OSV database (npm, PyPI, crates.io, Go, Packagist, RubyGems, Pub). Unlike depsonar_audit (which uses local tools like npm audit), this queries the live osv.dev database for the most up-to-date vulnerability data. No API key needed. Examples:
|
| depsonar_changelogA | Check changelogs and breaking changes before updating. Shows major/minor/patch breakdown with changelog URLs and release notes for breaking updates. Run this BEFORE depsonar_update to understand what will change. Examples:
|
| depsonar_migrateA | Detect framework migration needs by scanning code for deprecated patterns. Currently supports: Svelte 4→5, Next.js 13→14→15. Finds exact file locations of code that needs to change, with migration instructions for each pattern. Examples:
|
| depsonar_docsA | Fetch up-to-date documentation, changelogs, and migration guides for any npm package directly from source (GitHub + npm registry). Use this BEFORE writing code that depends on a library, to get the latest API docs and avoid hallucinating outdated APIs. Sections available:
Combine with a query to focus on a specific topic (e.g. query="runes" for Svelte 5 migration docs). Examples:
|
| depsonar_search_packageA | Search the npm registry for packages by name or keyword. Returns matching packages with name, latest version, and description. Use this to find the right package name before calling depsonar_docs. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Soflutionltd/depsonar'
If you have feedback or need assistance with the MCP directory API, please join our Discord server