Provides real-time access to package metadata for Flask, including latest versions and weekly download counts via the PyPI registry.
Allows monitoring the operational and service health status of GitHub.
Provides tools for querying real-time npm package data, including latest versions, weekly download counts, licenses, and dependency information.
Enables tracking of Python packages on PyPI, offering tools to check versions, download statistics, and package metadata.
Allows checking the latest version, license, and weekly download statistics for the React package on npm.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@grounded-mcp What's the latest version of React?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for real-time package versions, download counts, and service status — powered by Grounded.
Tracks 1,000+ npm and PyPI packages and 76 cloud services. No signup required.
claude mcp add grounded -- uvx grounded-mcpAdd to your claude_desktop_config.json:
{
"mcpServers": {
"grounded": {
"command": "uvx",
"args": ["grounded-mcp"]
}
}
}Add to your MCP settings:
{
"grounded": {
"command": "uvx",
"args": ["grounded-mcp"]
}
}Related MCP server: API Status Check MCP Server
Tool | Description | Example |
| Latest version of an npm or PyPI package |
|
| Weekly download count |
|
| Cloud service operational status |
|
| General-purpose fact lookup |
|
For npm/PyPI packages: latest_version, license, deprecated, dep_count, required_runtime, weekly_downloads
For services: status
Works out of the box with no API key (50 lookups/day per IP).
For higher limits, set GROUNDED_API_KEY:
claude mcp add grounded -e GROUNDED_API_KEY=your_key -- uvx grounded-mcpSign up for a free API key (1,000 req/day) at https://grounded-api.dev.
Ask your AI assistant:
"What's the latest version of React?"
The assistant calls check_package_version("react") and gets:
Value: 19.2.4
Source: https://registry.npmjs.org/react
Fetched at: 2026-03-06T12:00:00Z
Hash: sha256:a1b2c3...
Tier: warm (TTL: 300s)Check the weekly download count of a package on npm or PyPI.
Args: package_name: The package name — e.g. "react", "express", "flask", "requests" registry: "npm" or "pypi" (defaults to "npm")
Inputs: package_name (required), registry. Returns: result
Check the latest version of a package on npm or PyPI.
Args: package_name: The package name — e.g. "react", "express", "flask", "requests" registry: "npm" or "pypi" (defaults to "npm")
Inputs: package_name (required), registry. Returns: result
Check the current status of a cloud service (via its status page).
Args: service_name: The service name — e.g. "github", "stripe", "openai", "cloudflare", "vercel"
Inputs: service_name (required). Returns: result
Look up any fact tracked by Grounded.
Args: source: The fact source — "npm", "pypi", or "statuspage" entity: The entity name — e.g. "react", "flask", "github" field: The fact field — e.g. "latest_version", "license", "deprecated", "dep_count", "required_runtime", "weekly_downloads", or "status"
Inputs: source (required), entity (required), field (required). Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Dive into the world of npm with our NPM Package Info MCP. Access crucial metadata about any npm
Live internet status, security incidents, and dependency and GitHub repo checks. No key.
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Live npm and UNPKG data for AI agents: resolution, audits, import maps, malware/CVE checks.