Is doconda@0.7.0 safe to install?

doconda@0.7.0

VERIFIED

Publisher claims: "Create, review and edit editable Word, PowerPoint, Excel and PDF files from any AI agent. Remote MCP server with OAuth sign-in or an API key, or local over stdio with npx @doconda/mcp." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher b-c-software · publishing for 1 daysInstalls 0Last detonated 14 h ago

$npx skills add doconda

Watch Report an issue

Coverage

Started with a decoy DOCONDA_API_KEY; tool list observed. Tool calls with a real credential not tested.

Tested: server startup with a tagged decoy in DOCONDA_API_KEY · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
Not tested: what the tools do when called with a real credential
Needs: DOCONDA_API_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

Before you give it your token

It will ask for: no credential variables read in the code; at startup it asked for DOCONDA_API_KEY
Where it talks to: doconda.test (its own)
What the honeypot saw: no credential files read · no network
What we could not test: what the tools do when called with a real credential

Reasonable to connect. No credential asked for, no third-party host named, Started with a decoy DOCONDA_API_KEY; tool list observed. Tool calls with a real credential not tested.

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) on 2026-11-13 and scored it 91/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 45 s · 2 scenarios · 0 deviations

t+CategoryObserved action

0.0sprocessno install scripts in bundle

5.1sprocessdependency install exit 0

25sprocessrelaunched with a decoy DOCONDA_API_KEY (tagged; nothing real)

45sclaimed8 tools with a decoy DOCONDA_API_KEY: create_document, upload_file, convert_file, edit_document, list_documents, get_document, get_report, read_artifact_data

45stoolsf11d7ed6e1c41804

45stoolscde600af90375730

45stools3e7581263313de7b

45stools2380796e6bdd652d

45stools00ea3a27740ead70

45stools1b181853127c93c3

45stoolsacb8714771e1237f

45stoolsc11c2f1d50b26fae

45sprocessscript backend runs setup only

45sprocessno install scripts to re-run

Static findings

MEDIUM

npx invocation of non-well-known package.github/ISSUE_TEMPLATE/bug_report.md:16 · npx invocation of non-well-known package — may execute untrusted code- Remote (`https://api.eu.doconda.com/mcp`) or local (`npx @doconda/mcp`):Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

No other findings across 2,964 lines in 21 files.

Cost to the agent

Instructions loaded

≈36 tok

1 file · 21 in bundle

Tool list per prompt

≈1,988 tok

8 tools · 249 per tool

Handshake

663 ms

launch to tools/list, stdio

Undocumented tools

description under 20 chars · avg 291

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

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.