devos-intelligence-mcp@0.1.0
VERIFIEDPublisher claims: "Enables AI coding agents to query the semantic graph, observations, and context packs generated for their repository, receiving compact answers with file:line evidence and redacted snippets instead of raw generations. It resolves generations from local folders, OCI caches, or GHCR and supports federation queries across repositories." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
DEVOS_MCP_GH_TOKENDEVOS_MCP_REGISTRY_TOKENGHCR_TOKENConfiguration, not credentials: DEVOS_MCP_CACHE, DEVOS_MCP_GENERATIONS, DEVOS_MCP_MAX_ANCESTORS, DEVOS_MCP_OCI, DEVOS_MCP_OCI_MAX_BYTES, DEVOS_MCP_OCI_REFERENCE, DEVOS_MCP_OCI_SYSTEMS_REFERENCE, DEVOS_MCP_OCI_TIMEOUT_MS, DEVOS_MCP_REGISTRY_USER, DEVOS_MCP_SYSTEM, DEVOS_MCP_WORKSPACE, DOCKER_CONFIG- 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
- what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for DEVOS_MCP_GH_TOKEN, DEVOS_MCP_REGISTRY_TOKEN, GHCR_TOKEN 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.
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-12 and scored it 85/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 · 20 s · 2 scenarios · 0 deviationsStatic findings
RUN mkdir -p /generations /cache && chmod 1777 /cacheFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.…ation publishes system generations; the server looks them up by the input tags `<system>.<repo>.<commit>` (the immutable `<system>-<key>` and `<system>-main` tags are d…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.const offline = await new Resolver(loadConfig({ ...env, DEVOS_MCP_OCI_REFERENCE: 'http://127.0.0.1:9/{owner}/context-{repo}' })).resolve(dir);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.&& rm -rf /var/lib/apt/lists/* \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.const layer = tarGz(folderEntries(sys, ['manifest.json', 'inputs.ndjson', 'context/overview.md']));Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…6-10-30):** one repository per owner, `ghcr.io/<owner>/context-systems`. Tags: `<system>-<key>` (immutable), `<system>-main` (moving), and one per included input, `<sys…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.assert.equal(redact('https://user:pw@host/x'), 'https://<redacted>@host/x');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN npx tsc -p tsconfig.json \Fix: Pin versions and sources; vendor anything fetched at install time.assert.throws(() => readTar(tarGz([{ path: '/etc/passwd', data: Buffer.from('x') }]), 1e6), /absolute path/);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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.