sitebay-mcp@0.1.1774045660
VERIFIED· not startedPublisher claims: "SiteBay MCP Server - WordPress hosting management through Claude Code" 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
CLOUDFLARE_API_TOKENSITEBAY_API_TOKENConfiguration, not credentials: BACKEND_URL, LOCAL_BIBLE_PATH, MCP_HTTP_HOST, MCP_HTTP_PORT, MCP_TRANSPORT, OUTPUT_PATH, SITEBAY_API_URL- Where it talks to
- sitebay.org (its own)Also githubusercontent.com, cloudflare.com — 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 githubusercontent.com, cloudflare.com as well as its own vendor. The guard injects CLOUDFLARE_API_TOKEN, SITEBAY_API_TOKEN only into requests to sitebay.org (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-18 and scored it 81/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
<summary><strong>📡 Run over HTTP</strong></summary> ```bash # Defaults to 127.0.0.1:7823 uvx sitebay-mcp --http # Or specify host/port uvx sitebay-mcp --http -Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.…ay", "title": "Keys", "examples": [["/wp-content/themes/twentytwentythree/readme.txt"]]}, "version_ids": {"items": {"anyOf": [{"type": "string"}, {"type": "null"}]}, "type": "array", "title": "Version Ids", "examples": [["version_id_1", "v…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."build": "npx @smithery/cli build",Fix: Pin versions and sources; vendor anything fetched at install time.console.log(`Wrote stub to ${OUTPUT_PATH}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."dev": "npx wrangler dev",Fix: Pin versions and sources; vendor anything fetched at install time.// 3. Try npx wrangler whoami to confirm auth, then read token via wrangler secretFix: Pin versions and sources; vendor anything fetched at install time."deploy": "npx wrangler deploy"Fix: Pin versions and sources; vendor anything fetched at install time.const whoami = execSync("npx wrangler whoami 2>&1", { encoding: "utf-8" });Fix: Pin versions and sources; vendor anything fetched at install time.console.log(`\nWrote ${results.length} embeddings to ${OUTPUT_PATH}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."No Cloudflare API token found. Set CLOUDFLARE_API_TOKEN env var or log in with `npx wrangler login`.",Fix: Pin versions and sources; vendor anything fetched at install time.console.log("Wrangler whoami output:", whoami.slice(0, 200));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.<summary><strong>🔑 Authentication Issues</strong></summary> 1. Verify your API token is correct 2. Check that the token is properly set in the environment variFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 sitebay-mcp@0.1.1774045660 as of 30 min ago. This is the package itself, not its dependencies.