Vigia
Related Servers
Alternatives to Vigia
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.MIT
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.16 npmISC
- AlicenseAqualityBmaintenanceEnables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.5213 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables coding assistants to pull on-demand documentation for any npm package — TypeScript signatures, prose docs, and code examples formatted to match the user's intent (how-to, reference, or migration). It also supports version comparison with real changelog-backed breaking changes, cross-version migration guides, error diagnosis, side-by-side package comparison, and project dependency scanning for outdated, deprecated, or insecure packages.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.1MIT
- AlicenseAqualityBmaintenanceProvides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.674 npmMIT
TDQS
Scored across 12 tools
Most tools target clearly distinct resource+action combinations: package status, version status, upgrade impact, symbol existence, compatibility selection, manifest audit, runtime EOL, model status, and package search. The main overlap is between changes_since_cutoff and recent_changes, which both answer 'what changed since my training data,' but their descriptions differentiate a curated cutoff snapshot from a raw detection feed. Minor confusion risk remains.
All names use lower snake_case and are descriptive. However, conventions are mixed: verb_noun (find_package, list_versions, upgrade_impact, check_dependencies) alongside noun_status (package_status, version_status, symbol_status) and ad hoc phrases (changes_since_cutoff, recent_changes). Readable but not a single predictable pattern.
12 tools is well within the 3-15 sweet spot for a dependency/runtime intelligence server. Each tool covers a distinct analysis mode, so the count feels well scoped rather than bloated or thin.
Coverage is comprehensive for read-only software supply-chain intelligence: package search/status/versions/vulnerabilities, version compatibility, upgrade impact, symbol checking, manifest audit, runtime EOL, AI model status, and change feeds. Cross-references handle edge cases, and stated ecosystem limits are explicit rather than silent gaps.