lastseen-mcp
Related Servers
Alternatives to lastseen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables checking whether software packages are deprecated, archived, stale, active, or unknown with supporting evidence, auditing dependency manifests, and looking up runtime support and end-of-life dates.MIT
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.13 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables agents to query whether a WordPress plugin, npm package, or PyPI project looks abandoned, returning a live abandonment-risk score, status, and the registry signals behind it, plus raw registry, GitHub, and version history detail. Calls are paid per request in USDC via x402, with free discovery and source-listing tools.MIT
- AlicenseNot gradedqualityDmaintenanceMonitors and analyzes dependency health in Node.js projects, providing tools to check outdated packages, vulnerabilities, licenses, and suggest safe upgrades.8 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables users to look up package versions, scan for vulnerabilities, and analyze dependencies across multiple registries (npm, Maven, PyPI, etc.) using exact version recommendations for security.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.1,348 npmMIT
TDQS
Scored across 4 tools
Each tool targets a distinct input scope: single owner/repo, org slug, pasted manifest, and category profile. The scopes are clearly described, and the batch manifest tool is unlikely to be confused with the single-entity or org-level lookups.
Three of the four tools follow the consistent check_<scope> pattern (check_entity, check_org, check_manifest). survival_profile breaks the verb_noun pattern, but it is a single recognizable exception rather than a systemic inconsistency.
Four tools is a reasonable size for a narrow read-only lookup service. However, survival_profile is effectively an unsupported stub that always returns not_supported, so it pads the count without adding a working capability.
The core lookup workflows are covered: single entity, org-wide, and manifest-based batch checks. The main gap is category-level ranking, which survival_profile cannot provide, though the description points to alternative lookups and external dumps as workarounds.