scoutdocs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token to increase API rate limits from 60 req/hr to 5,000 req/hr |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_package_infoA | Get metadata for a package: latest stable version, description, docs URL, repository, license. Supports Python (PyPI), JavaScript/TypeScript (npm), and Rust (crates.io). |
| get_package_docsA | Fetch actual documentation content for a package. Returns README or description text. Use get_package_info first to check version. |
| search_package_docsA | Search a package's documentation for a query. Discovers pages from the registry's docs/homepage, llms.txt / llms-full.txt, sitemap.xml, and same-host links. Returns the highest-scoring pages with source URLs. Bounded to a small set of pages and characters. |
| detect_project_dependenciesA | Inspect manifests/lockfiles in a local project directory and return the declared dependencies. Supports Python (pyproject.toml, requirements*.txt, uv.lock), npm (package.json, package-lock.json), and Rust (Cargo.toml, Cargo.lock). Local-only — runs on the user's machine. |
| cache_statsA | Get cache statistics (total entries, valid, expired). |
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 5 tools
Each tool has a clearly distinct purpose: metadata retrieval, documentation fetching, documentation search, local dependency detection, and cache statistics. No overlap or ambiguity.
Four tools follow the verb_noun pattern (get_package_info, get_package_docs, search_package_docs, detect_project_dependencies), while cache_stats deviates slightly but still uses consistent snake_case and remains descriptive.
Five tools is an ideal count for this domain, covering all necessary operations without redundancy or overwhelming options.
The tool set covers the full workflow for exploring package documentation: metadata lookup, content retrieval, search, and even local dependency detection. No obvious gaps.