arachne-mcp@1.7.0
VERIFIED· not startedPublisher claims: "🕷️ MCP server for Arachne — search, scrape, browser, vision, transcribe, RAG, Social Research, GitHub (trending/PRs/activity) + VRT visual (Oito Olhos). 237 tools. Proprietary client — requires an Arachne plan (free tier: 500 requests/month) to use the API." 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
ARACHNE_API_KEYConfiguration, not credentials: ARACHNE_API_URL- Where it talks to
- no vendor host named in the codeAlso seu.pet, youtube.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 seu.pet, youtube.com as well as its own vendor. The guard injects ARACHNE_API_KEY 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.
What changed since 1.5.0
vet-skills diff arachne-mcp 1.5.0 1.7.0This version reaches for something 1.5.0 did not: 2 new hosts (seu.pet, youtube.com) · 1 new credential variable (ARACHNE_API_KEY). Compared from the two recorded runs, not from source.
- New hosts
- seu.pet, youtube.com
- New credential variables
- ARACHNE_API_KEY
1.5.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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 92/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
'calculada (nunca faça conta na cabeça). Sandbox AST, nunca eval(). Ex: 1.5*300/7.',Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.No other findings across 2,698 lines in 14 files.
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 arachne-mcp@1.7.0 as of 13 min ago. This is the package itself, not its dependencies.