stele-mcp@18.16.4
VERIFIED· not startedPublisher claims: "MCP server for Stele, governed agent memory. Agents log what worked and what failed; a lesson stays out of search until another named actor promotes it with evidence." 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
STELE_API_KEYSSTELE_AUTH_DISABLEDSTELE_STORE_DSNConfiguration, not credentials: STELE_ALLOWED_HOSTS, STELE_ENV, STELE_NOW, STELE_RATE_LIMIT_BURST, STELE_RATE_LIMIT_PER_MINUTE, STELE_STORE, STELE_STORE_ID, STELE_TOOL_SET- 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 STELE_API_KEYS, STELE_AUTH_DISABLED, STELE_STORE_DSN 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-19 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
spec.loader.exec_module(mod)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.mod = importlib.util.module_from_spec(spec)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 stele-mcp@18.16.4 as of 4 h ago. This is the package itself, not its dependencies.