realtimex-web-scraping-mcp-server@0.1.0
VERIFIED· not startedPublisher claims: "A Model Context Protocol (MCP) server for web scraping using Crawl4AI" 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
LITELLM_API_KEYConfiguration, not credentials: LITELLM_API_BASE, LITELLM_MAX_RETRIES, LITELLM_TIMEOUT, WEB_SCRAPING_BROWSER_TIMEOUT, WEB_SCRAPING_CDP_URL, WEB_SCRAPING_DEFAULT_HEADLESS, WEB_SCRAPING_DEFAULT_MODE, WEB_SCRAPING_DEFAULT_OUTPUT_FORMAT, WEB_SCRAPING_DEFAULT_TIMEOUT, WEB_SCRAPING_ENABLE_SESSIONS, WEB_SCRAPING_MAX_CONCURRENT, WEB_SCRAPING_MAX_URLS, WEB_SCRAPING_SERVER_NAME, WEB_SCRAPING_SERVER_VERSION, WEB_SCRAPING_USER_DATA_DIR- Where it talks to
- no vendor host named in the code
- 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. It asks for LITELLM_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-15 and scored it 87/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
# Mask proxy credentialsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.logger.error("Failed to kill session", session_id=session_id, error=str(e))Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 realtimex-web-scraping-mcp-server@0.1.0 as of 1 h ago. This is the package itself, not its dependencies.