scoutdocs-mcp@0.2.0b4
VERIFIED· not startedPublisher claims: "MCP server that fetches and searches latest stable documentation for packages on PyPI, npm, and crates.io." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
GITHUB_TOKENConfiguration, not credentials: ALLOWED_ORIGINS, CACHE, CACHE_TTL_SECONDS, RATE_LIMIT_MCP, RATE_LIMIT_SEARCH, SCOUTDOCS_VERSION, SEARCH_MAX_CHARS_PER_PAGE, SEARCH_MAX_PAGES, SEARCH_MAX_TOTAL_CHARS- Where it talks to
- no vendor host named in the codeAlso docs.rs, crates.io, sitemaps.org — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names docs.rs, crates.io, sitemaps.org as well as its own vendor. The guard injects GITHUB_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-17 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
run: npx wrangler deploy --dry-run --outdir=distFix: Pin versions and sources; vendor anything fetched at install time."https://user:[email protected]/psf/requests",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for scoutdocs-mcp@0.2.0b4 as of 21 min ago. This is the package itself, not its dependencies.