grounded-mcp
Related Servers
Alternatives to grounded-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides comprehensive contextual information about npm packages including README files, versions, dependencies, download statistics, and search functionality. Enables users to explore and analyze npm packages through natural language queries with intelligent GitHub README fetching and branch fallback.9MIT
- AlicenseAqualityCmaintenanceLive operational status for 2,400+ major software services — AWS, GitHub, Stripe, OpenAI, Cloudflare, and more — pulled from each provider's official status page and returned as a normalised up / degraded / down result for any service you ask about.51MIT
- AlicenseBqualityDmaintenanceEnables querying NPM package download statistics, metadata, and dependency information through natural language.2MIT
- AlicenseCqualityBmaintenanceMonitor the real-time status of 200+ popular APIs and services. Check if services like GitHub, Stripe, AWS, and Slack are experiencing outages or degraded performance directly from your AI assistant.58 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables checking real-time operational status of 75+ AI services (OpenAI, Anthropic, Cursor, etc.) through tools like check_ai_status and list_ai_services.MIT
- AlicenseNot gradedqualityBmaintenanceProvides 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.MIT
TDQS
Scored across 4 tools
The tools `check_downloads` and `check_package_version` are both specific to package registries, and `lookup_fact` can replicate their functionality by querying the same sources (npm/pypi) with appropriate fields, causing ambiguity. `check_service_status` is distinct but also could be covered by `lookup_fact` with source 'statuspage'.
Three tools use the `check_` prefix, while `lookup_fact` uses a different verb but still follows a verb_noun pattern. The naming is mostly consistent and predictable.
With 4 tools, the set is small but reasonable for checking package metrics and service status. The redundancy suggests a slightly lower count could suffice, but overall it is not excessive or insufficient.
The server covers basic checks for npm/PyPI packages and cloud services, but lacks operations like listing available packages/services, comparing versions, or retrieving more detailed metadata beyond the predefined fields. Some intended functionality is indirectly available via `lookup_fact`, but the surface feels gappy.