soma@1.3.2
CAUTION· not startedPublisher claims: "Soma is a protocol for agents to trust each other: a message is an envelope with a hard token budget, a mandate, a price and an Ed25519 signature, so refusals name the rule and context degradation is declared. Ships MCP, A2A and x402 carriers, three-tier memory, signed receipts, reputation from facts, federation with portable history, and a conformance suite any implementation can pass." 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: Caution 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
SOMA_SECRETSOMA_SIGNING_KEYSOMA_TOKENX402_GATE_SUB_SECRETConfiguration, not credentials: SOMA_AGENT_DESCRIPTION, SOMA_AGENT_NAME, SOMA_AGENT_URL, SOMA_AGENTS, SOMA_COLD, SOMA_DB, SOMA_EMBED_MODEL, SOMA_EMBED_THRESHOLD, SOMA_FORCE_VISIBILITY, SOMA_HISTORY, SOMA_MANAGED, SOMA_MAX_BODY, SOMA_PATH_ALIASES, SOMA_QUIET, SOMA_QUOTA_PER_HOUR, SOMA_RATE_LIMIT_PER_HOUR, SOMA_REPUTATION, SOMA_SEMANTIC, X402_GATE_FACILITATOR, X402_GATE_FREE_PER_DAY, X402_GATE_NETWORK, X402_GATE_PAY_TO, X402_GATE_PRICE_ATOMS, X402_GATE_SUB_PRICE_ATOMS- Where it talks to
- soma.dev (its own)Also rta.lat, payai.network, x402.org, your-hub.example — 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 rta.lat, payai.network, x402.org, your-hub.example as well as its own vendor. The guard injects SOMA_SECRET, SOMA_SIGNING_KEY, SOMA_TOKEN, X402_GATE_SUB_SECRET only into requests to soma.dev (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-16 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
if name == ".env" or (name.startswith(".env.") and not name.endswith((".example", ".sample", ".test", ".dist"))):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* файл .env или его копия в репозитории,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.findings.append(f"{rel}: файл с секретами (.env) не должен быть в репозитории")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.в `~/.env` уже лежат `X402_NETWORK=eip155:84532` (Sepolia) для тестовFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert memory.get_cold("../../etc/passwd") is NoneFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return subprocess.run(["git", "-C", str(repo), *args], capture_output=True,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.- name: Secrets, .env files and third-party mailFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…ublic facts, quotas).\n\nYour own node — private memory, own key:\n\n```json\n{"mcpServers": {"soma": {"url": "https://rta.lat/hub/mcp",\n "headers": {"Authorization": "Bearer $SOMA_TOKEN"}}}}\n```\n\nMemory: `soma_remember` — store a fact…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.chmod +x "$ROOT/.githooks/pre-commit"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.<pre>{{"mcpServers": {{"soma": {{"url": "https://rta.lat/hub/mcp",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim mrpkk: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.