grounded-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROUNDED_API_KEY | No | API key for higher rate limits (1,000 req/day). Sign up at https://grounded-api.dev. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_factB | 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" |
| check_package_versionA | 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") |
| check_downloadsA | 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") |
| check_service_statusA | 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" |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.